[6bone] freebsd src addr wrong

[Kimmo Suominen]

I've found that on a multihomed KAME (NetBSD) system the address
numerically closest to that of the destination would be used, at
least when all the egress interfaces (being tunnels) had no global
addresses.  I would have liked to be able to mark one address as
the primary to be used when a specific source address was not
explicitly requested by the application.

The workaround is not to use routers to talk to anyone...  :-)

+ Kim


| From:    Paul Timmins <paul@timmins.net>
| Date:    Wed, 11 Dec 2002 13:23:48 -0500
|
| At 11:36 AM 12/11/2002 -0500, you wrote:
| >I have a 6bone tunnel connection with a non-routed tunnel endpoint 2001::
| >address.  I also have an official 6bone 3ffe:: address, which is assigned
| >to one of my ether interfaces.
| >
| >When I "ping6 www.kame.net" I see that my side of the tunnel is used as a
| >source address.  I don't get ping responses back (presumably because
| >www.kame.net does not know where to send responses, given that the address
| >it is getting is not routed).
|
| What it is doing is correct, and all implementations do this. They take the
| IP address of the closest egress interface, being your tunnel.
|
| This is generally a good thing, as if you have a machine with a RFC-1918
| address on fxp0, and an internet wide interface on ppp0, you don't want to
| source packets out ppp0 with the IP address of fxp0. Put in this
| perspective, it makes more sense. :-)