Re: TCP_COMPAT_42 support

2006-05-04 Thread Julian H. Stacey
Mike Silbersack wrote: > > On Tue, 7 Mar 2006, Julian H. Stacey wrote: > > >> 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 differe

Re: TCP_COMPAT_42 support

2006-03-10 Thread Mike Silbersack
On Tue, 7 Mar 2006, Julian H. Stacey wrote: 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? Hmm. Thanks Mike, Until you wrote t

Re: TCP_COMPAT_42 support

2006-03-07 Thread Julian H. Stacey
> 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? Hmm. Thanks Mike, Until you wrote that I was thinking of install an old Free

Re: TCP_COMPAT_42 support

2006-03-07 Thread Mike Silbersack
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

Re: TCP_COMPAT_42 support

2006-02-28 Thread Julian H. Stacey
Hi Mike & net@ people, "Mike Silbersack" wrote: > > Thanks Mike, > > Well I fixed a local problem of parity on my FreeBSD end, by changing to > > XTerm*eightBitInput:False > > XTerm*eightBitOutput: False > > xrdb -merge ~/.Xdefaults > > But

Re: TCP_COMPAT_42 support

2006-02-28 Thread Mike Silbersack
> Thanks Mike, > Well I fixed a local problem of parity on my FreeBSD end, by changing to > XTerm*eightBitInput:False > XTerm*eightBitOutput: False > xrdb -merge ~/.Xdefaults > But rlogins & telnets to the 4.2BSD Symmetric still die af

Re: TCP_COMPAT_42 support

2006-02-28 Thread Julian H. Stacey
Mike Silbersack wrote: > On Mon, 27 Feb 2006, Julian Stacey wrote: > > Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ? > TCP_COMPAT_42 just tweaked how we generated TCP initial sequence numbers. > The lack of it should not be impacting your ability to connect to machines > of any vin

Re: TCP_COMPAT_42 support

2006-02-27 Thread Mike Silbersack
On Mon, 27 Feb 2006, Julian Stacey wrote: Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ? TCP_COMPAT_42 just tweaked how we generated TCP initial sequence numbers. The lack of it should not be impacting your ability to connect to machines of any vintage. Mike "Silby" Silbersa

TCP_COMPAT_42 support

2006-02-27 Thread Julian Stacey
Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ? I'm trying to connect to my Symmetric 375 ( An NSC 32016 running BSD 4.2 ), hardware by Bill Jollitz, 2M of main RAM, rather small kernel http://berklix.com/~jhs/symmetric/ & of course I dont have full sources, & the reconfig kernel kit