Hello, Since I've updated a RELENG_6 router a few days ago, a long gone problem with ppp cropped up (again?); and I'm suspecting a regression between ng_pppoe.c 1.74.2.3 and 1.74.2.4. The problem is that the last mile carrier of the PPP provider that this router is attached to disconnects the ppp session forcibly once every 24h. Before the update, ppp would detect this and reconnect immediately. After the update, ppp doesn't recover gracefully from this anymore, but spits out on the console: ng_pppoe[5]: no matching session for hours, and tries to connect again every two minutes without success, until I manually stop and restart the userland ppp daemon (and then the connection is immediately restored with a new session). I've tried this for a few days now, and it is always the same: it's definitely not a problem on the provider's side: As soon as ppp restarts, it gets a new session without any problems and connects again. Since the last working sources were from 2007/09/25, and ng_pppoe.c was at rev. 1.74.2.3; and the new revision of ng_pppoe.c is now at 1.74.2.4; I'm suspecting that whatever was changed there could be the cause (because this "no matching session" is being logged from there). Since that router is not within easy reach, I'd rather not take the risk to compile a kernel with the old ng_pppoe.c, and have that box crash/hosed. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/
Alexander Motin
2007-Dec-06 05:08 UTC
"no matching session" in ng_pppoe.c 1.74.2.4? (RELENG_6)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 cpghost wrote:> The problem is that the last mile carrier of the PPP provider > that this router is attached to disconnects the ppp session > forcibly once every 24h. Before the update, ppp would detect > this and reconnect immediately. After the update, ppp doesn't > recover gracefully from this anymore, but spits out on the > console: > > ng_pppoe[5]: no matching session > > for hours, and tries to connect again every two minutes without > success, until I manually stop and restart the userland ppp daemon > (and then the connection is immediately restored with a new session). > I've tried this for a few days now, and it is always the same: it's > definitely not a problem on the provider's side: As soon as ppp > restarts, it gets a new session without any problems and connects > again. > > Since the last working sources were from 2007/09/25, and > ng_pppoe.c was at rev. 1.74.2.3; and the new revision of > ng_pppoe.c is now at 1.74.2.4; I'm suspecting that whatever > was changed there could be the cause (because this "no matching > session" is being logged from there).I have tested and unable to reproduce that myself with ppp -> mpd or mpd - -> mpd PPPoE connections. Actually I am not sure about any difference between reconnect and ppp restart. From the ng_pppoe node point of view it should be the same. Could you provide tcpdump output for connection tries from your Ethernet interface? Use "-pes 0" options please. - -- Alexander Motin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHV+Oc0kCgngV3usoRAnZtAKCQ/7hW63Zli9UiytDK1xj8lNrsBQCffwhl 377pyCH24ytoR8tOnbtYqX8=v+x0 -----END PGP SIGNATURE-----