ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

wdirksen · 2022-10-09 11:18:36

I have a new Intel Tiger Lake PC with a 2x 4x r5125 2.5Gb PCIe NIC cards hoping to replace conventional router running OpenWRT. The in tree r5169 kernel module is replaced by proprietary r5125 module. I have relied heavily on the excellent https://wiki.archlinux.org/title/router and have tested it with netctl + dnsmasq + dhcpcd + iptables/shorewall, but currently systemd-networkd + firewalld + radvd). While the setup works as intended when the WAN interface is connected to the LAN of the router, a successful WAN DHCP connection to the ONT never happens. The same machine running x64 OpenWRT 22.04 does connect to the ONT (without using VLAN) so it should work. I have searched the web endlessly and tried many setups and tweaks but am now at my wit's end. The ONT is supposed to accept a DHCP client but it won't. I have tried to factory reset, unplug, power cycle, wait forever, many times. I am hoping some change/tweak/setting will cure this.

This table is from the ISP's tutorial for 3rd party routers:

- WAN connection type - Automatic/Dynamic IP (DHCP)
- On Automatic IP connection - Host Name and MAC Address fields blank
- DNS Server Settings - Connect to DNS Server Automatically
- VLAN - Untagged (or Disable)

The NIC's are renamed to wan0, lan0, lan1, etc

wan.network

[Match]
Name=br0
Type=bridge

[Network]
Address=192.168.0.1/24
Address=fd54:xxxx:xxxx:xxxx::/64
DHCPServer=true
IPMasquerade=ipv4
IPv6PrivacyExtensions=kernel
IPv6SendRA=yes
DHCPv6PrefixDelegation=yes

[DHCPServer]
PoolOffset=100
PoolSize=100
EmitDNS=yes
DNS=9.9.9.9

br0.netdev

[NetDev]
Name=br0
Kind=bridge

br0.network

[Match]
Name=lan*
Type=ether

[Network]
Bridge=br0

wan.network

[Match]
Name=wan0
Type=ether

[Network]
DHCP=yes
IPv6PrivacyExtensions=kernel

radvd.conf

interface br0 {
    AdvSendAdvert on;
    prefix ::/64 {  };
    # Google Public DNS
    RDNSS 2001:4860:4860::8888 2001:4860:4860::8844 { };
};

sysctl conf files

# Enable IPv4 forwarding
net.ipv4.ip_forward = 1

# Enable IPv6 forwarding across all interfaces
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.forwarding = 1

# Enable privacy extensions
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
net.ipv6.conf.wan0.use_tempaddr = 2
net.ipv6.conf.lan0.use_tempaddr = 2
net.ipv6.conf.lan1.use_tempaddr = 2
net.ipv6.conf.lan2.use_tempaddr = 2
net.ipv6.conf.lan1G.use_tempaddr = 2
net.ipv6.conf.wlan0.use_tempaddr = 2

# Allow router advertisements through all interfaces
net.ipv6.conf.all.accept_ra = 2
net.ipv6.conf.default.accept_ra = 2
...

