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
When the NIC (Network Interface Card) contains several IPs, e.g. 169.254.0.[1-5]0 and 169.254.13.106,
although designate 169.254.13.106 as InetAddress for JmDNS.create(InetAddress) and JmDNS.create(InetAddress, String),
tcpdump still find the mDNS query packages are sent by 169.254.0.50.
$ ip a | grep 169
inet 169.254.13.106/16 brd 169.254.255.255 scope link disc0:mc
inet 169.254.0.10/16 scope link secondary disc0:dt
...
inet 169.254.0.50/16 scope link secondary disc0:dt
$ ip route
...
169.254.0.0/16 dev disc0 proto kernel scope link src 169.254.13.106
$ tcpdump -i disc0 -nn host 169.254.0.50 or 169.254.13.106
...
07:04:24.390833 IP 169.254.0.50.5353 > 224.0.0.251.5353: 0 PTR (QM)? _http._tcp.local. (34)
Above test is based on 3.5.4, but it seems 3.5.8 has the same problem per the source code.
According to JmDNSImpl::openMulticastSocket(), it seems not bind any IP to the source socket.
Could this issue be fixed? Thanks.
The text was updated successfully, but these errors were encountered:
When the NIC (Network Interface Card) contains several IPs, e.g. 169.254.0.[1-5]0 and 169.254.13.106,
although designate 169.254.13.106 as
InetAddress
forJmDNS.create(InetAddress)
andJmDNS.create(InetAddress, String)
,tcpdump still find the mDNS query packages are sent by 169.254.0.50.
Above test is based on 3.5.4, but it seems 3.5.8 has the same problem per the source code.
According to
JmDNSImpl::openMulticastSocket()
, it seems not bind any IP to the source socket.Could this issue be fixed? Thanks.
The text was updated successfully, but these errors were encountered: