Re: dymanic route table problem
- From: "Brian E" <dirwolf@xxxxxxxxxxxxx>
- Date: Thu, 21 Sep 2006 12:15:38 -0400
Well that I can answer, each of the entries I see do correspond to a host within the outsourcing companies internal networks, jump stations used for administration, monitoring servers, so they are real.
The issue is that all unknown routes are supposed to be sent to the default gateway to let the core routers handle the flow of traffic.
There is no NAT or PAT happening here.
198.182.130.31
198.182.130.120
198.182.130.26
These are three I see consistently and all are valid internal hosts to the outsourcer.
And is only the systems that live on the same vlan that pix firewall for the outsourcer sits on , 167.126.101.101 is the internal interface for that device.
So the question again is how are these OS learning about routes when they should just send to the dgatway? :-)
"Phillip Windell" <@.> wrote in message news:ucW99PZ3GHA.3508@xxxxxxxxxxxxxxxxxxxxxxx
Pick a few machines that are doing this stuff,...sounds like it won't be
hard to find some.
Watch the route tables.
Record and inventory these routes from all the examined machines into a
Table (maybe Excel) like this:
NetID or Host Mask Gateway
Interface
198.182.130.120 255.255.255.255 167.126.101.101 167.126.101.25
After building up a list of them,. let's look for patterns or some kind of
consistancy between them. It is also important to note routes to individual
Hosts as opposed to routes to networks or subnets. Routes to Hosts will
use an "All 255" mask.We also need to ask if these routes actually represent
a true working path to the NetId or Host and if these NetIDs or Hosts
actually exist on your over-all network somewhere.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
- References:
- dymanic route table problem
- From: Brian E
- Re: dymanic route table problem
- From: Brian E
- Re: dymanic route table problem
- From: Kurt
- Re: dymanic route table problem
- From: Brian E
- dymanic route table problem
- Prev by Date: RE: Program Access
- Next by Date: Re: W2K repair
- Previous by thread: Re: dymanic route table problem
- Next by thread: Re: dymanic route table problem
- Index(es):
Relevant Pages
|
Loading