| Summary: | 'out of buffer space' after many PPPoE re-dial attempts, connectivity lost | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Bob Frazier <bobf> |
| Component: | kern | Assignee: | Brian Somers <brian> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.4-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Bob Frazier
2005-09-17 18:00:24 UTC
Bob,
next time this happends, please check the following things:
1) Does restart ppp(8) helps? To check this you will need to:
/etc/rc.d/ppp-user stop
[check that no ppp process is present]
/etc/rc.d/ppp-user start
If no success on 1), follow to 2):
2) Does restart of ppp(8) + renewal of tun(4) interface help?
/etc/rc.d/ppp-user stop
[check that no ppp process is present]
ifconfig tun0 destroy
[check that tun0 interfaces disappeared]
/etc/rc.d/ppp-user start
2) Does restart of ppp(8) + renewal of tun(4) + renewal of netgraph
PPPoE node helps?
/etc/rc.d/ppp-user stop
[check that no ppp process is present]
ifconfig tun0 destroy
[check that tun0 interfaces disappeared]
ngctl shutdown fxp0:orphans [assuming you run PPPoE on fxp0]
[check that no PPPoE nodes remained, 'ngctl types | grep pppoe' must
display 0]
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
Attach this to Audit-Trail. ----- Forwarded message from Bob Frazier <bobf@mrp3.com> ----- > next time this happends, please check the following things: It happened again today > 1) Does restart ppp(8) helps? To check this you will need to: > > /etc/rc.d/ppp-user stop > [check that no ppp process is present] in my case it was still running. I did a 'kill ###' on it, which ended it. > /etc/rc.d/ppp-user start This made the problem go away! Only /dev/tun0 was present, so the tun device was properly deleted when I killed the process, FYI. So it looks like it's client-side ppp doing it. ----- End forwarded message ----- Responsible Changed From-To: freebsd-bugs->brian Looks like related to ppp(8). Let Brian look at it. State Changed From-To: open->feedback Sorry I'm a little late to respond here... I'd be interested (if the originator still has such a setup) to know if routed is the only thing with a problem or if ppp ends up in a state where it's never able to re-establish the connection. If ppp is stuck, can the originator try something like "set log +phase lcp ipcp physical" and send the resulting log? I'm guessing that routed is sending traffic to tun0, but as ppp isn't connected, it won't read the data... after some time the interface queue just gets too big. If ppp is getting stuck, maybe I can reproduce the problem by having some other process repeatedly write something to tun0. If such traffic is hurting ppp's abililty to connect, then it can probably be taught to detect this and purge the offending data. Thanks. State Changed From-To: feedback->closed No response from the submitter in over three weeks. I conceed that I didn't originally respond in over three years, but I can't help without additional details (as per the feedback request). |