>> # rndc status
>> rndc: connect failed: 127.0.0.1#953: connection refused
>>
>> In syslog I can see among the startup messages:
>>
>> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command channel
>> 127.0.0.1#953: permission denied
>> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command
On Sun, 30 Jun 2024, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
Environment:
- FreeBSD 13.3-STABLE #n257580
- BIND 9.19.24 installed using "pkg in
> If you (as root) temporary chnage
> sysctl net.inet.ip.portrange.reservedhigh=952
> does it work then (as user bind)?
Yes!
Steinar Haug, AS2116
On 6/30/24 04:46, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
bind-tools-9.18.27_1 with 14.1-RELEASE-p1 suffers from this as well.
On Jul 1, 2024, at 9:18 AM, Craig Leres wrote:
>
> On 6/30/24 04:46, sth...@nethelp.no wrote:
>> Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
>> listen to localhost port 953, with the result that rndc doesn't work.
>> Problem is 100% reproducible.
>
> bind-tools-9.18.27_1 wi
Hi!
> On 6/30/24 04:46, sth...@nethelp.no wrote:
> > Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
> > listen to localhost port 953, with the result that rndc doesn't work.
> > Problem is 100% reproducible.
>
> bind-tools-9.18.27_1 with 14.1-RELEASE-p1 suffers from this as wel
On 7/1/24 10:17, Bakul Shah wrote:
On Jul 1, 2024, at 9:18 AM, Craig Leres wrote:
On 6/30/24 04:46, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
On Sat, Jun 29, 2024 at 8:17 PM Craig Leres wrote:
>
> When I upgraded ~10 systems from 13.3 to 14.1 recently, 90%+ of my
> breakage was due to the localhost source address changing from 127.0.0.1
> to 127.0.0.2. This was on two of my systems.
>
> My lo0 config is standard:
>
> mote 20 % ifco
On 7/1/24 15:53, Michael Proto wrote:
What netmask are you using for 127.0.0.2? I'd treat it as I would an
IP alias (only on localhost) with a /32 netmask, should keep it
isolated. Just tried it myself on a test box and iperf works as
expected, using 127.0.0.1 as the source when connecting.
I
On Mon, Jul 1, 2024 at 7:04 PM Craig Leres wrote:
>
> On 7/1/24 15:53, Michael Proto wrote:
> > What netmask are you using for 127.0.0.2? I'd treat it as I would an
> > IP alias (only on localhost) with a /32 netmask, should keep it
> > isolated. Just tried it myself on a test box and iperf work
Linux routes sound from the audio driver to the video driver causing
sound to come out of the HDMI cable. FreeBSD can't. This affects ALL i3,
i5, i7, i9 systems.
FreeBSD can't even support x11 on my GMKtec K8 with Radeon 780M
graphics. Linux Mint does.
11 matches
Mail list logo
