You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using interface: 0.0.0.0, replies to queries from clients sometimes originate from a different address than the client used to connect. This breaks the response flow and the client experiences a timeout, not getting the reply back from its perspective.
To reproduce
Steps to reproduce the behavior:
interface: 0.0.0.0
# ip addr add 10.0.0.1/32 dev lo
On a client (Windows in this example): nslookup amazon.com 10.0.0.1
Doesn't happen with nslookup set vc and then executing the query (to run in TCP mode)
Expected behavior
A clear and concise description of what you expected to happen.
Seems like the reply src address is already being set.
The workaround was to set interfaces: 10.0.0.1 and others explicitly. When there are multiple sockets bound, one for each interface address, it works just fine.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using
interface: 0.0.0.0
, replies to queries from clients sometimes originate from a different address than the client used to connect. This breaks the response flow and the client experiences a timeout, not getting the reply back from its perspective.To reproduce
Steps to reproduce the behavior:
interface: 0.0.0.0
# ip addr add 10.0.0.1/32 dev lo
nslookup amazon.com 10.0.0.1
Doesn't happen with nslookup
set vc
and then executing the query (to run in TCP mode)Expected behavior
A clear and concise description of what you expected to happen.
System:
unbound -V
output:Additional information
tcpdump fragment:
unbound/util/netevent.c
Lines 650 to 656 in 7b62767
Seems like the reply src address is already being set.
The workaround was to set
interfaces: 10.0.0.1
and others explicitly. When there are multiple sockets bound, one for each interface address, it works just fine.The text was updated successfully, but these errors were encountered: