Re: bind reacts badly to dhcpcd losing/regaining connectivity

Date:Sat, 15 Apr 2017 20:24:45 -0700 From:John Nemeth Message-ID: <201704160324.v3g3ojwt018...@server.cornerstoneservice.ca> | There are issues with IP_PKTINFO on NetBSD, see 48166 and 48280. The missing field (48166) doesn't bother me (I

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 15, 8:14pm, jnem...@cue.bc.ca (John Nemeth) wrote: -- Subject: Re: bind reacts badly to dhcpcd losing/regaining connectivity | } It is a weak copyleft license. It creates problems for us because | } it will require a lot more work to import, and cause more issues | } for redistribution

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 16, 6:48am, k...@munnari.oz.au (Robert Elz) wrote: -- Subject: Re: bind reacts badly to dhcpcd losing/regaining connectivity | Date:Sat, 15 Apr 2017 22:16:43 + (UTC) | From:chris...@astron.com (Christos Zoulas) | Message-ID: <ocu64b$9r

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 16, 8:23am, Robert Elz wrote: } } | I suspect the IP_RECVDSTADDR setsockopt() } } Actually, more probably IP_PKTINFO as that's the one named uses for IPv6. } Either would do for the purpose of determining the incoming address of a } UDP datagram, so the reply can be sent from the

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 15, 10:16pm, Christos Zoulas wrote: } In article <201704152047.v3fklaxz010...@server.cornerstoneservice.ca>, } John Nemeth wrote: } > } > What's wrong with the MPL? } } It is a weak copyleft license. It creates problems for us because } it will require a lot more

Re: bind reacts badly to dhcpcd losing/regaining connectivity

Date:Sat, 15 Apr 2017 22:16:43 + (UTC) From:chris...@astron.com (Christos Zoulas) Message-ID: | > How is this done in NetBSD? | | bind to INADDR_ANY I assume that what jnemeth was really asling, was how to make it

Re: bind reacts badly to dhcpcd losing/regaining connectivity

In article <201704152047.v3fklaxz010...@server.cornerstoneservice.ca>, John Nemeth wrote: > > What's wrong with the MPL? It is a weak copyleft license. It creates problems for us because it will require a lot more work to import, and cause more issues for redistribution.

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 15, 9:09am, Christos Zoulas wrote: } On Apr 15, 5:29pm, k...@munnari.oz.au (Robert Elz) wrote: } } | ps: Christos - capabilities (if we had them) would not be the answer - if you } | were to trust bind to be unhackable, then just using root would be just as } | good a solution, if you

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Apr 15, 5:29pm, k...@munnari.oz.au (Robert Elz) wrote: -- Subject: Re: bind reacts badly to dhcpcd losing/regaining connectivity | ps: Christos - capabilities (if we had them) would not be the answer - if you | were to trust bind to be unhackable, then just using root would be just as | good

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Sat 15 Apr 2017 at 13:55:08 +0700, Robert Elz wrote: > Changing the bind() call is easy, fixing all the places it is assumed to > work the way it now does is harder. Ah, that is probably why the following attempt did not cause bind to open a wildcard socket: listen-on-v6 { any; }; /*

Re: bind reacts badly to dhcpcd losing/regaining connectivity

Date:Sat, 15 Apr 2017 03:06:13 + (UTC) From:chris...@astron.com (Christos Zoulas) Message-ID: | Or capabilities, or wildcard bind. That is what I meant by ... | >or to recode the | >receive code to use the new way to

Re: bind reacts badly to dhcpcd losing/regaining connectivity

In article <4355.1492217...@andromeda.noi.kre.to>, Robert Elz wrote: >Date:Sat, 15 Apr 2017 01:41:17 +0200 >From:Rhialto >Message-ID: <20170414234117.ga18...@falu.nl> > > > | Why does named not succeed in using the interface

Re: bind reacts badly to dhcpcd losing/regaining connectivity

In article <20170415005323.ga17...@falu.nl>, Rhialto wrote: >-=-=-=-=-=- > >On Fri 14 Apr 2017 at 19:20:13 -0500, Jeremy C. Reed wrote: >> On Sat, 15 Apr 2017, Rhialto wrote: >> >> > and these errors about re1 (my external interface) kept going all the >> > time. When I noticed

Re: bind reacts badly to dhcpcd losing/regaining connectivity

Date:Sat, 15 Apr 2017 02:53:23 +0200 From:Rhialto Message-ID: <20170415005323.ga17...@falu.nl> | I also noticed the error seems to mention IPv4 only. I am not sure if it | managed to bind an IPv6 address on the same interface (and now it is too

Re: bind reacts badly to dhcpcd losing/regaining connectivity

Date:Sat, 15 Apr 2017 01:41:17 +0200 From:Rhialto Message-ID: <20170414234117.ga18...@falu.nl> | Why does named not succeed in using the interface when it gets an | address again? What to do about it? I noticed partly because my dns data |

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Fri 14 Apr 2017 at 19:20:13 -0500, Jeremy C. Reed wrote: > On Sat, 15 Apr 2017, Rhialto wrote: > > > and these errors about re1 (my external interface) kept going all the > > time. When I noticed them and restarted named, they went away. > > > > Why does named not succeed in using the

Re: bind reacts badly to dhcpcd losing/regaining connectivity

On Sat, 15 Apr 2017, Rhialto wrote: > and these errors about re1 (my external interface) kept going all the > time. When I noticed them and restarted named, they went away. > > Why does named not succeed in using the interface when it gets an > address again? What to do about it? I noticed