incorrect port value in tcpdump output

2009-03-31 Thread pluknet
Hi there. [I don't know if it was discussed already.] tcpdump'ed from RELENG_7, kernel and modules as of Mar 22 are in sync, world as of Mar 18. I caught this while building kernel via NFS. The subj host is an NFS server. 23:22:03.056098 IP (tos 0x0, ttl 64, id 26932, offset 0, flags [DF], prot

Re: incorrect port value in tcpdump output

2009-03-31 Thread Dan Nelson
In the last episode (Apr 01), pluknet said: > tcpdump'ed from RELENG_7, kernel and modules as of Mar 22 are in sync, > world as of Mar 18. > > I caught this while building kernel via NFS. The subj host is an NFS server. > > 23:22:03.056098 IP (tos 0x0, ttl 64, id 26932, offset 0, flags [DF], prot

Re: incorrect port value in tcpdump output

2009-03-31 Thread pluknet
2009/4/1 Dan Nelson : > In the last episode (Apr 01), pluknet said: >> tcpdump'ed from RELENG_7, kernel and modules as of Mar 22 are in sync, >> world as of Mar 18. >> >> I caught this while building kernel via NFS. The subj host is an NFS server. >> >> 23:22:03.056098 IP (tos 0x0, ttl 64, id 26932