kernel panics in in_lltable_lookup (with INVARIANTS)

[Brian Somers]

On Fri, 21 Aug 2009 21:55:03 -0700 Brian Somers <brian at FreeBSD.org> wrote:
> On Fri, 21 Aug 2009 17:13:45 -0700 Kip Macy <kmacy at freebsd.org> wrote:
> > Try this:
> > 
> > Index: sys/net/flowtable.c
> > ===================================================================
> > --- sys/net/flowtable.c (revision 196382)
> > +++ sys/net/flowtable.c (working copy)
> > @@ -688,6 +688,12 @@
> >                 struct rtentry *rt = ro->ro_rt;
> >                 struct ifnet *ifp = rt->rt_ifp;
> > 
> > +               if (ifp->if_flags & IFF_POINTOPOINT) {
> > +                       RTFREE(rt);
> > +                       ro->ro_rt = NULL;
> > +                       return (ENOENT);
> > +               }
> > +
> >                 if (rt->rt_flags & RTF_GATEWAY)
> >                         l3addr = rt->rt_gateway;
> >                 else
> > 
> > You'll need to apply this by hand as gmail munges the formatting.
> > 
> > -Kip
> 
> Hi,
> 
> That certainly stops the panic, however data routed to the tun
> interface doesn't come out the back end and data written
> to the back end doesn't come out the tun interface.
[.....]
> Maybe this problem isn't a routing problem.  I'll
> look into it further and figure out if the packet is getting to the tun
> driver and if so, what it thinks it's doing with it.

I wasn't correct - the data *IS* being read out of the back of
the tunnel device.  When I send the ICMP, it goes into the tun
device and comes out the back end as an AF_LINK packet.  ppp
silently discards this (ironically I have a comment noting
that I should really track unidentified packet counts).

I'll try to figure out what in if_tun.c is corrupting the family next...

Cheers.

> > On Fri, Aug 21, 2009 at 16:43, Brian Somers<brian at freebsd.org> wrote:
> > > Hi,
> > >
> > > I've been working on a fix to address an issue that came up with
> > > our update of openssh-5.  The issue is that openssh-5 now uses
> > > pipe() to create stdin/stdout channels between sshd and the server
> > > side program where it used to use socketpair().  Because it uses
> > > pipe(), stdin is no longer bi-directional and cannot be used for both
> > > input and output by a child process.  This breaks the use of ssh
> > > as a tunnel with ppp on either end (set device "!ssh -e none host
> > > ppp -direct label")
> > >
> > > I talked with des@ for a while and then with the openssh folks and
> > > have not been able to resolve the issues in openssh that made them
> > > choose to enforce the use of pipe() over socketpair().  I now have a
> > > patch to ppp that makes ppp detect that it's connected via pipe() and
> > > causes it to use stdin for input and stdout for output (usually it expects
> > > just one descriptor).  Although I'm happy with the patch and planned on
> > > requesting permission to commit, I've bumped into a show-stopper
> > > that seems unrelated, so I thought I'd ask here if anyone has seen
> > > this or has any suggestions as to what the problem might be.
> > >
> > > The issue....
> > >
> > > I'm seeing a panic when I send traffic through a ppp link:
> > >
> > > panic string is: sin_family 18
> > > Stack trace starts:
> > >    in_lltable_lookup()
> > >    llentry_update()
> > >    flowtable_lookup()
> > >    ip_output()
> > >    ....
> > >
> > > The panic is due to a KASSERT in in_lltable_lookup() that expects the
> > > sockaddr to be AF_INET.  Number 18 is AF_LINK.
> > >
> > > AFAICT this is happening while setting up a temporary route for the
> > > first outbound packet.  I haven't been able to do much investigation
> > > yet due to other patches in my tree that seem to have broken all my
> > > kernel symbols, but once I get a clean rebuild I should be back in
> > > business.
> > >
> > > If anyone has any suggestions, I'm all ears!
> > >
> > > Cheers.

-- 
Brian Somers                                          <brian at Awfulhak.org>
Don't _EVER_ lose your sense of humour !               <brian at FreeBSD.org>