The route that your ping is going to traverse is going to
depend on which hop has the best metric.
If you want your ping to go to 150.3.53.3, then your last
static route should be:
ip route 204.0.0.0 255.0.0.0 150.3.53.3.
Never be afraid to try something new.
Remember, the Titanic was built
reload at 13:00 may 9
will schedule a reload at 1PM on May 9th.
-Original Message-
From: Larry Ogun-Banjo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 2:57 PM
To: [EMAIL PROTECTED]
Subject: Scheduled reload [7:3869]
Does anyone know if there is a command to boot/reload a
If your sniffer is a WAN sniffer, you could use a V35 Y cable between the
CSU and
the router. If it is a LAN sniffer, you will probably have to plug it into
the
hub or switch that your router connects to.
-Original Message-
From: Rizzo Damian [mailto:[EMAIL PROTECTED]]
Sent: Friday,
Are you and/or your vendor running NAT?
-Original Message-
From: SH Wesson [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 11:21 AM
To: [EMAIL PROTECTED]
Subject: PIX and sniffing [7:2265]
I have a pix that protects my internal network from vendors. So the
internal lan
A situation that I have run across is where you have a port speed that is 4
times your CIR and your carrier cuts you off at the egress port for all
packets over twice your CIR.
-Original Message-
From: EA Louie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 2:22 PM
To: [EMAIL
I believe when you add the 255 you are changing the administrative distance
to create a floating static route. If you had a route learned by EIGRP for
instance with an administrative distance of 90 and the floating static route
with a distance of 255, the route learned by EIGRP would be used
6 matches
Mail list logo