[EMAIL PROTECTED] (Steve Dodd) wrote on 08.10.99 in
<[EMAIL PROTECTED]>:
> On Fri, Oct 08, 1999 at 12:41:00AM +0200, Kai Henningsen wrote:
>
> > It seems (correct me if I'm wrong) that there is no really "good" version
> > of tcpdump/libpcap that can deal with ISDN. There are various patches to
> > the [03].4a6 version floating around (though [03].4 final has been around
> > for quite some time), most of them trying to guess packet type by looking
> > at device names.
>
> I'm not an ISDN bod but I'll probably have some patches related to PPP stuff
> that I'll want to feed into tcpdump and libpcap -- are there active
> maintainers for those packages?
Well, there's a non-Linux upstream. But for Linux stuff, nobody seems to
be coordinating anything - everyone does their own patches, it seems. Over
an old alpha version, too.
> > Now, I gather that under 2.2, it's quite possible to find out exactly what
> > type of packet one has. However, I seem to have trouble finding any docs
> > on this.
>
> I don't know about ISDN, but I'm assuming you use PPP over it. When the
> packets hit pcap / tcpdump, do they have ISDN link info still on them or is
> it a raw PPP packet? What does the "Link encap" field of ifconfig output
> show for the device?
Point-to-Point Protocol. But ISDN encapsulation is weird. For syncppp at
least, it's different for incoming and outgoing packets, for example!
> There are many intelligent species in the universe. They all own
> cats.
They are all owned by cats, you mean. At least the one currently in my
window is going to seriously scold me when I go down to eat in a few
minutes.
MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
