"no matching session" in ng_pppoe.c 18.104.22.168? (RELENG_6)
cpghost at cordula.ws
Wed Dec 5 18:16:32 PST 2007
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 22.214.171.124 and 126.96.36.199.
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
ng_pppoe: 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
Since the last working sources were from 2007/09/25, and
ng_pppoe.c was at rev. 188.8.131.52; and the new revision of
ng_pppoe.c is now at 184.108.40.206; 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.
Cordula's Web. http://www.cordula.ws/
More information about the freebsd-stable