Ideas on identifying gateways

[Jeff Boles <bolesjb () yahoo com>]

List members:

Maybe this will make good thinking 'fodder' for some
of you.  I'm fishing for ideas on a problem
approach...

Currently struggling with needing to go into an
environment completely blind except for IP space and
physical access, and identifying/auditing potential
gateways / circuits to other networks.  I'll call any
circuit connecting to this network from another a
gateway.  There is no concrete knowledge in this
environment of gateways or circuits, and equipment
supporting connectivity may not be visible or
locatable.  I cannot rely conclusively on the
possibility of actively running routing protocols,
cdp, or other protocol support.  Potential circuits
may not be actively routing traffic (i.e. no traffic
to the destination on the other end) but might still
serve as a point of entry.  Long history of just
hooking stuff together, by lots of different folks.

Although I'm just getting started really thinking
about this, my current approach will consist mostly of
sniffing traffic for oddities and router behavior,
digging through what router configs I can identify and
get into, and fingerprinting systems in the main IP
space.  

Any comments or thoughts on different approaches? 
Trying to rapidly foment ideas, so any input is
greatly appreciated.


__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
_______________________________________________
firewall-wizards mailing list
firewall-wizards () nfr com
http://list.nfr.com/mailman/listinfo/firewall-wizards