November 1999 - USR-TC - mailman.xmission.com

RE: (usr-tc) clean up processes on HARC
by Stainforth, Matthew 24 Nov '99

24 Nov '99

okay, no big deal. You can still monitor the user using the interface slot:x/mod:y rather than the username. It just takes longer is all. > -----Original Message----- > From: Mike Wronski [mailto:mike@coredump.ae.usr.com] > Sent: Wednesday, November 24, 1999 5:43 PM > To: usr-tc(a)lists.xmission.com > Subject: RE: (usr-tc) clean up processes on HARC > > > > > |-----Original Message----- > |From: owner-usr-tc(a)lists.xmission.com > |[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of > Stainforth, Matthew > |Sent: Wednesday, November 24, 1999 3:23 PM > |To: 'usr-tc(a)lists.xmission.com' > |Subject: RE: (usr-tc) clean up processes on HARC > | > | > |> -----Original Message----- > |> From: Mike Wronski [mailto:mike@coredump.ae.usr.com] > |> > |> |312004 CLI 312004 Application Inactive > |> |322003 CLI 322003 Application Inactive > |> |332008 PPP Monitor 332008 Application Inactive > |> | > |> > |> try "KILL \"PPP Monitor 332008\"".. Your milage may vary.. > |> Are you sure you > |> dont have an other open telnet session that still has the > PPP monitor > |> running.. I see alot of CLI processes.. > | > |oh yes, I'm quite sure those are not legitimate sessions. > The kill command > |didn't get rid of the monitor either. Any other suggestions? > > I dont think you have any other option here.. A reboot seems > to be the only > option.. I will see if we can get some patches in future code > to prevent > this from happening.. > > -M > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

(usr-tc) clean up processes on HARC
by Stainforth, Matthew 24 Nov '99

24 Nov '99

How does one clean up old stale processes on the HARC? Something is preventing me from doing: Enter the user name to monitor below: Press Escape to return to the previous screen. Press Enter/Return to enter the name. User Name: [xyzzy ] Monitoring user xyzzy. Some other process is tracing the user "xyzzy". Only one process may trace a user at a time. I think there is a stale process causing this...a list proc shows: 2b2001 CLI Application Inactive 2d2007 CLI 2d2007 Application Inactive 2e2008 CLI 2e2008 Application Inactive 2f2014 CLI 2f2014 Application Inactive 30200c CLI 30200c Application Inactive 312004 CLI 312004 Application Inactive 322003 CLI 322003 Application Inactive 332008 PPP Monitor 332008 Application Inactive among other things. Is there any way to clean this up aside from rebooting the whole HARC? It's V4.1.59-6 if that makes any difference. Matthew Stainforth || Technical Services Manager || BrunNet Inc. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

RE: (usr-tc) Dropped connections for 2nd login with same login ID . MPPP weird thing?
by Scott Trautman 24 Nov '99

24 Nov '99

USER_DEFAULT Password = "TUH3UyS3x6a0.", Expiration = "Feb 18 1999" Idle-Timeout = 1200, User-Service-Type = Framed-User, Framed-Protocol = PPP, Framed-Address = 255.255.255.254, Framed-MTU = 1500, Framed-Routing = None # standish 10/17/96 10:41 Pstandish Crypt-Password = "GENOWAYMANspU" Framed-Filter-Id = std SMT -----Original Message----- From: Brian [mailto:signal@shreve.net] Sent: Wednesday, November 24, 1999 11:43 AM To: 'usr-tc(a)lists.xmission.com' Cc: Scott Trautman; 'paul_steffen(a)planar.com' Subject: RE: (usr-tc) Dropped connections for 2nd login with same login ID . MPPP weird thing? Scott, Post us this users radius config, or if they don't have a radius config, post us your default config. Like krish says chances are you have port-limit or max-channels settings going on that are causing this problem. Brian On Tue, 23 Nov 1999, Tatai SV Krishnan wrote: > On Wed, 24 Nov 1999, Scott Trautman wrote: > > > You've identified the essential problem. No, this <client> ISN'T trying to > > negotiate a multilink connection. Win95 client dialing, doesn't seem to > > matter what client dials, same result. IE, no the client isn't attempting to > > bond with another connection. > > Win 95 is capable of doing multilink - so it can negotiate, this normal, > then rejecting this option is fine. However if a user with the same name > is logged in and another user using the same name but from a different > machine is trying to login and he fails - that problem would mean that > either you have port limit or max-channels setup for the user or the > default user. > > > > > It's picking up on something that makes it think this is a 2nd channel in a > > multilink connection, and that's not correct at all! > > > > NO its not picking up anything, it clearly rejected multilink and told > the hiper arc that it cannot do multilink, thats fine. The rejection of > the call was not present in the ppp trace. So first check if the user > has any port limit or any max-channel setup on this hiper arc - if you > the call drop is valid. > > krish > > > SMT > > > > -----Original Message----- > > From: Tatai SV Krishnan [mailto:tkrishna@bubba.ae.usr.com] > > Sent: Tuesday, November 23, 1999 10:23 PM > > To: Scott Trautman > > Cc: 'usr-tc(a)lists.xmission.com'; 'paul_steffen(a)planar.com' > > Subject: RE: (usr-tc) Dropped connections for 2nd login with same login > > ID . MPPP weird thing? > > > > > > On Wed, 24 Nov 1999, Scott Trautman wrote: > > > > > Okay, hup two three four ppp mon on your door. > > > > > > slot:14/mod:21 is the Pstandish session in question. > > > No data from slot:14/mod:5, which is the Pstandish already on. > > > slot:4/mod:3 I believe you can ignore. > > > > > > SMT > > > > > > > > > HiPer PPP Monitor > > > > > > Select a letter for one of the following options: > > > C) Monitor PPP Call Events. > > > I) Monitor a specific interface. > > > N) Monitor the next session that starts up. > > > U) Monitor a specific user. > > > X) Exit the monitor. > > > Please Enter Your Choice :N > > > Monitoring the next session to start up. > > > Decode tracing started, press ESCAPE to stop; press X for hex tracing. > > > > > > Outgoing PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REQ MRU 05 ea > > > ASYNC_MAP 00 00 00 00 > > > AUTH_TYPE c0 23 > > > MAGIC_NUM 43 ea d3 f3 > > > PROTO_COMP > > > AC_COMP > > > MPP_MRRU 05 ea > > > MPP_ENDPTID 03 00 c0 49 11 58 64 > > > > > > Incoming PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REQ ASYNC_MAP 00 0a 00 00 > > > MAGIC_NUM 09 f5 c0 31 > > > PROTO_COMP > > > AC_COMP > > > CALLBACK 06 > > > > > > Outgoing PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REJ CALLBACK 06 > > > > > > Incoming PPP Data on interface: slot:4/mod:3 > > > CTCP_DATA ff 03 00 2d 64 05 ac 04 00 04 30 00 01 00 > > > > > > Incoming PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REQ ASYNC_MAP 00 0a 00 00 > > > MAGIC_NUM 09 f5 c0 31 > > > PROTO_COMP > > > AC_COMP > > > > > > Outgoing PPP Data on interface: slot:14/mod:21 > > > LCP CFG_ACK ASYNC_MAP 00 0a 00 00 > > > MAGIC_NUM 09 f5 c0 31 > > > PROTO_COMP > > > AC_COMP > > > > > > LCP CFG_REQ MRU 05 ea > > > ASYNC_MAP 00 00 00 00 > > > AUTH_TYPE c0 23 > > > MAGIC_NUM 43 ea d3 f3 > > > PROTO_COMP > > > AC_COMP > > > MPP_MRRU 05 ea > > > MPP_ENDPTID 03 00 c0 49 11 58 64 > > > > > > ... > > > > > > Incoming PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REJ MPP_MRRU 05 ea > > > MPP_ENDPTID 03 00 c0 49 11 58 64 > > > > So here you client has rejected Multilink -- Why? > > > > > > Outgoing PPP Data on interface: slot:14/mod:21 > > > LCP CFG_REQ MRU 05 ea > > > ASYNC_MAP 00 00 00 00 > > > AUTH_TYPE c0 23 > > > MAGIC_NUM 43 ea d3 f3 > > > PROTO_COMP > > > AC_COMP > > > > Thus it is not a multilink call any more. > > > > Are you trying to have this connection as Multilink ? If so the client > > has rejected the same above. > > > > krish > > > > > > > > Incoming PPP Data on interface: slot:4/mod:3 > > > CTCP_DATA ff 03 00 2d 64 08 b2 e2 00 04 30 00 01 00 > > > > > > Incoming PPP Data on interface: slot:14/mod:21 > > > LCP CFG_ACK MRU 05 ea > > > ASYNC_MAP 00 00 00 00 > > > AUTH_TYPE c0 23 > > > MAGIC_NUM 43 ea d3 f3 > > > PROTO_COMP > > > AC_COMP > > > > > > Incoming PPP Data on interface: slot:14/mod:21 > > > PAP REQUEST USERNAME = Pstandish > > > PASSWORD = ******* (was unencrypted and > > > correct) > > > Outgoing PPP Data on interface: slot:4/mod:3 > > > IP_DATA 45 00 02 40 39 d2 00 00 30 06 ac 6b 98 a3 b4 19 9c 2e b9 8f > > > ... > > > > > > Outgoing PPP Data on interface: slot:4/mod:3 > > > IP_DATA 45 00 02 40 39 d3 00 00 30 06 ac 6a 98 a3 b4 19 9c 2e b9 8f > > > ... > > > > > > Outgoing PPP Data on interface: slot:4/mod:3 > > > IP_DATA 45 00 02 40 39 d4 00 00 30 06 ac 69 98 a3 b4 19 9c 2e b9 8f > > > ... > > > > > > Outgoing PPP Data on interface: slot:14/mod:21 > > > PAP ACK > > > Incoming PPP Data on interface: slot:4/mod:3 > > > CTCP_DATA ff 03 00 2d 64 08 b0 ca 00 02 18 00 01 00 > > > > > > - > > > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > > > with "unsubscribe usr-tc" in the body of the message. > > > For information on digests or retrieving files and old messages send > > > "help" to the same address. Do not use quotes in your message. > > > > > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > ----------------------------------------------------- Brian Feeny (BF304) signal(a)shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

RE: (usr-tc) Dropped connections for 2nd login with same login ID . MPPP weird thing?
by Scott Trautman 24 Nov '99

24 Nov '99

You've identified the essential problem. No, this <client> ISN'T trying to negotiate a multilink connection. Win95 client dialing, doesn't seem to matter what client dials, same result. IE, no the client isn't attempting to bond with another connection. It's picking up on something that makes it think this is a 2nd channel in a multilink connection, and that's not correct at all! SMT -----Original Message----- From: Tatai SV Krishnan [mailto:tkrishna@bubba.ae.usr.com] Sent: Tuesday, November 23, 1999 10:23 PM To: Scott Trautman Cc: 'usr-tc(a)lists.xmission.com'; 'paul_steffen(a)planar.com' Subject: RE: (usr-tc) Dropped connections for 2nd login with same login ID . MPPP weird thing? On Wed, 24 Nov 1999, Scott Trautman wrote: > Okay, hup two three four ppp mon on your door. > > slot:14/mod:21 is the Pstandish session in question. > No data from slot:14/mod:5, which is the Pstandish already on. > slot:4/mod:3 I believe you can ignore. > > SMT > > > HiPer PPP Monitor > > Select a letter for one of the following options: > C) Monitor PPP Call Events. > I) Monitor a specific interface. > N) Monitor the next session that starts up. > U) Monitor a specific user. > X) Exit the monitor. > Please Enter Your Choice :N > Monitoring the next session to start up. > Decode tracing started, press ESCAPE to stop; press X for hex tracing. > > Outgoing PPP Data on interface: slot:14/mod:21 > LCP CFG_REQ MRU 05 ea > ASYNC_MAP 00 00 00 00 > AUTH_TYPE c0 23 > MAGIC_NUM 43 ea d3 f3 > PROTO_COMP > AC_COMP > MPP_MRRU 05 ea > MPP_ENDPTID 03 00 c0 49 11 58 64 > > Incoming PPP Data on interface: slot:14/mod:21 > LCP CFG_REQ ASYNC_MAP 00 0a 00 00 > MAGIC_NUM 09 f5 c0 31 > PROTO_COMP > AC_COMP > CALLBACK 06 > > Outgoing PPP Data on interface: slot:14/mod:21 > LCP CFG_REJ CALLBACK 06 > > Incoming PPP Data on interface: slot:4/mod:3 > CTCP_DATA ff 03 00 2d 64 05 ac 04 00 04 30 00 01 00 > > Incoming PPP Data on interface: slot:14/mod:21 > LCP CFG_REQ ASYNC_MAP 00 0a 00 00 > MAGIC_NUM 09 f5 c0 31 > PROTO_COMP > AC_COMP > > Outgoing PPP Data on interface: slot:14/mod:21 > LCP CFG_ACK ASYNC_MAP 00 0a 00 00 > MAGIC_NUM 09 f5 c0 31 > PROTO_COMP > AC_COMP > > LCP CFG_REQ MRU 05 ea > ASYNC_MAP 00 00 00 00 > AUTH_TYPE c0 23 > MAGIC_NUM 43 ea d3 f3 > PROTO_COMP > AC_COMP > MPP_MRRU 05 ea > MPP_ENDPTID 03 00 c0 49 11 58 64 > > ... > > Incoming PPP Data on interface: slot:14/mod:21 > LCP CFG_REJ MPP_MRRU 05 ea > MPP_ENDPTID 03 00 c0 49 11 58 64 So here you client has rejected Multilink -- Why? > > Outgoing PPP Data on interface: slot:14/mod:21 > LCP CFG_REQ MRU 05 ea > ASYNC_MAP 00 00 00 00 > AUTH_TYPE c0 23 > MAGIC_NUM 43 ea d3 f3 > PROTO_COMP > AC_COMP Thus it is not a multilink call any more. Are you trying to have this connection as Multilink ? If so the client has rejected the same above. krish > > Incoming PPP Data on interface: slot:4/mod:3 > CTCP_DATA ff 03 00 2d 64 08 b2 e2 00 04 30 00 01 00 > > Incoming PPP Data on interface: slot:14/mod:21 > LCP CFG_ACK MRU 05 ea > ASYNC_MAP 00 00 00 00 > AUTH_TYPE c0 23 > MAGIC_NUM 43 ea d3 f3 > PROTO_COMP > AC_COMP > > Incoming PPP Data on interface: slot:14/mod:21 > PAP REQUEST USERNAME = Pstandish > PASSWORD = ******* (was unencrypted and > correct) > Outgoing PPP Data on interface: slot:4/mod:3 > IP_DATA 45 00 02 40 39 d2 00 00 30 06 ac 6b 98 a3 b4 19 9c 2e b9 8f > ... > > Outgoing PPP Data on interface: slot:4/mod:3 > IP_DATA 45 00 02 40 39 d3 00 00 30 06 ac 6a 98 a3 b4 19 9c 2e b9 8f > ... > > Outgoing PPP Data on interface: slot:4/mod:3 > IP_DATA 45 00 02 40 39 d4 00 00 30 06 ac 69 98 a3 b4 19 9c 2e b9 8f > ... > > Outgoing PPP Data on interface: slot:14/mod:21 > PAP ACK > Incoming PPP Data on interface: slot:4/mod:3 > CTCP_DATA ff 03 00 2d 64 08 b0 ca 00 02 18 00 01 00 > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

