Date: Sun, 29 Jun 2008 16:27:33 +0900 From: Shunsuke SHINOMIYA <shino@fornext.org> To: Andrew Thompson <thompsa@FreeBSD.org>, Hiroki Sato <hrs@FreeBSD.org> Cc: freebsd-bugs@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re[2]: kern/125003: incorrect EtherIP header format. Message-ID: <20080629150108.6783.A2D40D1E@fornext.org> In-Reply-To: <20080626143424.GA56861@citylink.fud.org.nz> References: <200806260713.m5Q7DxoX002890@www.freebsd.org> <20080626143424.GA56861@citylink.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
> It is unclear where the interoperability problem comes in.
I'm sorry. A fix I submitted was a mistake.
> Which would conform to the requirement. Can you describe the problem you
> are seeing.
FreeBSD's current implementation expects 0x03, 0x00 as EtherIP header,
but another implementation(UNIVERGE IX2015, products by NEC, Japan)
transmits 0x30, 0x00. Then FreeBSD box discards EtherIP packets.
I read RFC3378 and thought 0x30, 0x00 is correct.
The result of 'tcpdump -np -x proto etherip' at FreeBSD box is as
follows.
192.168.2.37: FreeBSD box
192.168.2.128: IX2015
MAC addresses were replaced with ****.
16:02:40.952832 IP 192.168.2.128 > 192.168.2.37: etherip 344
0x0000: 4500 016c 0098 0000 4061 f2a3 c0a8 0280
0x0010: c0a8 0225 3000 **** **** **** **** ****
~~~~ EtherIP header by IX2015
snip
16:02:48.080826 IP 192.168.2.37 > 192.168.2.128: etherip 108
0x0000: 4500 0080 01f3 0000 1e61 1435 c0a8 0225
0x0010: c0a8 0280 0300 **** **** **** **** ****
~~~~ EtherIP header by FreeBSD
snip
--
Shunsuke SHINOMIYA <shino@fornext.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080629150108.6783.A2D40D1E>