What is generating these ICMP messages? You should be able to stop them by
dropping the packets you're intercepting. It strikes me as totally possible
that they are causing the problem.
Also, I might try testing using nslookup or dig instead of ping.
-- Murphy
On Aug 25, 2011, at 9:55 AM, ib
Hi Christian,
Wireshark shows standard dns replays, and that's why ping works sometimes. The
only irregularity I see are icmp "port unreachable" packets, generated because
nothing is listening on 10.0.0.2:53. but I think it's not the problem!
Thanks for you help.
Ibrahim
From: chest...@dca.fee.
Hi again,
One last question in this thread :) , about weird dns functionality:
In mininet I have a single switch (s1), 4 hosts (h2,h3,h4,h5) (10.0.0.2 ->
10.0.0.5)
resolve.conf points to 10.0.0.2 as dns server, but actually nox catchs dns
requests matching with dst port 53, builds the respons
Hi Murphy,
That's true, converting to string solves the problem. However, I think it would
be better to modify checksum() to test the type of passed data. Also, a "build
packet" example would be great for the next nox update :-)
Thanks,
Ibrahim
Subject: Re: [nox-dev] FW: Checksum calculation
