<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Very true - async 1/105 and tty 1/105 denote one and the same
modem/line/interface. The "line" data structure handles the
physical/character mode aspects of the line, and the "interface" data
structure handles the framed aspects of the connection (layer 2 framing
such as PPP/SLIP, layer 3 attributes such as IP.)<br>
<br>
Aaron<br>
<br>
<hr size="2" width="100%"><br>
<blockquote
cite="midOF9E8CAD20.A0B8ECBA-ON852571A9.006B33E2-852571A9.006C1AE6@yorku.ca"
type="cite"><br>
<font face="sans-serif" size="2">Hi,</font>
<br>
<font face="sans-serif" size="2"> A real quick question
to which I'm quite sure of the answer however I've been asked to
confirm.
When users dial into our 5350 modem pool with a script.....they
connect
to a tty, let's say 1/105, authenticate and then start up PPP which
'invokes'
(for lack of a better word ) int async 1/105. It appears that there
is a direct 1 to 1 correlation between ttys and async interfaces. So,
there's no chance that someone could connect to tty 1/102 and somehow
invoke
int async 2/98?..........right?........ie......if tty 1/103 is never
accessed
then int async 1/103 will never be used?</font>
<br>
<br>
<font face="sans-serif" size="2">........thanks in
advance................Jamie</font>
<br>
<br>
<font face="sans-serif" size="2">James Savage
York University <br>
Senior Communications Tech. 108 Steacie Building<br>
<a class="moz-txt-link-abbreviated" href="mailto:jsavage@yorku.ca">jsavage@yorku.ca</a>
4700 Keele Street<br>
ph: 416-736-2100 ext. 22605 Toronto,
Ontario<br>
fax: 416-736-5701
M3J 1P3, CANADA
</font>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-nas mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a>
</pre>
</blockquote>
<br>
</body>
</html>