Confused tcpdump

Michael Proto mike at jellydonut.org
Thu Sep 24 18:12:16 UTC 2009


2009/9/24 Dag-Erling Smørgrav <des at des.no>:
> 15:50:42.622040 IP 10.0.0.10.871009576 > 10.0.0.4.2049: 192 lookup [|nfs]
> 15:50:42.622386 IP 10.0.0.4.2049 > 10.0.0.10.871009576: reply ok 236 lookup [|nfs]
>
> I'm pretty sure 871009576 is not a valid port number...
>
> DES
> --
> Dag-Erling Smørgrav - des at des.no
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>

I've noticed this behavior since at least 4.3 as well, with the source
port being some obscenely-high number, when examining UDP-based NFS
traffic with tcpdump (32bit).

Not chiming-in on validity one way or the other as its never really
bothered my troubleshooting to-date, but it has been there quite a
while.


-Proto


More information about the freebsd-net mailing list