The 7268cv2 is drawing its power from the PoE switch port. The WAN setting has Ethernet enabled, DHCP client, Use DNS from router - but the Ethernet port continues to report itself as unavailable.
The WiFi interface has been configured to connect to the WLAN in place in my lab and the WiFi interface has associated to that WLAN and enabled the 7268 to connect to both WisDM and TTN successfully.
There appears to be something funky about the DHCP process on that 7268 Ethernet port, as other devices are able to receive a DHCP address from that PoE Lan switch port.
Confirmation that the 7268 has been offered a DHCP IP address on its ethernet port, but for some reason the 7268 is not binding it to the Ethernet interface
Below you can see my gateway (RAK7289CV2) configuration. Could you get the your Gateway ethernet port Tracking configuration?
Maybe a wrong tracking configuration can make the interface as “down” because it is receiving a failure to reach the specified destination in the tracking feature.
Hi Claudio, I have attached the WAN Ethernet setting and the Tracking. IMO, the fact that the DHCP client in the 7268 has not accepted the DHCP offer and bound the ethernet port to that IP address is why the Ethernet port is inactive.
In my network environment, the WiFi interface and the Ethernet interface are in the same subnet, 10.10.10.x 255.255.255.0
I don’t know if the DHCP client in the 7268 has a conflict if both WiFi and Ethernet receive DHCP offers in the same subnet for both interfaces.
The 7268 should be able to receive IP addresses in the same subnet for both interfaces, since the 7268 does not have to route traffic between these interfaces.
But I could understand if the route table in the 7268 was confused if it received DHCP offers for the same subnet on two different interfaces.
Actually, I just realized. The 10.10.10.96 address is the DHCP address assigned to the WiFi interface. So now I am wondering if the DHCP request was actually sent out via the ethernet interface.
Do we know if the MAC address for the WiFi and Ethernet interfaces are different ?
I will try to sniff the ethernet interface later today
These are the results of commands I ran via the ssh connection
root@14-301024-K23101:~# ip route
default via 10.10.10.1 dev apcli0 proto static src 10.10.10.96 metric 20
10.10.10.0/24 dev apcli0 proto static scope link metric 20
169.254.0.0/16 dev eth0.2 proto kernel scope link src 169.254.201.11
192.168.230.0/24 dev br-lan proto kernel scope link src 192.168.230.1
root@14-301024-K23101:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0 apcli0
10.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 apcli0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0.2
192.168.230.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan
root@14-301024-K23101:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
link/ether ac:1f:09:19:c9:0b brd ff:ff:ff:ff:ff:ff
3: ip6tnl0@NONE: mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/tunnel6 :: brd ::
8: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
link/ether e2:a5:7d:d2:c3:ec brd ff:ff:ff:ff:ff:ff
14: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:09:19:c9:0b brd ff:ff:ff:ff:ff:ff
15: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:09:19:c9:0b brd ff:ff:ff:ff:ff:ff
16: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:09:19:c9:0b brd ff:ff:ff:ff:ff:ff
17: apcli0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether ae:1f:09:19:c9:0c brd ff:ff:ff:ff:ff:ff
It’s clear from this that the DHCP server assigned the 10.10.10.96 address to the apcli interface, but the eth0 interface in state UNKNOWN is confusing to me, as the 7268 is drawing power from this interface and there are activity lights on the ethernet switch port
The RAK utilities are buggy, especially when you change Ethernet between WAN/LAN. I found a recent issue where changing from a Static WAN Ethernet IP to a DHCP served LAN Ethernet was not fully clearing all the settings. There were also stale routes for the static IP
After looking in /etc/config/network I was able to see settings were only half cleared.
