On Tue, 28 Feb 2006, Julian H. Stacey wrote:
-------
& the only things I typed into that box were
rlogin skyr
ls
I had previously started in another xterm
tcpdump -v -i rl0 -l | grep skyr
& got this:
-------
20:49:03.103230 IP (tos 0x0, ttl 15, id 240, offset 0, flags [none], length: 40)
skyr.jhs.private.login > fire.jhs.private.978: F [tcp sum ok] 579:579(0) ack 25
win 0
20:49:03.103255 IP (tos 0x10, ttl 64, id 5009, offset 0, flags [DF], length: 40)
fire.jhs.private.978 > skyr.jhs.private.login: . [tcp sum ok] ack 580 win 65535
20:49:03.103712 IP (tos 0x10, ttl 64, id 5010, offset 0, flags [DF], length: 40)
fire.jhs.private.978 > skyr.jhs.private.login: F [tcp sum ok] 25:25(0) ack 580
win 65535
20:49:03.110660 IP (tos 0x0, ttl 15, id 241, offset 0, flags [none], length: 40)
skyr.jhs.private.login > fire.jhs.private.978: . [tcp sum ok] ack 26 win 0
Notes:
There's no tcpdump on my 4.2 box
skyr is the 4.2-BSD box
fire is the FreeBSD-5.3 box
high is just an alias in my named for 192.168.x.255
Could this problem be due to different broadcasting convetions for 4.2 & 4.4,
perhaps triggered by eg arpd or named etc doing discovery every minute or so ?
(But FreeBSD worked for years OK to that 4.2-BSD, & I recall all FreeBSD are
4.4)
Looks to me like skyr decided to close the connection, and it closed as
expected. I think the problem is probably above the TCP layer - have you
tried an older version of rlogin to see if that makes a difference?
Sorry about the delay in responding to this, I got sidetracked, and then I
got a cold. :)
Mike "Silby" Silbersack
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
