patches to fix bindaddress (for IPv6) in innfeed

Antonio Querubin tony at lava.net
Thu Mar 28 18:00:18 UTC 2002


On Thu, 28 Mar 2002, Matus "fantomas" Uhlar wrote:

> -> Ok, here's an attempt to add meager documentation for bindaddress6 to the
> -> manpage for innfeed.  The updated connection.c.diff also removes the
> -> dependency on the SA_LEN macro which may be causing build problems for
> -> some.
>
> does this work with DNS names?
> What if DNS record points to ipv4 and ipv6 address too?

bindaddress can only be an IPv4 address, not a hostname.  As with the
bindaddress parameter, bindaddress6 needs to be specified in innfeed.conf
as just an IPv6 address only, not a hostname.

If your INN server has both IPv4 and IPv6 addresses, bindaddress will
apply only to connections made to an IPv4 address of a receiving server
and bindaddress6 will affect only connections to an IPv6 address of the
receiver.

If the server you are feeding has both IPv4 and IPv6 addresses, the
destination address that innfeed chooses to talk to will vary from
connection to connection if the receiving server is specified by hostname
only.  In any case, innfeed will use the appropriate bindaddress(6) value
based on the actual connection type whether that be IPv4 or IPv6.

If you specify bindaddress and the receiving server hostname resolves to
an IPv6 address only, bindaddress is not used.  If you specify
bindaddress6 but the receiving server is IPv4 only, then bindaddress6 is
not used.

Well, at least that's the way it's supposed to work :)




More information about the inn-workers mailing list