Date: Fri, 21 Aug 1998 18:34:37 +0200 (CEST) From: hm@kts.org (Hellmuth Michaelis) To: andreas.gaertner.gp@oen.siemens.de (Anderl) Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: tcpdump and isppp0 Message-ID: <m0z9u97-00001yC@bert.kts.org> In-Reply-To: <Pine.GSO.3.96.980820100654.12206k-200000@s71ee26> from Anderl at "Aug 20, 98 10:08:12 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Anderl wrote:
> now i wanted to check the traffic going over the interface using 'tcpdump
> -i isppp0'. everything seemed fine. i started up the connection, put
> tcpdump onto the interface to listen and did a ping to a remote site. i
> stopped the ping and since then weird packets were wandering from the
> remote site to my machine and vice versa and wouldn't stop. also inetd
> showed traffic. when i then terminated tcpdump all grew quiet again.
> connection was still up and no traffic went over the interface. so
> something (i assume tcpdump) must effect or even generate traffic over
> isppp0 even if there is none or supposed to be none. how can that be?
BPF support for the isppp driver is buggy or at least inconsistent (two
call to bpf_mtap() with different parameter passing).
Also there seemed to be a parameter passing change happened for bpf_mtap()
for FreeBSD-current.
Since i still don't use sppp and i don't run current, diffs are - as usual -
welcome ;-)
hellmuth
--
Hellmuth Michaelis hm@kts.org Hamburg, Europe
A duck is like a bicycle because they both have two wheels except the duck
(terry@cs.weber.edu)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0z9u97-00001yC>