ip route (this is through the LAN of the router, through the ONT all wan0 routes are missing

default via 10.0.0.1 dev wan0 proto dhcp src 10.0.0.181 metric 1024
10.0.0.0/24 dev wan0 proto kernel scope link src 10.0.0.181 metric 1024
10.0.0.1 dev wan0 proto dhcp scope link src 10.0.0.181 metric 1024
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.1

DHCP config file from OpenWRT which works is nothing special:

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

firewall-cmd --info-zone=public

public (active)
  target: DROP
  icmp-block-inversion: no
  interfaces: wan0
  sources:
  services: dhcp dhcpv6-client plex
  ports:
  protocols:
  forward: yes
  masquerade: yes
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

# from 'systemctl status systemd-networkd' when running through the router LAN

systemd-networkd[473]: wan0: Gained carrier
systemd-networkd[473]: wan0: DHCPv4 address 10.0.0.181/24, gateway 10.0.0.1 acquired from 10.0.0.1

When connected to the ONT the 'Gained carrier' line is present, the second line with DHCPv4 is not
The ISP states, 'Host Name and MAC Address fields blank' but a blank hostname doesn't help. I don't know if /etc/hosts requires something different
I'm hoping someone who really knows this stuff can provide guidance. Thanks

Last edited by wdirksen (2022-10-19 10:43:10)

Koatao · 2022-10-09 16:54:59

Hello,

I know a bit about connecting CPE to an ISP through their fiber optic networks. But I have never encounter an ISP using DHCP to provide internet access for FTTH (only with PPPoE).
So what I'm about to say is more educated guess than anything else.

I'm a bit confused, but how do you know that the DHCP server is on the ONT? I'm pretty sure this is not the role of an ONT, if it really does that, then it is probably not an ONT (or not only an ONT).
Are you the one that has set up the OpenWRT router?

You can enable systemd-networkd log as DEBUG. It will give you more information.
https://superuser.com/questions/1187633 … d-networkd
To look at the logs, do not use systemctl status systemd-networkd command but journalctl -b -u systemd-networkd.

Can you post the logs of the OpenWRT router DHCP client when it connects to your ISP network? And the network configuration it finally has at the end (IP address and routing tables at least). You can mask the public IP addresses and MAC address if you want, as long as it stays coherent.

You can also sniff the network frame of your OpenWRT router and your arch one and look at the differences during the connection process to your ISP network to understand something you might be missing. You can use tcpdump, export as pcap file and read the pcap file with a graphical software like Wireshark. If you don't find any differences between the frame they are sending except the source MAC address, try spoofing your arch WAN interface's MAC address with the OpenWRT WAN interface's MAC address.

You tried to disable the firewall on the arch router?
I will state the obvious here, but your LAN configuration is irrelevant.

Does your ISP provide support for 3rd-party router? If so, what did they tell you about your issue?

And what if you connect whatever has a DHCP client behind the ONT, does it get a network configuration from DHCP?

Last edited by Koatao (2022-10-09 17:04:25)

wdirksen · 2022-10-09 19:32:05

@Koatao, Thanks for your input! I will trial your recommendations within +/- 24 hours. A few responses:

According to the ISP's not so technically sharp call center service, the ONT is a mini 1Gb DHCP server with an optic WAN. No PPPoE for sure. Their main troubleshooting test is to plug a PC directly into the ONT LAN which I have tried with Windows 10 and linux with NM and dhcpcd. They are greatly surprised it doesn't 'just work'.
Indeed it makes more sense to from now on disable everything except the sole wan0.network on systemd-networkd when looking further at the journal
The ISP have a choice of rental routers which are optional. They state these are stock factory and not modified. Their BYOD policy is as stated above and again here:

- WAN connection type - Automatic/Dynamic IP (DHCP)
- On Automatic IP connection - Host Name and MAC Address fields blank
- DNS Server Settings - Connect to DNS Server Automatically
- VLAN - Untagged (or Disable)

Do you have any ideas about: "Automatic IP connection - Host Name and MAC Address fields blank'?

wdirksen · 2022-10-10 20:42:38

Here's the logs of 3 separate scenarios:

Archer C7 OpenWRT successful connection to ONT (not nearly as verbose):

OpenWrt 22.03.0, r19685-512e76967f
-----------------------------------------------------
root@ArcherC7-WRT:~# logread | grep wan
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan' is enabled
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan' is setting up now
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan6' is enabled
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan6' is setting up now
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Sep 17 07:46:03 2022 daemon.notice netifd: Interface 'wan6' has link connectivity
Sat Sep 17 07:46:04 2022 daemon.notice netifd: wan (2252): udhcpc: started, v1.35.0
Sat Sep 17 07:46:06 2022 daemon.notice netifd: wan (2252): udhcpc: broadcasting discover
Sat Sep 17 07:46:09 2022 daemon.notice netifd: wan (2252): udhcpc: broadcasting discover
Sat Sep 17 07:46:12 2022 daemon.notice netifd: wan (2252): udhcpc: broadcasting discover
Sat Sep 17 07:46:18 2022 daemon.notice netifd: wan (2252): udhcpc: broadcasting select for 158.xxx.xxx.xx, server 101.xxx.xxx.xxx
Sat Sep 17 07:46:18 2022 daemon.notice netifd: wan (2252): udhcpc: lease of 158.xxx.xxx.xx obtained from 101.xxx.xxx.xxx, lease time 1800
Sat Sep 17 07:46:19 2022 daemon.notice netifd: Interface 'wan' is now up

systemd-network wan0 through the OpenWRT router LAN where connection is successful (the LLDP Rx messages repeat beyond that):

[root@archlinux xxxxxx]# journalctl -e -u systemd-networkd
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: Received message from RAW socket, processing.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: OFFER
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: Received message from RAW socket, processing.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: ACK
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: lease expires in 11h 59min 59s
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: T2 expires in 10h 30min
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 client: T1 expires in 5h 59min 59s
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 address 10.0.0.181/24, gateway 10.0.0.1 acquired from 10.0.0.1
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Requesting DHCPv4 address (n/a): 10.0.0.181/24 (valid for 11h 59min 59s, preferred for 11h 59min 59s), flags: tentative, scope: global
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCP: No static routes received from DHCP server.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Requesting DHCPv4 route (n/a): dst: 10.0.0.1/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Requesting DHCPv4 route (n/a): dst: n/a, src: n/a, gw: 10.0.0.1, prefsrc: 10.0.0.181, scope: global, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCP: requested route destination 10.0.0.1/32 is in the assigned network 10.0.0.0/24, ignoring gateway address 10.0.0.1
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Requesting DHCPv4 route (requesting): dst: 10.0.0.1/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: State changed: configured -> configuring
Oct 11 08:23:44 archlinux systemd-networkd[11297]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=93 reply_cookie=0 signature=sa{sv}as error-name=n/a erro>
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: link_check_ready(): address 10.0.0.181/24 is not ready.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Configuring DHCPv4 address (requesting): 10.0.0.181/24 (valid for 11h 59min 59s, preferred for 11h 59min 59s), flags: tentative, scope: global
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Configuring DHCPv4 route (requesting): dst: 10.0.0.1/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Configuring DHCPv4 route (requesting): dst: n/a, src: n/a, gw: 10.0.0.1, prefsrc: 10.0.0.181, scope: global, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received updated DHCPv4 address (configured): 10.0.0.181/24 (valid for 11h 59min 58s, preferred for 11h 59min 58s), flags: n/a, scope: global
Oct 11 08:23:44 archlinux systemd-networkd[11297]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=94 reply_cookie=0 signature=sa{sv}as error-name=n/a erro>
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: link_check_ready(): IPv4LL:no DHCPv4:no DHCPv6:no DHCP-PD:no NDisc:yes
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: State changed: configuring -> configured
Oct 11 08:23:44 archlinux systemd-networkd[11297]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=95 reply_cookie=0 signature=sa{sv}as error-name=n/a erro>
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received new foreign route (configured): dst: 10.0.0.181/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: host, table: local(255), proto: kernel, type: local, nexthop: 0, priority: 0, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received new foreign route (configured): dst: 10.0.0.255/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: local(255), proto: kernel, type: broadcast, nexthop: 0, priority: 0, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received new foreign route (configured): dst: 10.0.0.0/24, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: main(254), proto: kernel, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: dhcp4_check_ready(): DHCPv4 address and routes are not set.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received remembered DHCPv4 route (configured): dst: 10.0.0.1/32, src: n/a, gw: n/a, prefsrc: 10.0.0.181, scope: link, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: dhcp4_check_ready(): DHCPv4 address and routes are not set.
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: Received remembered DHCPv4 route (configured): dst: n/a, src: n/a, gw: 10.0.0.1, prefsrc: 10.0.0.181, scope: global, table: main(254), proto: dhcp, type: unicast, nexthop: 0, priority: 1024, flags: n/a
Oct 11 08:23:44 archlinux systemd-networkd[11297]: wan0: DHCPv4 address and routes set.
Oct 11 08:23:46 archlinux systemd-networkd[11297]: wan0: LLDP Rx: Invoking callback for 'refreshed' event.
Oct 11 08:23:46 archlinux systemd-networkd[11297]: wan0: LLDP Rx: Successfully proc

systemd-network wan0 direct through to the ONT LAN where connection is unsuccessful. The ONT was power cycled beforehand. You can see I waited about 8 minutes after the ONT came online with Gained carrier:

[root@archlinux xxxxxx]# journalctl -u systemd-networkd | grep wan0i
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: Flags change: +LOWER_UP +RUNNING
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: Gained carrier
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: found matching network '/etc/systemd/network/wan0.network'.
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: DHCPv4 client: STARTED on ifindex 5
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: Acquiring DHCPv4 lease.
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: Discovering IPv6 routers
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: NDISC: Started IPv6 Router Solicitation client
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: LLDP Rx: Started LLDP client
Oct 11 08:48:58 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (init-reboot)
Oct 11 08:49:00 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 3s
Oct 11 08:49:02 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REBOOTED
Oct 11 08:49:02 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:49:03 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 7s
Oct 11 08:49:06 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:49:10 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:49:10 archlinux systemd-networkd[351]: wan0: NDISC: No RA received before link confirmation timeout
Oct 11 08:49:10 archlinux systemd-networkd[351]: wan0: NDISC: Invoking callback for 'timeout' event.
Oct 11 08:49:10 archlinux systemd-networkd[351]: wan0: NDisc handler get timeout event
Oct 11 08:49:10 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 14s
Oct 11 08:49:17 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:49:25 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 28s
Oct 11 08:49:33 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:49:54 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 55s
Oct 11 08:50:05 archlinux systemd-networkd[351]: wan0: DHCPv4 client: DISCOVER
Oct 11 08:50:05 archlinux systemd-networkd[351]: wan0: DHCPv4 client: Received message from RAW socket, processing.
Oct 11 08:50:05 archlinux systemd-networkd[351]: wan0: DHCPv4 client: OFFER
Oct 11 08:50:05 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:50:08 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:50:17 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:50:33 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:50:49 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 1min 48s
Oct 11 08:51:06 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:52:10 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:52:38 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 3min 33s
Oct 11 08:53:14 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:54:17 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:55:22 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)
Oct 11 08:56:11 archlinux systemd-networkd[351]: wan0: NDISC: Sent Router Solicitation, next solicitation in 6min 58s
Oct 11 08:56:25 archlinux systemd-networkd[351]: wan0: DHCPv4 client: REQUEST (requesting)

