Le jeu. 29 oct. 2020 à 21:17, Theo de Raadt <deraadt@openbsd.org> a écrit :
>
> Or, don't try to overlay stuff onto a single port. Look, we can tell
> what is going on here, you want to tunnel over the least-filtered port
> on the internet, but if you do that trying to use that port for another
> thing is quite a problem of your own making.
Le jeu. 29 oct. 2020 à 23:10, Theo de Raadt <deraadt@openbsd.org> a écrit :
>
> port 53 has a well known use. It is the firstcomer, for a critical service.
>
> You are abusing that port.
Totally agreed. This is because of my stupid idea to share port 53 for
this use. Maybe my understanding of sockets was wrong, but I thought
that applications could use the bind port _if and only_ they weren't
trying to bind the same IP+port, hence my question about this
conflict, which could happen with other ports as well.
> I could easily argue there is nothing to fix in our kernel.
I think I agree, anyhow, this behavior might be intentional, so I'll
avoid doing that in the future.
Thanks everyone who answered, and if anyone has the definitive answer
about why it wg binds INADDR_ANY, I'd be interested to know.
No comments:
Post a Comment