Computer can not see ethernet connection with board PYNQ-Z2

Support
21

sorry for that here is full output:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-IA80HBJ
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hs-bremen.de

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
Physical Address. . . . . . . . . : 4C-CC-6A-DE-9F-AD
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Unknown adapter ProtonVPN TUN:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ProtonVPN Tunnel
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Unknown adapter Połączenie lokalne:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-ProtonVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-CE-FE-BA-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Połączenie lokalne* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 10-F0-05-9A-0D-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : hs-bremen.de
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3168
Physical Address. . . . . . . . . : 10-F0-05-9A-0D-CB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8977:7614:96af:9af5%9(Preferred)
IPv4 Address. . . . . . . . . . . : 172.31.11.160(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Lease Obtained. . . . . . . . . . : wtorek, 10 maja 2022 12:27:31
Lease Expires . . . . . . . . . . : wtorek, 10 maja 2022 16:37:30
Default Gateway . . . . . . . . . : 172.31.255.254
DHCP Server . . . . . . . . . . . : 194.94.24.187
DHCPv6 IAID . . . . . . . . . . . : 84996101
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-56-1D-96-4C-CC-6A-DE-9F-AD
DNS Servers . . . . . . . . . . . : 194.94.24.34
194.94.24.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Połączenie sieciowe Bluetooth 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2
Physical Address. . . . . . . . . : 10-F0-05-9A-0D-CF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

board pinging the computer
image

22

The arp -a and arp -s is set under Windows not the Zynq board.
Must sure you got my meaning right.
Generally it is bounded by after 1st connections.
Interface: 192.168.1.37 — 0x13
Internet Address Physical Address Type
192.168.1.1 04-d4-c4-45-9c-98 dynamic
192.168.1.39 0a-63-c4-90-1b-42 dynamic
192.168.1.53 26-b4-6b-82-fa-d4 dynamic <<<<<<<<
192.168.1.55 00-e0-4c-ea-2e-21 dynamic

xilinx@pynq:/boot$ ping 192.168.1.37
PING 192.168.1.37 (192.168.1.37) 56(84) bytes of data.
64 bytes from 192.168.1.37: icmp_seq=1 ttl=128 time=0.232 ms
64 bytes from 192.168.1.37: icmp_seq=2 ttl=128 time=0.221 ms
64 bytes from 192.168.1.37: icmp_seq=3 ttl=128 time=0.214 ms
^C
— 192.168.1.37 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2083ms
rtt min/avg/max/mdev = 0.214/0.222/0.232/0.007 ms
xilinx@pynq:/boot$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.53 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::24b4:6bff:fe82:fad4 prefixlen 64 scopeid 0x20
ether 26:b4:6b:82:fa:d4 txqueuelen 1000 (Ethernet)
RX packets 13521 bytes 2695190 (2.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7108 bytes 7493793 (7.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 26 base 0xb000

23

From your screenshots your Ethernet is not connected or not configure. I would expect to see your Ethernet connection on your PC with the static IP address you configured for it.

In both your screenshots ping isn’t working.

Check you followed the instructions.

If you are having problems with the direct connection to your PC, are you able to connect your board to your network? You might find this easier as you won’t have to configure anything. You will need to find the IP address of the board which you can do with ip a as you did above.

Cathal

24

I am not sure if I got your meanig right but here is how I understood it:

typed in windows cmd:
C:\Users\Michu>arp -a

Interface: 192.168.153.21 — 0xe
Internet Address Physical Address Type
192.168.153.1 c4-ad-34-e3-87-d6 dynamic
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

and then go to PUTTY:

xilinx@pynq:~$ ping 192.168.153.21
ping: connect: Network is unreachable
xilinx@pynq:~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:05:6b:02:c6:13 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 28 base 0xb000

eth0:1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.2.99 netmask 255.255.255.0 broadcast 192.168.2.255
ether 00:05:6b:02:c6:13 txqueuelen 1000 (Ethernet)
device interrupt 28 base 0xb000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 1206 bytes 96013 (96.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1206 bytes 96013 (96.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

1 Like
25

Your board is not able to assign a valid IP address from ifconfig so this is why it is not working.
So you didn’t do the IPV4 setup accordingly.

Check subnet is in bound aka both host and device are in 192.168.2.xxx
Check any thing are missed during the network setup procedure.

26

Here is a thing after I run board I should see “undefined connection” here:
image
but any of my computers don’t see it

so I go to adapter seetings and setup this like here:

image
image784×569 48.8 KB

27

Sadlly i have no acces to router

28

The screenshot from your PC network interface shows the Ethernet cable is unplugged.

Can you make sure the cable is plugged in then run the following again and post the output:
On PC: ipconfig /all
On board: ip a

Try ping again from board to PC and from PC to board.

Cathal

1 Like
29

The easiest way is to check all IP in the current subnet and manually forcing 1 by replacing 2.99 on the board to the same subnet with your assigned IP.

What I guess is that you are using WIFI on your PC and the board is plug to a wall or ethernet socket?

30

The Ethernet cable is plugged, I checked is cable okay and are the Ethernet ports in computers Okay by connecting two computers using same ethernet cable and it was working, computers could “see” each other. I start thinking that ethernet port on the board is not working. Btw. if I power the borad only one diode on the ethernet port is lighting, but I see that there is one more diode should it be also lighting?

C:\Users\Michu>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-6IBDSOR
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 40-B0-76-AC-80-53
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Połączenie lokalne* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 50-EB-71-77-42-4C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Połączenie lokalne* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 52-EB-71-77-42-4B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz
Physical Address. . . . . . . . . : 50-EB-71-77-42-4B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a00:c380:c101:5699:2190:2cf9:6a45:1f51(Preferred)
Temporary IPv6 Address. . . . . . : 2a00:c380:c101:5699:cd39:b94b:fc2e:e4d8(Preferred)
Link-local IPv6 Address . . . . . : fe80::2190:2cf9:6a45:1f51%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.153.21(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, May 12, 2022 12:44:34 PM
Lease Expires . . . . . . . . . . : Saturday, May 14, 2022 12:44:34 PM
Default Gateway . . . . . . . . . : fe80::c6ad:34ff:fee3:87d6%14
192.168.153.1
DHCP Server . . . . . . . . . . . : 192.168.153.1
DHCPv6 IAID . . . . . . . . . . . : 122743665
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-B9-53-DE-40-B0-76-AC-80-53
DNS Servers . . . . . . . . . . . : 185.76.188.33
185.76.188.49
9.9.9.9
1.1.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Połączenie sieciowe Bluetooth:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 50-EB-71-77-42-4F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

C:\Users\Michu>ping 192.168.2.99

Pinging 192.168.2.99 with 32 bytes of data:
Reply from 192.168.153.1: Destination net unreachable.
Reply from 192.168.153.1: Destination net unreachable.
Reply from 192.168.153.1: Destination net unreachable.
Reply from 192.168.153.1: Destination net unreachable.

Ping statistics for 192.168.2.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

image

31

This looks like there is come problem with the network interface on your PC. E.g. cable isn’t connected or there is some problem with the cable:

I can’t offer any more help or suggestions unless you can resolve this. You can try check the LEDs on your network ports yourself to see if they indicate anything.

As an alternative, you could try use a USB dongle and connect the board to your WiFi and then connect to it from your PC over WiFi.

Cathal

32

What I see is that your PC connecting to WIFI.
So you got to understand there are config when WIFI is connected Ethernet will be disable or not prioritized as packet T/R
So disable the WIFI ipconfig again connect the board and tell us what is the result meantime ARP -a if you got a Ethernet and WIFI adapter connected should return two sets of lists

Disable the WIFI just enable the Ethernet adapter and connect the board under CAT-5 or above cable to discuss what is the result.

No offense modulator sometime won’t really help or provided experienced debug details as mostly only get bug from user or developer like us.

Make sure your PYNQ board is set to the subnet of 192.168.153.xxx then see what is the result.

33

I’m not sure what you mean by this.

No offense modulator sometime won’t really help or provided experienced debug details as mostly only get bug from user or developer like us.

The Ethernet connection is showing as cable unplugged. Connection to the board will not work until this is resolved.

It shouldn’t matter if the board is also connected to WiFi so you shouldn’t need to disable it.

Cathal

34

What I am saying in nice manner is modulator not thinking in an non engineer ways aka expecting people to have backgrounds.

Why the host PC is connected to WIFI and the board is connected to the ethernet will not work (when both devices are in the same subnet)?

There are nothing to do with the PC connection method as long as it is in the same subnet.

35

Sadlly it did not help
image

I will try with USB dongle after weekend

36

Now you dont even have any network connection devices:
Open explorer: Control Panel\Network and Internet\Network Connections
Disable other unnecessary connection devices remain 1 and only 1 than you plan to connect to the board subnet.
ipconfig and check the current host ip address i.e. 192.168.1xx.xxx
Then goto the board and then manually assign an ip address to 192.168.1xx.[free # 2 to 254].
Then ping on PC and board vice versa

37

Hey guys
My problem is solved, I did many things so I am not sure which one exactlly was a solution

  1. I followed instructions under these two links:
    https://answers.microsoft.com/en-us/windows/forum/all/unable-to-see-pcs-on-my-workgroup-network-id/896aac05-3df9-40f8-9a4b-5869d39d4418
    http://woshub.com/network-computers-not-showing-windows-10/
    2 Restart my computer
    3 Disable all in my computer Wifi, bluetooth, VPN (just not ethernet ofcourse)
    4 Run PYNQ-Z2 board
    5 Connect computer with board via ethernet (I think it is important to first start up the board and let to flash all LEDs and after that plug ethernet cable)
38

So at the end what is the subnet that you can connected to? Any modification are made in the IPV4 settings?

39

No modification for IPV4, subnet I mean IP of the board is deafult, as far I understood what happend one of the windows updates diseabled detecion of some devices in the network. Anyway thanks for the help.

40

I will guess the explanation is not about Windows update nor the board itself. From your link i will think the PC is not turn on enable to discover in private network setting. This you can see and do test if this is the case and help out the setup procedure a bit.
From my PYNQ 2.7 build to connection I had never touch any Windows settings nor the board network settings. Once it is flash to the SD card it is ready to run without any access issue. So maybe due to your environment limitation of network control you got to set your PC to private on network settings.