On Tue, Mar 19, 2002 at 02:09:36PM +0100, Chen Yu wrote:
> I am using Ethereal to monitor Mobile IPv6 packets in a testbed.
> But it seems that Ethereal can not work under Mobile IPv6 stack.
> I use MIPv6 stack issued by Microsoft.
It's quite possible that programs that use WinPcap - for example,
WinDump, Analyzer, and Ethereal - won't work under Microsoft's Mobile
IPv6 stack.
> When I start IPv6 ping from CN to MN and roam from home link
> to foreign link, IPv6 ping will be gone. Normally, IPv6 ping will
> recover after a short time. Does anyone have some idea on it?
In order to capture packets, WinPcap's device driver has to plug into
the networking stack; for some types of networking interfaces, that
appears to cause problems with the interface.
See, for example:
http://www.ethereal.com/faq.html#q4.10
and the equivalent FAQ on the WinPcap Web site:
http://netgroup-serv.polito.it/winpcap/misc/faq.htm
"Q-4: Can I use WinPcap on a PPP connection?
A: We have tested WinPcap on PPP connections under Windows 95, Windows
98 and Windows ME. In Windows 95, due to a bug in NDIS, WinPcap
sometimes resets the PPP connection. In Windows 98/ME this bug appears
to be corrected, and WinPcap seems to work properly. Under Windows NT
and Windows 2000 there are problems with the binding process, that
prevents a protocol driver from working properly on the WAN adapter."
I would suggest that you ask the WinPcap developers about this; send
mail to
winpcap@xxxxxxxxxxxxxxxxxxxxxxx
> PS: I start Ethereal on MN to monitor incoming and out going packets.
> Does Ethereal associates IP address with network cards?
No. Ethereal does not, in any sense, associate IP addresses with
network interfaces.
It does not, for example, assume that packets that come in on a
particular networking interface are associated with a particular IP
address, nor does it set the IP address for any networking interfaces.
