Jean-Marc Posted November 14, 2019 Posted November 14, 2019 Hi, I am running Debian buster 10.1 with following kernel on nanopir1 (1Gb of RAM) Linux srv-nanopir1-170 5.3.9-sunxi #5.99.191113 SMP Wed Nov 13 08:12:49 CET 2019 armv7l GNU/Linux I have all services up on local LAN Ethernet port, but not possible for me to setup WAN Ethernet port . Packages installed are .... Quote ansible@srv-nanopir1-170:~$ dpkg -l |grep linux-image ii linux-image-dev-sunxi 5.99.191113 armhf Linux kernel, version 5.3.9-sunxi ii linux-image-next-sunxi 5.92 armhf Linux kernel, version 4.19.62-sunxi The boot sequence is ... My current network configuration in udev is .... Quote ansible@srv-nanopir1-170:~$ cat /etc/udev/rules.d/99-eth-network-identify-interfaces.rules |grep -v "#" |grep -v "^$" SUBSYSTEM=="net", \ ACTION=="add", \ ATTR{dev_id}=="0x0", \ ATTR{type}=="1", \ ENV{ID_SERIAL}=="Realtek_USB_10_100_LAN_000000000000", \ ENV{ID_NET_DRIVER}=="r8152", \ ENV{ID_VENDOR}=="Realtek", \ NAME="et-prod" SUBSYSTEM=="net", \ ACTION=="add", \ ATTR{dev_id}=="0x0", \ ATTR{type}=="1", \ ENV{ID_PATH_TAG}=="platform-1c30000_ethernet", \ NAME="et-wan" As a result, r8152 kernel module is correctly installed Quote ansible@srv-nanopir1-170:~$ lsmod |grep r8152 r8152 49152 0 After connected one RJ45 to external DHCP server (running) , it is not possible to setup interface Quote ansible@srv-nanopir1-170:~$ sudo ip link ls dev et-wan 3: et-wan: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:00:00:70:03:05 brd ff:ff:ff:ff:ff:ff Quote ansible@srv-nanopir1-170:~$ sudo dhclient -v et-wan Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/et-wan/02:00:00:70:03:05 Sending on LPF/et-wan/02:00:00:70:03:05 Sending on Socket/fallback DHCPDISCOVER on et-wan to 255.255.255.255 port 67 interval 2 DHCPDISCOVER on et-wan to 255.255.255.255 port 67 interval 1 DHCPDISCOVER on et-wan to 255.255.255.255 port 67 interval 1 According hardware documentation, it seems that WAN port is based on on RTL8211E (§ 3.1) http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1 As a result, perhaps this bug is due to the fact there is no rtl8211e drivers Quote ansible@srv-nanopir1-170:~$ dpkg -l |grep firmware ii armbian-firmware 5.98 all Linux firmware ii firmware-atheros 20190114-2 all Binary firmware for Atheros wireless cards ii firmware-realtek 20190114-2 all Binary firmware for Realtek wired/wifi/BT adapters Quote ansible@srv-nanopir1-170:~$ dpkg -L armbian-firmware |grep -i 8211 ansible@srv-nanopir1-170:~$ dpkg -L firmware-realtek |grep -i 8211 Where is the firmware and the drivers ? Thanks in advance for your help tty-from-srv-nanopir1-170-2019-11-14-15h-39min.ok.txt
Jean-Marc Posted November 22, 2019 Author Posted November 22, 2019 Hello, is there a user of orangepiR1 with traces of good operation of the 2 Ethernet interfaces simultaneously? In advance, please provide the boot log of the kernel and the DTB version number
Igor Posted November 22, 2019 Posted November 22, 2019 On 11/14/2019 at 4:29 PM, Jean-Marc said: I am running Debian buster 10.1 with following kernel on nanopir1 Use unchanged stable image from the download section when asking for help. If you don't provide armbianmonitor -u ... you are wasting our precious time.
Jean-Marc Posted November 22, 2019 Author Posted November 22, 2019 Igor, Thanks for your reply. I have done new tests based on image: Armbian_19.11.3_Nanopi-r1_buster_current_5.3.9.7z test 1 : -------- Disconnect power, then reconnect power root@nanopi:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/22vY Please post the URL in the forum where you've been asked for. test 2: ------- Disconnect power, then reconnect power root@nanopi:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/22vZ Please post the URL in the forum where you've been asked for. root@nanopi:~# Conclusions: Eth0 (Wan port) is ok, but ... It seems that the MAC address on Ethernet port eth1 changed on each reboot, and on eth0, it is always the same. Could you please confirm this behaviour ? On file : http://ix.io/22vZ ### ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet XXX.XXX.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether be:11:34:10:e5:f0 brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 12:81:68:ec:e7:fa brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 66:f4:99:6c:47:19 brd ff:ff:ff:ff:ff:ff 5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8c:f7:10:9e:fc:f1 brd ff:ff:ff:ff:ff:ff On file : http://ix.io/22vY ### ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet XXX.XXX.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 32:cf:8d:ea:60:bc brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 12:81:68:ec:e7:fa brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ae:6d:32:73:9b:8f brd ff:ff:ff:ff:ff:ff 5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8c:f7:10:9e:fc:f1 brd ff:ff:ff:ff:ff:ff Thanks for your help
Jean-Marc Posted November 22, 2019 Author Posted November 22, 2019 Igor, Sorry, it was in the documentation (!) One Ethernet device gets random MAC 1
Recommended Posts