Re: (PM) PM2E & 2ER POP

F. Michael Taylor (taylor@syrinx.jeffnet.org)
Tue, 23 Feb 1999 12:06:52 -0800 (PST)

On Tue, 23 Feb 1999, Jake Messinger wrote:
> On Tue, 23 Feb 1999, F. Michael Taylor wrote:
>
> > > Can the 2eR get out tot he rest of the world?
> >
> > Yes.
>
> Hrm, could be a problem in the 2e ethernet.
> Try these things when it cant touch the world:
>
> Can you ping IT from the 2eR or anything else on your net?

No.

> Can IT ping anything locally or is it just the default gateway that seems
> to be getting lost?
> Do a sho route on the pm2e to see what it shows you.
> set debug 0x51 and to a set console on the 2e and watch to see if you get
> any ethernet timeouts or bufffer overflows, etc...
>
Don't know how much of this is relevent, so you get it all. While
monitoring the 2E:

01 01 00 18 02 06 00 00 00 00 05 06 4c 17 Connection Failed
Sending LCP_CONFIGURE_REQUEST to port S13 of 24 bytes containing:
01 01 00 18 02 06 00 00 00 00 05 06 91 04 Connection Failed
Sending LCP_CONFIGURE_REQUEST to port S13 of 24 bytes containing:
01 01 00 18 02 06 00 00 00 00 05 06 2b 14 Connection

Connection Closed by forien host.

so I telnet in to the 2ER:
pm2> sh route
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
0.0.0.0 0 204.203.90.164 local NS 1 frmW1
204.203.88.104 32 204.203.89.2 rip HD 2 ether0
204.203.88.118 32 204.203.89.2 rip HD 2 ether0
204.203.88.108 32 204.203.89.2 rip HD 2 ether0
204.203.88.107 32 204.203.89.2 rip HD 2 ether0
204.203.88.122 32 204.203.89.2 rip HD 2 ether0
204.203.88.117 32 204.203.89.2 rip HD 2 ether0
204.203.88.126 32 204.203.89.2 rip HD O 16 ether0
204.203.88.116 32 204.203.89.2 rip HD 2 ether0
204.203.88.65 32 204.203.88.65 local HL 1 ptp1
204.203.90.254 32 204.203.90.164 rip HD 2 frmW1
204.203.90.33 32 204.203.90.164 rip HD 2 frmW1
204.203.90.164 32 204.203.90.165 local HS 1 frmW1
204.203.90.128 27 204.203.90.164 rip ND 2 frmW1
204.203.90.192 27 204.203.90.164 rip ND 2 frmW1
204.203.90.32 27 204.203.90.164 rip ND 2 frmW1
204.203.90.0 27 204.203.90.164 rip ND 2 frmW1
204.203.88.0 27 204.203.90.165 local NS 1 frmW1
204.203.90.160 27 204.203.90.165 local NL 1 frmW1
204.203.89.0 27 204.203.89.1 local NL 1 ether0
-- Press Return for More --
204.203.212.0 24 204.203.90.164 rip ND 3 frmW1
204.203.213.0 24 204.203.90.164 rip ND 2 frmW1
204.203.91.0 24 204.203.90.164 rip ND 2 frmW1
199.238.98.0 24 204.203.90.164 rip ND 2 frmW1
pm2> ping pm3
pm3 (204.203.89.2) is alive
pm2> telnet pm3
Trying 204.203.89.2 ...
Connected - Escape character is '^]'.

it locked up at this point, so I hit a control C and got a login prompt,
but it won't echo back characters.

I try to reset it thru a script and get lots of these.

n_newbuf: No available netbufs
f,
n_newbuf: No available netbufs
n_newbuf: No available netbufs
n_n

I think we are hittin' on something here....

Now I reboot it because customers are copmplaining.

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>