On 21/04/2021 09:25, Todd Zullinger wrote:
Do you have a 192.168.122.26 interface on the host? That's
the error I see if I try to use an IP which is not assigned
to any interface.
Sure. But it didn't help that I forgot I had created a process a few weeks ago
that
happened to grab that port o
Ed Greshko wrote:
> On 21/04/2021 08:29, Todd Zullinger wrote:
>> Hi Ed,
>>
>> Ed Greshko wrote:
>>> Does anyone know of a way to get ncat to listen on port 53 when using
>>> systemd-resolved?
>>>
>>> [root@meimei ~]# ncat -l -4 -p 53
>>> Ncat: bind to 0.0.0.0:53: Address already in use. QUITTIN
On 21/04/2021 08:29, Todd Zullinger wrote:
Hi Ed,
Ed Greshko wrote:
Does anyone know of a way to get ncat to listen on port 53 when using
systemd-resolved?
[root@meimei ~]# ncat -l -4 -p 53
Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING.
You can't bind to the port if it's already
Hi Ed,
Ed Greshko wrote:
> Does anyone know of a way to get ncat to listen on port 53 when using
> systemd-resolved?
>
> [root@meimei ~]# ncat -l -4 -p 53
> Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING.
You can't bind to the port if it's already in use. But if
you're okay with us
Does anyone know of a way to get ncat to listen on port 53 when using
systemd-resolved?
[root@meimei ~]# ncat -l -4 -p 53
Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING.
(no rants, please)
--
Remind me to ignore comments which aren't germane to the thread.
_
