[Bug 214482] [ports][net/mpd5] mpd5 fails to reset interfaces after L2TP fail.

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214482

            Bug ID: 214482
           Summary: [ports][net/mpd5] mpd5 fails to reset interfaces after
                    L2TP fail.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: mav at FreeBSD.org
          Reporter: dgilbert at eicat.ca
             Flags: maintainer-feedback?(mav at FreeBSD.org)
          Assignee: mav at FreeBSD.org

I run a moderately sized mpd installation servicing DSL clients.  They arrive,
of course, by L2TP.

A problem occurs when the L2TP tunnel is cutoff remotely.  Think fiber cut as
an example, but I also believe the far end L2TP speaker can go down without
cleaning up.

In this case, all the ngX interfaces stay "UP" and mpd5 will not terminate. 
Rebooting seems the only solution.  If I kill -9 the mpd process, it does die,
but the ngX interfaces remain as does all the other in-kernel netgraph.

When I see this happen, mpd5 is still transmitting l2tp packets to nowhere.  No
incoming l2tp packets... just ones leaving the machine.

1) There needs to be a way to tell mpd5 to clear out, returning all resources.

2) mpd5 should recognize the non-existance of the other end and act
accordingly.

-- 
You are receiving this mail because:
You are the assignee for the bug.