20.06.2019 6:32, Rodney W. Grimes wrote:
>>> I've not run a userland without V6 in a long time once I started to have
>>> issues with some things.
>>
>> Can you give an example of such script in base system, please?
>>
>> If you have such script or binary not in our base, it's not our fault :-)
>
Rodney W. Grimes writes:
> >Wider question:
> >Say I'm running a system with both IPv4 and IPv6 enabled.
> >Stuff Happens(tm) and I want to completely disable IPv6 for some
> > indefinite but temporary period - not chamge any configuration
> > settings or firewall rules, but jus
[ Charset windows-1252 unsupported, converting... ]
> 19.06.2019 22:42, Rodney W. Grimes wrote:
>
> >> 18.06.2019 10:10, Ronald F. Guilmette wrote:
> >>> How can I turn off IPv6 entirely without rebuilding the kernel?
> >> You cannot. GENERIC kernel specifically enables IPv6 support and you need
> In message
>
> Andreas Nilsson wrote:
>
> >> That is *not* what the Handbook says. Please read it.
> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html
> >>
> >Ok, so the handbook is wrong. It's a bug in the documentation.
>
> ACK
Probably should just elimina
> 19.06.2019 22:42, Rodney W. Grimes wrote:
>
> >> 18.06.2019 10:10, Ronald F. Guilmette wrote:
> >>> How can I turn off IPv6 entirely without rebuilding the kernel?
> >> You cannot. GENERIC kernel specifically enables IPv6 support and you need
> >> to disable it at compile time.
> >> And if you
> 19.06.2019 23:18, Rodney W. Grimes wrote:
>
> >> 19.06.2019 3:57, Ronald F. Guilmette wrote:
> >>
> >>> And god only knows how much will break once I've done that.
> >>
> >> IPv6 will break only.
> >
> > That is incorrect, scripts that would silently do nothing can
> > now infact fail, trust me
> Rodney W. Grimes writes:
>
> > > And god only knows how much will break once I've done that. How many
> > other
> > > people have tested -all- of the resulting binaries, seriously, on actual
> > > production systems? (I may be the first one ever, at least for 12.0.)
> >
> > I also agree
In message
Andreas Nilsson wrote:
>> That is *not* what the Handbook says. Please read it.
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html
>>
>Ok, so the handbook is wrong. It's a bug in the documentation.
ACK
>As soon as set firewall_script instead of firewa
In message <74b7ccf0-967f-40b1-9818-3417cd8d1...@punkt.de>,
"Patrick M. Hausen" wrote:
>https://tools.ietf.org/html/rfc6761
Wow. Thanks for that. Quite certainly, 6.3 (part 1) is confirming
that this is the way things are now, and have been, apparently since
2013.
I really didn't know. Now
19.06.2019 22:42, Rodney W. Grimes wrote:
>> 18.06.2019 10:10, Ronald F. Guilmette wrote:
>>> How can I turn off IPv6 entirely without rebuilding the kernel?
>> You cannot. GENERIC kernel specifically enables IPv6 support and you need to
>> disable it at compile time.
>> And if you do, you better
19.06.2019 23:18, Rodney W. Grimes wrote:
>> 19.06.2019 3:57, Ronald F. Guilmette wrote:
>>
>>> And god only knows how much will break once I've done that.
>>
>> IPv6 will break only.
>
> That is incorrect, scripts that would silently do nothing can
> now infact fail, trust me, first hand experie
Rodney W. Grimes writes:
> > And god only knows how much will break once I've done that. How many other
> > people have tested -all- of the resulting binaries, seriously, on actual
> > production systems? (I may be the first one ever, at least for 12.0.)
>
> I also agree here, running a
> In message
>
> Freddie Cash wrote:
>
> >For someone who doesn't want to be preached to about the benefits of IPv6,
> >you certainly do a lot of preaching about not wanting IPv6. :)
>
> Guilty as charged.
>
> >You've been given the tools to do exactly what you want:
> > - comment out IPv6
> 19.06.2019 3:57, Ronald F. Guilmette wrote:
>
> > And god only knows how much will break once I've done that.
>
> IPv6 will break only.
That is incorrect, scripts that would silently do nothing can
now infact fail, trust me, first hand experience. This can
have consequences beyong "IPv6 will
> In message <23816.53518.998090.665...@jerusalem.litteratus.org>,
> Robert Huff wrote:
>
> >> Actually, no, that's not how one is supposed to enable one's own set
> >> of ipfw ules. To do that, the Handbook (Sec. 30.4.1) says very clearly
> >> that one should do:
> >>
> >> firewall_e
> 18.06.2019 10:10, Ronald F. Guilmette wrote:
>
> > How can I turn off IPv6 entirely without rebuilding the kernel?
>
> You cannot. GENERIC kernel specifically enables IPv6 support and you need to
> disable it at compile time.
> And if you do, you better rebuild the world too using WITHOUT_INET
> I do not wish to begin any religious war here. I understand that IPv6
> can be a sensitive and sometimes even emotional issue for many people.
> Speaking only for myself, and only for the present moment, I can say
> that for me, IPv6 represents only an annoyance and a very sizable
> distraction.
> > In message <201906190617.x5j6hqma016...@gndrsh.dnsmgr.net>,
> > Rodney W. Grimes" wrote:
> >
> > >> In message <201906181719.x5ihj8g0014...@gndrsh.dnsmgr.net>,
> > >> "Rodney W. Grimes" wrote:
> > >>
> > >> >What is in /etc/host.conf, /etc/resolv.conf, do you have DNS running?
> > >>
> >
> In message <201906190617.x5j6hqma016...@gndrsh.dnsmgr.net>,
> Rodney W. Grimes" wrote:
>
> >> In message <201906181719.x5ihj8g0014...@gndrsh.dnsmgr.net>,
> >> "Rodney W. Grimes" wrote:
> >>
> >> >What is in /etc/host.conf, /etc/resolv.conf, do you have DNS running?
> >>
> >>
> >> 1) http
Hi!
> Am 19.06.2019 um 09:14 schrieb Andreas Nilsson :
> As soon as set firewall_script instead of firewall_type your problems will
> be solved. Just try it. The man page for rc.conf will tell you the same
> thing.
He will need to adjust his rule file, though. Setting firewall_type
to an absolute
On Tue, Jun 18, 2019, 23:28 Ronald F. Guilmette
wrote:
> In message w...@mail.gmail.com>
> Andreas Nilsson wrote:
>
> >But why are you even running rc.firewall if it does not do what you want?
>
> You are asking me the very question that *I* have been asking myself
> since my "upgrade" to 12.0.
Hi!
> Am 19.06.2019 um 08:23 schrieb Ronald F. Guilmette :
> So basically you're telling me that local-unbound has taken it upon
> itself to decide for me, regardless of what is or isn't in my /etc/hosts
> file, what addresses "localhost" should resolve to??
>
> If so, that really is rather presu
22 matches
Mail list logo
