kern/90279: Appletalk and 0x090007 OUI enet frames invisible to
Guy F. Boyd
gfb at vta.com
Mon Dec 12 06:30:21 PST 2005
>Synopsis: Appletalk and 0x090007 OUI enet frames invisible to 6.0R?
>Arrival-Date: Mon Dec 12 14:30:02 GMT 2005
>Originator: Guy F. Boyd
>Release: 6.0-STABLE #0 WED DEC 7 08:02:20 2005
6.0-STABLE FreeBSD #0 Wed Dec 7 08:02:20 2005 gfb at testbox:/usr/src/sys/i386/compile/TESTKERN
Configure or load BRIDGE features on a 6.0 machine with 2 or more interfaces in the same group. Connect either or both of 2 interfaces to separate ethernet segments with plenty of Appletalk traffic. Place each interface in promiscuous mode in various exclusive modes of test:
tcpdump -i nge0 -n -e 'ether host 09:00:07:ff:ff:ff'
tcpdump -i re0 -n -e 'ether host 09:00:07:ff:ff:ff'
tcpdump 'ether proto \atalk'
On each segment that each interface is attached to, launch similar network monitoring techniques.
Move back to 5.4R or 4.11, temporarily.
Will provide sample tcpdump(1) output on request to qualified parties.
>sysctl -w net.link.ether.bridge.config=nge0:0,sk0:0,re0:0,
>sysctl -w net.link.ether.brige.enable=1
>ipfw add 1 allow all from any to any
On a network with a polyglot of appletalk devices and various FreeBSD machines of varying vintages, this 6.0 machine was configured as an ethernet bridge between 2 ethernet segments that were previously connected via cat5e hard wire. There is ( a lot of ) appletalk traffic on both segments. One segment is connected to nge0, the other to re0. sk0 has no appletalk traffic and connects to a router.
When placed into promiscuous mode via tcpdump(1), neither interface appears to show aarp,nbp-lkup, or other frames that are clearly visible on (and originating from devices on) each segment. These frames are independently visible by other FreeBSD vintage machines that are attached to those segments. Only a few packets with the OUI identifier 0x090007 originating from some HP printer products on one segment are the only packets visible at the 6.0 machine. Net result is that Appletalk clients that are a ttached to either segment cannot browse devices on the other segment across the bridged interfaces.
More information about the freebsd-bugs