From: Lee, Vaughan (vaughan.lee@xxxxxxxxxxx)
Date: Mon May 15 2000 - 06:19:14 GMT-3
A way to may this process quicker is to define four subinterfaces, with a
different encapsulation and network number on each. Then run the debug and
see which subinterface gives the error messages - that's the one with the
right encapsulation, and the error message gives the correct network
address. It's then a simple case of deleting the subinterfaces and
redfining the main interface with correct parameters.
Regards,
Vaughan Lee
-----Original Message-----
From: Brad Ellis [mailto:ironbrad@WANgurus.com]
Sent: 15 May 2000 00:04
To: Asbjorn Hojmark; ccielab@groupstudy.com
Subject: Re: Finding IPX network and encap
Asbjorn,
I know what you're getting at, but I wasn't able to figure out another way
of doing it. It's a pain in the butt and it definitely takes a bit of time
(and patience) to get the right IPX encapsulation and network #.
-B
----- Original Message -----
From: "Asbjorn Hojmark" <Asbjorn@Hojmark.ORG>
To: <ccielab@groupstudy.com>
Sent: Sunday, May 14, 2000 6:02 PM
Subject: Finding IPX network and encap
> Can anyone think of a time-efficient way of finding the correct
> IPX network and encapsulation for an interface when this isn't
> given?
>
> The only way, I can think of, is configuring a network and doing
> 'debug ipx packet'. That way you'll see incoming IPX traffic and
> get the network number. But you'll still have to test all the
> different encapsulations.
>
> TIA,
> -A
> --
> Heroes: Vint Cerf & Bob Kahn, Leonard Kleinrock, Robert Metcalfe
> Links : http://www.hojmark.org/networking/
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:29 GMT-3