If needed I can rig up this PC to use x64 OpenWRT again where it did work but I think it will look the same as the Archer C7. The version will be the same: OpenWrt 22.03.0

Koatao wrote:

If you don't find any differences between the frame they are sending except the source MAC address, try spoofing your arch WAN interface's MAC address with the OpenWRT WAN interface's MAC address.

Would you be so kind to explain how do I can best do this? Thanks

Last edited by wdirksen (2022-10-10 20:55:59)

progandy · 2022-10-10 20:56:48

For systemd-networkd you can try these settings:

[DHCPV4]
SendHostname=false
ClientIdentifier=mac # or duid # or duid-only

You could also try to install busybox and run udhcpc on arch linux for testing purposes instead of systemd-networkd.

wdirksen · 2022-10-11 05:43:01

progandy wrote:

For systemd-networkd you can try these settings:
[DHCPV4]
SendHostname=false
ClientIdentifier=mac # or duid # or duid-only

I tried those to no avail previously (it felt good that I was thinking along the same lines being a novice)

progandy wrote:

You could also try to install busybox and run udhcpc on arch linux for testing purposes instead of systemd-networkd.

Immediate WAN connection with udhcpc !!
However later after a reboot, udhcpc didn't connect immediately.Will have to play around with it
So is it possible to use udhcpc on the WAN and system-networkd on the LAN with firewalld?