3 2

(usr-tc) Three IPs on a dialup?
by Stephen Amadei 24 Nov '99

24 Nov '99

Hi ya guys... I have a customer who wants three IPs on a dialup. I am thinking this cannot be done with a dialup on a USR TC, Hiper or not, but in an attempt to satisify my morbid sense of trivia... How can a dialup line be set up with three IP addreses routed over it? Needless to say, I suggested they use NAT... Anyway, thanks in advance... ----Steve Stephen Amadei Director of MIS Dandy Connections, Inc. Atlantic City, NJ - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

4 6

RE: (usr-tc) Dropped connections for 2nd login with same login ID . MPPP weird thing?
by Scott Trautman 24 Nov '99

24 Nov '99

Okay, hup two three four ppp mon on your door. slot:14/mod:21 is the Pstandish session in question. No data from slot:14/mod:5, which is the Pstandish already on. slot:4/mod:3 I believe you can ignore. SMT HiPer PPP Monitor Select a letter for one of the following options: C) Monitor PPP Call Events. I) Monitor a specific interface. N) Monitor the next session that starts up. U) Monitor a specific user. X) Exit the monitor. Please Enter Your Choice :N Monitoring the next session to start up. Decode tracing started, press ESCAPE to stop; press X for hex tracing. Incoming PPP Data on interface: slot:4/mod:3 UTCP_DATA ff 03 00 2f 45 00 00 28 cc 0f 40 00 80 05 c3 35 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 UTCP_DATA ff 03 00 2f 45 00 00 28 cd 0f 40 00 80 05 c2 35 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 a5 93 40 00 f1 06 78 a8 cf c8 46 0d 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 ce 0f 00 00 80 06 01 2d 9c 2e b9 8f cf c8 46 0d ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 a5 94 40 00 f1 06 78 b0 cf c8 46 04 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 04 eb 19 01 00 12 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 a5 95 40 00 f1 06 76 97 cf c8 46 04 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 05 b0 34 00 04 ed 00 03 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 a5 96 40 00 f1 06 76 96 cf c8 46 04 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 a5 97 40 00 f1 06 76 95 cf c8 46 04 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:14/mod:21 LCP CFG_REQ MRU 05 ea ASYNC_MAP 00 00 00 00 AUTH_TYPE c0 23 MAGIC_NUM 43 ea d3 f3 PROTO_COMP AC_COMP MPP_MRRU 05 ea MPP_ENDPTID 03 00 c0 49 11 58 64 Incoming PPP Data on interface: slot:14/mod:21 LCP CFG_REQ ASYNC_MAP 00 0a 00 00 MAGIC_NUM 09 f5 c0 31 PROTO_COMP AC_COMP CALLBACK 06 Outgoing PPP Data on interface: slot:14/mod:21 LCP CFG_REJ CALLBACK 06 Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 05 ac 04 00 04 30 00 01 00 Incoming PPP Data on interface: slot:14/mod:21 LCP CFG_REQ ASYNC_MAP 00 0a 00 00 MAGIC_NUM 09 f5 c0 31 PROTO_COMP AC_COMP Outgoing PPP Data on interface: slot:14/mod:21 LCP CFG_ACK ASYNC_MAP 00 0a 00 00 MAGIC_NUM 09 f5 c0 31 PROTO_COMP AC_COMP Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 a5 98 40 00 f1 06 76 94 cf c8 46 04 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 d2 0f 40 00 80 06 bd 35 9c 2e b9 8f cf c8 46 04 ... Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 30 d3 0f 40 00 80 06 85 3d 9c 2e b9 8f 98 a3 b4 19 ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 05 a9 ec 00 02 18 00 03 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 2c b3 62 00 00 30 06 34 ef 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 UTCP_DATA ff 03 00 2f 45 00 00 28 d5 0f 40 00 80 02 83 45 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 70 02 f7 02 00 01 00 47 45 54 20 2f 68 74 6d 6c ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 b3 b5 00 00 30 06 32 88 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 6c 02 67 8c 00 02 18 00 02 06 00 01 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 01 2d b4 15 00 00 30 06 33 3b 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 d8 0f 40 00 80 06 80 45 9c 2e b9 8f 98 a3 b4 19 ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 b4 61 00 00 30 06 33 f4 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 6e 02 67 8a 00 fe fb 00 01 06 01 00 02 00 Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 30 da 0f 40 00 80 06 7e 3d 9c 2e b9 8f 98 a3 b4 19 ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 2c 37 81 00 00 30 06 b0 d0 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 UTCP_DATA ff 03 00 2f 45 00 00 28 db 0f 40 00 80 08 7d 45 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 70 08 80 18 00 01 00 47 45 54 20 2f 63 6f 6e 74 ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 37 d4 00 00 30 06 ae 69 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 6c 08 c1 8a 00 02 18 00 01 c6 00 01 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 38 5b 00 00 30 06 ad e2 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 38 5c 00 00 30 06 ad e1 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 08 bd 5a 00 04 30 00 01 00 Incoming PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 00 28 df 0f 40 00 80 06 b0 35 9c 2e b9 8f cf c8 46 04 ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 38 c9 00 00 30 06 ad 74 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 38 ca 00 00 30 06 ad 73 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 38 cb 00 00 30 06 ad 72 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 08 b9 2a 00 04 30 00 02 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 43 00 00 30 06 ac fa 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 44 00 00 30 06 ac f9 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 45 00 00 30 06 ac f8 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:14/mod:21 LCP CFG_REQ MRU 05 ea ASYNC_MAP 00 00 00 00 AUTH_TYPE c0 23 MAGIC_NUM 43 ea d3 f3 PROTO_COMP AC_COMP MPP_MRRU 05 ea MPP_ENDPTID 03 00 c0 49 11 58 64 Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 08 b7 12 00 02 18 00 01 00 Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 9a 00 00 30 06 ac a3 98 a3 b4 19 9c 2e b9 8f ... Incoming PPP Data on interface: slot:14/mod:21 LCP CFG_REJ MPP_MRRU 05 ea MPP_ENDPTID 03 00 c0 49 11 58 64 Outgoing PPP Data on interface: slot:14/mod:21 LCP CFG_REQ MRU 05 ea ASYNC_MAP 00 00 00 00 AUTH_TYPE c0 23 MAGIC_NUM 43 ea d3 f3 PROTO_COMP AC_COMP Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 08 b2 e2 00 04 30 00 01 00 Incoming PPP Data on interface: slot:14/mod:21 LCP CFG_ACK MRU 05 ea ASYNC_MAP 00 00 00 00 AUTH_TYPE c0 23 MAGIC_NUM 43 ea d3 f3 PROTO_COMP AC_COMP Incoming PPP Data on interface: slot:14/mod:21 PAP REQUEST USERNAME = Pstandish PASSWORD = ******* (was unencrypted and correct) Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 d2 00 00 30 06 ac 6b 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 d3 00 00 30 06 ac 6a 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:4/mod:3 IP_DATA 45 00 02 40 39 d4 00 00 30 06 ac 69 98 a3 b4 19 9c 2e b9 8f ... Outgoing PPP Data on interface: slot:14/mod:21 PAP ACK Incoming PPP Data on interface: slot:4/mod:3 CTCP_DATA ff 03 00 2d 64 08 b0 ca 00 02 18 00 01 00 - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

