It may be "easy to implement" something that superficially resembles
mDNS, but it's not that easy to implement mDNS correctly. One-shot
legacy resolution (multicast queries with src port != 5353, yielding
non-cacheable unicast replies) is pretty straightforward, but anyone who
binds to port 5353 is ...
What am I missing here? Why don't I see 1.1.1.1 traffic in the etl file?
pktmon start --capture --pkt-size 0 -f C:\tmp\capture.etl ping 1.1.1.1
pktmon stop
Latest Comments