Please help: ptp links addresses

  > Robert Martin-Legene <robert at DK.net> writes:
  > 
  > Because the address of the router in a traceroute then might be private
  > address space one. I sort of like the idea that you know where in the
  > world you are when you do a traceroute.

While this is nice but there may be a tradeoff here. 

If the address space for links and router interfaces is used
efficiently, this is very nice to have. 

However some people for convenience or other reasons want to burn a lot
of address space inefficiently -/24 subnets for 2 interfaces come to
mind.  In this case they are welcome to use private address space.  One
of the prices they pay is the tradcerooute problem; another is that they
are not able to address spaceific interfaces directly from the Internet.
Some tell us that this is a feature and not a bug ;-). 

As always there is no answer/soloution that fits everyone. 

Also note that even for private address space traceroute will return the
address correctly, so the diagnostics are useful.  There just are no
names. If the border gateways with publicly adressed interfaces has a
reasonable name such as 'bordergw-xxx.clever.net' 'clever-gw.customer.nl'
it is quite clear "where you are" in between.

  > If the interface has a hidden IP# that you can send packets to, but it
  > still will present itself as (for instance) the ethernet interface, you
  > just give the ethernet interface a "normal" IP# and all looks normal and
  > the router only takes up one IP# (not counting RFC1918 address space)
  > This way you can still ping the interface on 10.0.0.1 .

I am not sure I grok that.

Daniel