if the provider chooses to use private adressing between some nodes, traceroute shows this, because traceroute uses information provided by the node itself, but ping is stopped far earlier by the first router which doesn't know a route to the address 10.x.x.x. i.e.: node 1 (pinger /tracerouter): 1.1.1.1 node 2 (1st router): 1.1.1.200 and 2.2.2.200 node 3 (2nd router / adsl dslam): 2.2.2.201 and 10.1.1.1 node 4 (3rd router / adsl modem): 10.1.1.2 and 3.3.3.3 node 5 (target): 3.3.3.4 Traceroute: - node 1 knows that everything except the local network is reachable through node 2 - node 2 knows that 3.3.3.x is reachable through node 3 (routing information received from node 3) - node 3 knows that 3.3.3.x is reachable through node 4 (routing information statically entered) - node 4 knows node 5 is connected directly Ping: - node 1 knows that everything except the local network is reachable through node 2 - node 2 DOESN'T know, how to reach 10.x.x.x because nobody told it a route (10.x.x.x routes are normally not advertised) does that help? greets, remo ---- Remo Pini Pini Computer Trading, Duebendorf remo.pini@pini.org
-----Original Message----- From: Togan Muftuoglu [mailto:toganm@users.sourceforge.net] Sent: Monday, June 18, 2001 7:07 PM To: Suse Security Subject: Re: [suse-security] private IP on the net ?
* Steffen Cluver;
on 18 Jun, 2001 wrote: Hi
212.204.100.1 recieved the host is unreachebal.
If that is the case how can they see it when they traceroute ?
-- Togan Muftuoglu
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com