Thread View: comp.sys.next.sysadmin
4 messages
4 total messages
Started by Brian Willoughby
Fri, 02 Oct 1992 20:12
SLIP doesn't like dialins on two different 3.0 systems
Author: Brian Willoughby
Date: Fri, 02 Oct 1992 20:12
Date: Fri, 02 Oct 1992 20:12
64 lines
3656 bytes
3656 bytes
I have a friend with a NeXTcube who I regularly make SLIP connections with (we both call each other, so the slip interface is set up for dial-in and dial-out). Back when he still had 2.1, I modified our routing tables to allow -NXHost over SLIP (and it worked with programs running on 2.1 and outputting PostScript to the machine running 3.0). Now that he has upgraded to 3.0 also, we both get the following message when logging into the SLIP account: Can't open TTY for "slip1" m Does anyone know what might cause this message? If I need to provide more configuration information, that can easily be supplied. Here are our tables: ------------------------- chernobog:brian> netstat -r Routing tables Destination Gateway Flags Refs Use Interface Schernobog localhost UH 0 0 lo0 localhost localhost UH 2 3421 lo0 sounds Ssounds UGH 0 20 slip1 nwpassage Schernobog UH 0 0 slip0 Ssounds Schernobog UH 0 0 slip1 default nwpassage UG 0 0 slip0 next-default chernobog U 7 84942 en0 chernobog:brian> netstat -rn Routing tables Destination Gateway Flags Refs Use Interface 192.135.191.105 127.0.0.1 UH 0 0 lo0 127.0.0.1 127.0.0.1 UH 2 3421 lo0 192.42.172.3 192.135.191.103 UGH 0 20 slip1 192.135.191.253 192.135.191.105 UH 0 0 slip0 192.135.191.103 192.135.191.105 UH 0 0 slip1 default 192.135.191.253 UG 0 0 slip0 192.42.172 192.42.172.1 U 7 84947 en0 ------------------------- sounds:brianw> netstat -r Routing tables Destination Gateway Flags Refs Use Interface chernobog Schernobog UGH 0 12 slip1 Schernobog Ssounds UH 0 0 slip1 localhost localhost UH 2 550 lo0 nwpassage Ssounds UH 0 24 slip0 Ssounds localhost UH 0 0 lo0 default nwpassage UG 0 0 slip0 next-default sounds U 9 1835 en0 sounds:brianw> netstat -rn Routing tables Destination Gateway Flags Refs Use Interface 192.42.172.1 192.135.191.105 UGH 0 12 slip1 192.135.191.105 192.135.191.103 UH 0 0 slip1 127.0.0.1 127.0.0.1 UH 2 550 lo0 192.135.191.253 192.135.191.103 UH 0 24 slip0 192.135.191.103 127.0.0.1 UH 0 0 lo0 default 192.135.191.253 UG 0 0 slip0 192.42.172 192.42.172.3 U 9 1840 en0 -- Brian Willoughby Software Design Engineer, BSEE NCSU BrianW@SoundS.WA.com Sound Signal Processing Software and Consulting NeXTmail welcome - NO EMAIL SOLICITATION without prior permission
Re: SLIP doesn't like dialins on two different 3.0 systems
Author: Louis A. Mamakos
Date: Sat, 03 Oct 1992 15:32
Date: Sat, 03 Oct 1992 15:32
17 lines
1154 bytes
1154 bytes
In article <BvIG4M.1wn@sounds.wa.com> BrianW@SoundS.WA.com writes: >Now that he has upgraded to 3.0 also, we both get the following message when >logging into the SLIP account: > >Can't open TTY for "slip1" m > >Does anyone know what might cause this message? First, take a look at the syslog file, and the "m" should have been replaced by an error message. Also, is the dudisc_slip1 program setuid to root? This message indicates an error attempting to open /dev/tty; I don't know for certain why this would be. Does the connection get made and does the SLIP interface (slip1) actually come up, even if not in a working state? louie
Re: SLIP doesn't like dialins on two different 3.0 systems
Author: Bill Chin
Date: Sun, 04 Oct 1992 14:52
Date: Sun, 04 Oct 1992 14:52
23 lines
1354 bytes
1354 bytes
In article <1992Oct3.153228.14683@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes: >In article <BvIG4M.1wn@sounds.wa.com> BrianW@SoundS.WA.com writes: >>Now that he has upgraded to 3.0 also, we both get the following message when >>logging into the SLIP account: >> >>Can't open TTY for "slip1" m >> >>Does anyone know what might cause this message? > >Does the connection get made and does the SLIP interface (slip1) >actually come up, even if not in a working state? > >louie Also make sure that NXFax isn't running - the way it takes over the serial ports conflicts with Transys SLIP (haven't tested it with Teleconnect). Bill Chin -- Bill Chin Internet & NeXTmail: PC/IP Group, Computer Science Center bchin@terminus.umd.edu University of Maryland, College Park *Standard Disclaimers Apply*
Re: SLIP doesn't like dialins on two different 3.0 systems
Author: felix.lugo
Date: Sun, 04 Oct 1992 15:47
Date: Sun, 04 Oct 1992 15:47
17 lines
1129 bytes
1129 bytes
In article <15880@umd5.umd.edu> bchin@is-next.umd.edu (Bill Chin) writes: > >Also make sure that NXFax isn't running - the way it takes over the serial ports >conflicts with Transys SLIP (haven't tested it with Teleconnect). > >Bill Chin > >-- >Bill Chin Internet & NeXTmail: >PC/IP Group, Computer Science Center bchin@terminus.umd.edu >University of Maryland, College Park *Standard Disclaimers Apply* Then, how come the combination NXFax/Transys SLIP (DialUpIP) work on my 3.0 system? His problem lies somewhere else, though I don't know where that might be! --Felix
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads