kern/125003: incorrect EtherIP header format.

Shunsuke SHINOMIYA shino at fornext.org
Sun Jun 29 07:28:27 UTC 2008


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 at fornext.org>



More information about the freebsd-bugs mailing list