Re: Confused tcpdump

From: Michael Proto <mike_at_jellydonut.org>
Date: Thu, 24 Sep 2009 13:50:46 -0400
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
Received on Thu Sep 24 2009 - 15:50:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:56 UTC