[bind10-dev] #1534, IPV6_USE_MIN_MTU and similar

Shane Kerr shane at isc.org
Wed Feb 15 13:51:13 UTC 2012


Michal,

On Wednesday, 2012-02-15 12:17:39 +0100, 
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:
> > As for where to set the option (assuming "do it by default" is
> > agreed), I personally don't think it too much for the socket
> > creator. It basically just a single call to setsockopt
> > (unfortunately with a couple of ifdefs due to the non compliant
> > systems), and we do it unconditionally (the behavior doesn't change
> > based on the apps request).  If we even don't want to add that
> > amount of code to sock creator, we could do it in the boss,
> > probably with a small C/C++ wrapper module.
> 
> I don't know. Maybe if it is just „use it for everything“, it is OK
> for the socket creator.

Yes, it is. I think that an application that needs different behavior
(like TFTP) can change this before use.

> Is here somebody who uses both linux and non-linux on regular basis,
> to check both the ifdef branches compile correctly? If not, I can
> write it and try to be careful when writing the code that won't be
> compiled here, but it's always problematic.

There is a way to submit a branch to our build farm. I don't know the
link describing this off-hand, maybe Jeremy can point you there?

Cheers,

--
Shane
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120215/3cf00b2f/attachment.bin>


More information about the bind10-dev mailing list