On Thu, 2010-02-25 at 19:11 +0530, yogi wrote: > On Wed, 2010-02-24 at 01:16 -0300, Lucas Meneghel Rodrigues wrote: > > H i Yogi, I have read and rebased your patch against current trunk. I > > have one doubt: I noticed that the tcpdump command you use to monitor > > traffic is basically all traffic that goes to network routers > > > > /usr/sbin/tcpdump -npv ip6 -i any 'dst net ff02::2' > > > > However, the IPv4 implementation filters the traffic to the dhcp/bootp > > port, 68. Therefore the ipv6 mapper captures more (non necessarily > > useful) mappings than the ipv4 version. I made some brief research and > > couldn't figure out how to do it. Do you think it's possible to refine > > the tcpdump command to make it look only on the dhp request port (68)? > > > > Hello Lucas, thanks for reviewing my patches for ipv6. > Following tcpdump command will capture only the icmp6 packets and not > all the ipv6 packets > tcpdump -npv -i any icmp6 and 'dst net ff02::2' > > Since the patch uses ip6 link local address, we are looking for router > solicitation messages.
Ok, so you think it'd be better to change the tcpdump command used in the patch to be "tcpdump -npv -i any icmp6 and 'dst net ff02::2'"? That said, I don't fully understand all gory ipv6 details, so please bear with me on this question: how would we be benefit from having an ipv6 address cache? I mean, it's not like we're going to use the mappings for any of the communications... This patch will stay in the queue so Michael can take a look at it and give opinions. Cheers, Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
