Gordon Messmer writes:

On 01/20/2011 07:19 PM, Sam Varshavchik wrote:
Gordon Messmer writes:
Wouldn't the easiest fix be to use IPV6_V6ONLY mentioned in section
5.3 of RFC 3493?

No, that's something that's unrelated.

I really think they're the same thing. The documentation for the IPV6_V6ONLY sockopt indicates that this is a boolean value controlling whether or not an AF_INET6 is V6ONLY or not.

The Linux man page for ipv6 further clarifies that /proc/sys/net/ipv6/bindv6only, which Debian has set to "1" specifies the default value for IPV6_V6ONLY.

If Courier specifically sets IPV6_V6ONLY to int 0, it should override Debian's behavior and allow the application to function normally:

       int on = 0;
       if (setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY,
                      (char *)&on, sizeof(on)) == -1)
           perror("setsockopt IPV6_V6ONLY");

Splendid. We have our solution.

I'm in the middle of pulling all the innards out, and hopefully putting them back, sometime soon, but this is going to be the next thing on the chopping block.


Attachment: pgpyeSnlPrHtp.pgp
Description: PGP signature

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to