Ethereal-dev: Re: [ethereal-dev] pim(protocol independent multicast)

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: itojun@xxxxxxxxxx
Date: Sat, 16 Oct 1999 10:56:51 +0900
>That still leaves open, however, the question of how to display tunnelled
>protocols. We can show ipv6/udp/data as children of PIM, or as siblings
>of PIM.

	Hmm, there are "obvious" tunnelling protocols, like:
	- GRE
	- IPv6 over IPv4 (RFC1933)
	- whatever,
	and not very obvious tunnelling, like
	- PIM register.
	There are some protocols where original packets are attached
	(not really a tunnel but besically a error report).
	- ICMP/ICMPv6 error report
	What is the most proper way to show these? I'm not really sure.

	The filter code issue is another thing.  If you have multiple
	AH and would like to perform a filter with AH field, what should I do?
	For IPv6 case, header chain chasing is a problem.  If we have
	intermediate header between IPv6 header and TCP header,
	"ipv6.nxt == TCP" will fail to capture those packets.

itojun