wdirksen · 2022-10-15 01:30:25

wdirksen wrote:

Immediate WAN connection with udhcpc !!

Unfortunately not. Udhcpc identifies the public IP in 'ip route' but does not make a connection
Back to square one.

Koatao · 2022-10-15 05:58:18

wdirksen wrote:

Udhcpc identifies the public IP in 'ip route' but does not make a connection

What do you mean by that? What is the error you get from the arch router?
If the DHCP server acknowledged your request (after its offer), then as far as DHCP protocol is concerned, everything is normal (this is still better than with systemd-networkd's DHCP client).

So you get a valid IP and gateway.
Can you ping the gateway with ICMP? If yes, you can do a traceroute 8.8.8.8 to try to pinpoint where the internet connection is failing.
Do you have trouble to make a connection to internet with IPv6 too?

Last edited by Koatao (2022-10-15 06:00:15)

wdirksen · 2022-10-17 20:11:17

@Koatao, Thanks for not giving up on this

udhcpc give varying results which isn't surprising as hotplugging the WAN in the working OpenWRT router is inconsistent sometimes requires power cycling the ONT etc, to regain the connection
I have had a connection with udhcpc only 2x. When it does show up in ip route but then there is no outside internet with failed ping results to google and failed pacman -Syu.
I would show a udhcpc log feed but even with the -S option set in udhcpc I can't find udhcpc output in journalctl with using a systemd service file or just running the binary as root.
I will try to look further into journalctl options.

The output I can see from udhcpc in systemctl status or output from the binary in all cases indicates it receives an IP from the ONT at discovery which it gets via the ISP's DNS servers as shown the logs above, beyond that no lease/connection happens except for when I got lucky
I forgot to mention that I have a fixed IP from the ISP but still is supposed to use the DHCP protocol. I have played around with fixed IP settings in dhcpcd, networkctl, system-networkd to no avail previously.

The ISP only offers a IPv4 public IP address with blank public IPv6 address in OpenWRT. A IPv6 IP is created by udhcpc (meant to be private?) but the syntax does not include words like 'found', 'received', or 'leased' associated with that IPv6 address

It will take a few days until I have time but will try to:
- Play around with "traceroute 8.8.8.8 to try to pinpoint where the internet connection is failing' and provide more logs
- Try to explicitly state the ISP's DNS servers in the setup based on logs stating they get the public IP "150.xxx...." from their DNS servers "101.xxx...."

Last edited by wdirksen (2022-10-17 22:41:33)

-thc · 2022-10-18 12:12:38

Please be precise. Saying this:

wdirksen wrote:

- Try to explicitly state the ISP's DNS servers in the setup based on logs stating they get the public IP "150.xxx...." from their DNS servers "101.xxx...."

by referring to this:

Sat Sep 17 07:46:18 2022 daemon.notice netifd: wan (2252): udhcpc: lease of 158.xxx.xxx.xx obtained from 101.xxx.xxx.xxx, lease time 1800

leads to confusion. This is a DHCPv4 lease from a DHCPv4 server. No "DNS" involved.

wdirksen wrote:

The ISP only offers a IPv4 public IP address with blank public IPv6 address in OpenWRT. A IPv6 IP is created by udhcpc (meant to be private?) but the syntax does not include words like 'found', 'received', or 'leased' associated with that IPv6 address

Please do not fall into the trap (as I once did) assuming IPv6 works just like IPv4. It doesn't - not at all. The IPv6 address you mention - presumably starting with "fe80" - is a link-local IPv6 address created by the IPv6 stack itself. No DHCPv6 involved.

wdirksen · 2022-10-19 10:41:33

@-thc, Thanks for the insights and advice

The issue is solved for good! It turned out to be solved by both udhcpc using standard config, and with systemd-networkd by adding the fixed public IP and gateway to the Network section of wan.network.
I did not recognize it working when trying different options previously because it turns out the router itself @ 10.0.0.1 had no internet access.
I just discovered the clients connected to the LAN did have internet all along. Luckily it only took a reboot to get internet access to the machine itself

Thanks to @Koatao and @progandy for the tips pointing me in the right direction
This is the working wan.network file

[Match]
Name=wan0
Type=ether

[Network]
DHCP=yes
IPv6PrivacyExtensions=kernel
Address=158.xxx.xxx.xx/24
Gateway=158.xxx.xxx.x

[DHCPv4]
SendHostname=false
ClientIdentifier=duid-only

Arch Linux

#1 2022-10-09 11:18:36

ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#2 2022-10-09 16:54:59

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#3 2022-10-09 19:32:05

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#4 2022-10-10 20:42:38

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#5 2022-10-10 20:56:48

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#6 2022-10-11 05:43:01

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#7 2022-10-15 01:30:25

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#8 2022-10-15 05:58:18

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#9 2022-10-17 20:11:17

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#10 2022-10-18 12:12:38

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

#11 2022-10-19 10:41:33

Re: ArchLinux router won't connect to fiber ONT (VLAN not required) SOLVED

Board footer