3 2

RE: (usr-tc) Three IPs on a dialup?
by James Cook 24 Nov '99

24 Nov '99

Nope, you need to add a static route in your main router to point to (I'm assuming here) your HiperARC. Next add a route in the HiperARC to send traffic for that subnet to whatever address the user's equipment has when they are dialed in. They will need a static IP address for this to work properly which may be assigned via RADIUS. We used to offer this service over dial-up but found it problematic at best. Hope this helps . . . ======================= James M. Cook Net Resource 603.629.9008x302 Fax: 603.629.9749 james(a)net-resource.com -----Original Message----- From: Stephen Amadei [mailto:amadei@dandy.net] Sent: Wednesday, November 24, 1999 4:32 AM To: usr-tc(a)lists.xmission.com Subject: Re: (usr-tc) Three IPs on a dialup? On Wed, 24 Nov 1999, Mike Andrews wrote: > Route a /29 subnet to them, which is the smallest block that'll give them > at least 3 usable addresses. (8 addresses, 6 usable.) O.K... I guess I can do this through RADIUS, right? Now, subnetting below /24 has always been a weak point for me... and I realise I'm going a bit off topic, but I figure everyone on this list are about as knowledgable in subnetting as I'm going to find. I understand the basic tables of subnets and masks for under a class C. But I have two questions on how to use them. First, lets say I give this dialup a network of 192.168.1.0/29 (assuming 192.168.1.0/24 is a normal, routable class C). The net number is .0 and the broadcast is .7. What I don't understand next is what to do with the rest of the addresses. Can I dump the rest of the addresses onto an existing segment of my network that currently has a class C on it? Would I do it like the following? Internet----Router(200.200.200.1) | ____________ Main Network 200.200.200.0/24 192.168.1.8/29 192.168.1.16/28 192.168.1.32/27 192.168.1.64/26 192.168.1.128/25 ____________ | ____________ Total Control (normally gives out IPs from a pool in 200.200.200.0/24 Gives out a 192.168.1.0/29 ____________ Next, I don't quite understand where I need to apply static routes. I assume I would need to add a static route on the TC for the subnet I give the dialup, but would that subnet also require a routing entry on my router, except for the obvious need for a 192.168.1.0/24 route? Confused... but thanx in advance... ----Steve Stephen Amadei Director of MIS Dandy Connections, Inc. Atlantic City, NJ - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

(usr-tc) DNIS from an 800 number
by Brian 24 Nov '99

24 Nov '99

We have an 800 number that is forwarded to our main dialup pool number, so that users can use 800 service when they are out of town. We would like to capture DNIS for the 800 number in RADIUS so that we can bill accordingly. Currently when someone dials the main number (not 800 number) we get DNIS. When someone dials the 800 number, we do not get DNIS information of any kind. Is it possible to get DNIS information from this 800 number? Brian ----------------------------------------------------- Brian Feeny (BF304) signal(a)shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

5 6

(usr-tc) IP filter example
by Brian 24 Nov '99

24 Nov '99

I am wanting to filter outbound traffic from my users so that my core is protected (only allow http to webserver, smtp/pop to mail server, dns to nameserver, no telnet, etc)............... If anyone has an example IP filter that would be really cool, so I could have something to work off of. Also if you could show me how you applied it to users in RADIUS that would be good too. Appreciate it, Brian ----------------------------------------------------- Brian Feeny (BF304) signal(a)shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

RE: (usr-tc) TCH Reboot will cause T1 service outage
by Stainforth, Matthew 24 Nov '99

24 Nov '99

I have seen this with our telco but only after the carrier has been down for a number of minutes. You might want to inquire whether they can change this setting on their end to increase the time period before the switch turns down the trunks. > -----Original Message----- > From: mft [SMTP:tsaim@mft.com] > Sent: Tuesday, November 23, 1999 9:22 AM > To: usr-tc(a)lists.xmission.com > Subject: (usr-tc) TCH Reboot will cause T1 service outage > > Hi All, > > I have a problem w/ our T1-PRI carrier and I don't know how to > tell them to let them realize that they can help. > > Every time we "reboot" the TCH box, the phone line become > not in service. "Busy" tone will appear , after the reboot, when > user dial into it. > > This was not the case in the past. But recently the reboot will > cause this problem. And the only way to resove it is > to call the carrier's NPC and give they the circuit/trunk group number > and ask them to restore the service, because it is "blocked" in their > term. > > Does, any one know this is our TCH problem or is it the carrier's > circuit setup issue ? > > Thank in adv. > > Meng Tsai > tsaim(a)mft.com > ----- Original Message ----- > From: Jeff Mcadams <jeffm(a)iglou.com> > To: <usr-tc(a)lists.xmission.com> > Sent: Tuesday, November 23, 1999 7:39 AM > Subject: Re: (usr-tc) NIC and NAC install > > > > Thus spake Sheldon Koehler > > >I have a simple question, when installing a card set in a hot chassis, > do > > >you install the MIC or NAC first? > > > > NIC first, always. :) > > -- > > Jeff McAdams Email: jeffm(a)iglou.com > > Head Network Administrator Voice: (502) 966-3848 > > IgLou Internet Services (800) 436-4456 > > > > - > > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > > with "unsubscribe usr-tc" in the body of the message. > > For information on digests or retrieving files and old messages send > > "help" to the same address. Do not use quotes in your message. > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0