[RP-PPPoE] Which timeout affects PADO packets?
Dan Jacobson
jidanni at jidanni.org
Sun Apr 14 00:26:56 EDT 2019
What timeout needs to be adjusted to avoid
"Timeout waiting for PADO packets. Unable to complete PPPoE Discovery."?
09:54:48 kernel: r8169 0000:07:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw
09:54:48 kernel: Generic PHY r8169-700:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-700:00, irq=IGNORE)
09:54:48 kernel: IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
09:54:48 pppd[9477]: Plugin rp-pppoe.so loaded.
09:54:48 kernel: PPP generic driver version 2.4.2
09:54:48 pppd[9479]: pppd 2.4.7 started by jidanni, uid 0
09:54:48 kernel: NET: Registered protocol family 24
09:54:50 kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 100Mbps/Full - flow control rx/tx
09:54:50 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
09:55:23 pppd[9479]: Timeout waiting for PADO packets
09:55:23 pppd[9479]: Unable to complete PPPoE Discovery
09:55:53 pppd[9479]: PPP session is 1
09:55:53 pppd[9479]: Connected to 34:6e:9d:91:30:1e via interface enp7s0
09:55:53 pppd[9479]: Using interface ppp0
09:55:53 pppd[9479]: Connect: ppp0 <--> enp7s0
09:55:53 systemd-udevd[9483]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
09:55:54 pppd[9479]: PAP authentication succeeded
As you can see it connects just fine, without human intervention, but on its second cycle.
What parameter can I adjust to get a longer cycles, so no error occurs? Thanks.
More information about the RP-PPPoE
mailing list