On Mon, Apr 2, 2012 at 5:28 AM, Peter Eckel lists@eckel-edv.de wrote:
Routing tables won't do much for you when you have several different IP addresses (stateless autocnfigured, privacy extension and static) within the same network on the same physical interface - they'll all use the same route. The longest match algorithm would more or less lead to a random choice of source addresses.
If you want a specific source address to be used, you have to specify it ... no big deal, though. bind() hasn't changed that much.
So what does that mean for a client application (http/ftp,etc.) where you might have local firewalls permitting things for internal-subnet source ranges but you also have external targets that only accept pre-configured static sources? With NAT you'd use the public side of the NAT for the remote configuration. What's the equivalent when the application has to do it itself?