stop UDP from bringing up SLIP?

Thread View: comp.sys.next.sysadmin

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Derek Beatty Mon, 10 Aug 1992 13:49

#426

Author: Derek Beatty
Date: Mon, 10 Aug 1992 13:49

19 lines
1566 bytes

I'm using Mamakos' 920802 version of Dialupip to connect to campus through  
a Cisco ASM/3.  (So my default route points to this link.)  I'd like to  
stop SBook from bringing up the link, so I tried removing the word "udp"  
from the "protocols" line of my ".access" file. I thought this would  
suffice.  But now authough when I launch SBook a message like:
Aug  7 18:23:09 sqhilton tcldiald[115]: Unauthorized protocol UDP (17)
is logged via the syslog facility, as I expect, subsequent attempts to  
open TCP connections seem not to bring up the link automatically; instead,  
I have to use the duioctl to bring it up by hand. 

Would anyone who has succeeded in something like this be willing to share  
the secret?  What have I misunderstood about the access file?  Thanks.

PS: I'm not trying to outwit SBook's licensing scheme; it's just  
unreasonable to tie up a port on our Cisco whenever I run it.

--
Derek_Beatty@cs.cmu.edu (No NeXTmail! MIME Ok.)  PhD student  412 268-7898
Computer Science, Carnegie Mellon Univ., 5000 Forbes Ave, Pgh PA 15213 USA

Re: stop UDP from bringing up SLIP?

#711

Author: Louis A. Mamakos
Date: Thu, 13 Aug 1992 15:58

29 lines
2143 bytes

In article <1992Aug10.134954.266402@cs.cmu.edu> beatty@sqhilton.pc.cs.cmu.edu (Derek Beatty) writes:
>I'm using Mamakos' 920802 version of Dialupip to connect to campus through  
>a Cisco ASM/3.  (So my default route points to this link.)  I'd like to  
>stop SBook from bringing up the link, so I tried removing the word "udp"  
>from the "protocols" line of my ".access" file. I thought this would  
>suffice.  But now authough when I launch SBook a message like:
>Aug  7 18:23:09 sqhilton tcldiald[115]: Unauthorized protocol UDP (17)
>is logged via the syslog facility, as I expect, subsequent attempts to  
>open TCP connections seem not to bring up the link automatically; instead,  
>I have to use the duioctl to bring it up by hand. 

I think that I understand what is going one.  You have stumbled onto a
bug that goes something like this:

When an attempt is made to transmit a packet, a message is sent from
the kernel driver to the tcldiald process.  The SLIP interface is
marked as "bring-up in progress".  This prevents further messages from
being sent to the tcldiald process.  A timer is also started, by
default it is 5 minutes.  If nothing happens by then, then the
interface is cleared (actually, it may get disabled.. I'll have to
check).

In any case, since tcldiald refuses to bring up the link because its
not the right packet type, it ignores it and moves on.  It really
ought to reset the state of the interface and wait for further
attempts.  I will look at how difficult it might be to fix this to do
the right thing.

louie

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