On Sunday 2010-08-29 12:48, Xavier Roche wrote: >1. one outgoing IP per service (for example, a SMTP server would >have its own address for the outgoing interface - and one unique >reverse IP to the declared SMTP server address) > >The first case can sometimes be partially solved using >application-specific configuration (bind to a specific address) - >however this is not desirable when you need to listen to all >interfaces (ie. including IPv4-only or IPv6-only ones) You are confusing incoming with outgoing connections. bind is correct. For the incoming one you bind to [::]:25, for the outgoing one you bind to [2a01::desired]:0. Problem solved. > 3. one outgoing IP for specific network blocks > etc .. Hosts uses their assigned address as outgoing source address. >RFC 3484 (4) specifies the way source address is selected ; with the >following order (5): > > 1. Prefer same address. (i.e. destination is local machine) > 2. Prefer appropriate scope. (i.e. smallest scope shared with the destination) > 3. Avoid deprecated addresses. > 4. Prefer home addresses. > 5. Prefer outgoing interface. (i.e. prefer an address on the interface we're > sending out of) > 6. Prefer matching label. > 7. Prefer public addresses. > 8. Use longest matching prefix. And somewhere in between is /etc/gai.conf. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
