openwrt / netifd

[MIRROR] OpenWrt Network interface configuration daemon

Home Page:https://git.openwrt.org/?p=project/netifd.git;

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No pppoe connect possible

schuettecarsten opened this issue · comments

The netifd commits from December 2023 break my pppoe connection to Deutsche Telekom AG. The connection is established and IP if set, but default route is not added. Looks like netifd crashes silently when the connection is established. Going back to the netifd version from November, 14th (before udebug was added) fixes this issue. The only difference that I can see in the logs is that the new version reports netifd: Network device 'pppoe-wan' link is down immediately after the connection was established while the older version does more stuff.

Logs of December version (failing):

Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: PAP authentication succeeded
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: peer from calling number XXX authorized
Tue Dec 19 10:13:47 2023 daemon.notice ttyd[4973]: [2023/12/19 10:13:47:7076] N: rops_handle_POLLIN_netlink: DELADDR
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: local  IP address XXX
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: remote IP address XXX
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: primary   DNS address XXX
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: secondary DNS address XXX
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: local  LL address XXX
Tue Dec 19 10:13:47 2023 daemon.notice pppd[9104]: remote LL address XXX
Tue Dec 19 10:13:47 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Tue Dec 19 10:13:47 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down
root@rpi4-01:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
62.155.242.194  *               255.255.255.255 UH    0      0        0 pppoe-wan
192.168.178.0   *               255.255.254.0   U     0      0        0 br-lan

Logs of november version (working):

Tue Dec 19 10:15:55 2023 daemon.notice pppd[5140]: PAP authentication succeeded
Tue Dec 19 10:15:55 2023 daemon.notice pppd[5140]: peer from calling number XXX authorized
Tue Dec 19 10:15:56 2023 daemon.notice ttyd[5248]: [2023/12/19 10:15:56:0777] N: rops_handle_POLLIN_netlink: DELADDR
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: local  IP address XXX
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: remote IP address XXX
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: primary   DNS address XXX
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: secondary DNS address XXX
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: local  LL address XXX
Tue Dec 19 10:15:56 2023 daemon.notice pppd[5140]: remote LL address XXX
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Interface 'wan6' is enabled
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Dec 19 10:15:56 2023 daemon.notice netifd: Interface 'wan' is now up
root@rpi4-01:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         p3e9bf2c2.dip0. 0.0.0.0         UG    0      0        0 pppoe-wan
62.155.242.194  *               255.255.255.255 UH    0      0        0 pppoe-wan
116.203.70.106  p3e9bf2c2.dip0. 255.255.255.255 UGH   0      0        0 pppoe-wan
192.168.178.0   *               255.255.254.0   U     0      0        0 br-lan

Did you try a build with the 2023-12-18 update included? It should fix the crashes.

Yes, without success.

Tue Dec 19 11:47:08 2023 daemon.info pppd[9842]: PPP session is 196
Tue Dec 19 11:47:08 2023 daemon.warn pppd[9842]: Connected to 54:1e:56:3b:3c:12 via interface br-eth1.7
Tue Dec 19 11:47:08 2023 daemon.info pppd[9842]: Using interface pppoe-wan
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: Connect: pppoe-wan <--> br-eth1.7
Tue Dec 19 11:47:08 2023 daemon.info pppd[9842]: Remote message: SRU=116448#SRD=533721#
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: PAP authentication succeeded
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: peer from calling number 54:1E:56:3B:3C:12 authorized
Tue Dec 19 11:47:08 2023 daemon.notice ttyd[4827]: [2023/12/19 11:47:08:6090] N: rops_handle_POLLIN_netlink: DELADDR
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: local  IP address 87.143.255.192
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: remote IP address 62.155.242.194
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: primary   DNS address 217.237.149.142
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: secondary DNS address 217.237.150.205
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: local  LL address fe80::a4af:2cca:2ce5:479a
Tue Dec 19 11:47:08 2023 daemon.notice pppd[9842]: remote LL address fe80::561e:56ff:fe3b:3c12
Tue Dec 19 11:47:08 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Tue Dec 19 11:47:08 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down

Does it create a corefile in /tmp? If so, could you please send it to me, along with your build system .config

There is no such file.

While testing, I tried to restart the network using /etc/init.d/network restart and got some Command failed: Request timed. On a second ssh connection, I saw that the restart process was waiting for ubus call network.interface down { "interface" : "lan" }. Looks like something deadlocks when ppp connects, so there is no crash.

Please try the latest version. It should work now.

Works now, thank you!