Date: Thu, 18 Nov 2004 11:45:21 +0700 (NKZ) From: Vladimir Kurtukov <vk@vk.pp.ru> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/74059: IPX protocol support doesn't work Message-ID: <200411180445.iAI4jLPC002002@fbsd5.kbb.kemerovo.su> Resent-Message-ID: <200411180450.iAI4oP8W027314@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 74059
>Category: kern
>Synopsis: IPX protocol support doesn't work
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Nov 18 04:50:25 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Vladimir Kurtukov
>Release: FreeBSD 5.3-RELEASE i386
>Organization:
KBB
>Environment:
System: FreeBSD fbsd5.kbb.kemerovo.su 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Thu Nov 18 09:22:33 NKZ 2004 vk@fbsd5.kbb.kemerovo.su:/usr/obj/usr/src/sys/TEST i386
world compiled with
CPUTYPE=p2
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
NOPROFILE=true
MODULES_WITH_WORLD=true
xl0: <3Com 3cSOHO100-TX OfficeConnect> port 0xc000-0xc07f mem
0xd5100000-0xd5100
07f irq 12 at device 4.0 on pci1
miibus0: <MII bus> on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:01:02:fb:33:e2
xl0: [GIANT-LOCKED]
fxp0: <Intel 82557 Pro/100 Ethernet> port 0xc400-0xc41f mem
0xd5000000-0xd50ffff
f,0xd6000000-0xd6000fff irq 11 at device 10.0 on pci1
miibus1: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus1
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:a0:c9:91:34:8f
fxp0: [GIANT-LOCKED]
kernel config is like GENERIC bit with commented out SCSI, firewire, USB,
network cards and this options:
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPDIVERT
options BRIDGE
# ipx support
options IPX
device ef
options ETHER_II
>Description:
IPX support work fine on 4-STABLE, but with 5-BETA7 and 5.3-RELEASE
I can't force it to work. tcpdump shows strange IPX network in
outgoing packets.
# tcpdump -p -i xl0 -n -e ipx
correct packet (net 0x123) comes from Novell Netware server:
10:30:07.740774 00:60:08:96:c0:46 > ff:ff:ff:ff:ff:ff, ethertype IPX
(0x8137), length 494: (NOV-ETHII) 00000123.00:60:08:96:c0:46.0452 >
00000123.ff:ff:ff:ff:ff:ff.0452:ipx-sap-resp[|ipx 448]
# tcpdump -p -i xl0 -n -e ipx and ether host 00:01:02:fb:33:e2
outgoing packet from out machine:
10:30:57.458631 00:01:02:fb:33:e2 > ff:ff:ff:ff:ff:ff, ethertype IPX
(0x8137), length 58: (NOV-ETHII) 04530000.01:23:00:01:02:fb.33e2 >
00000000.01:23:ff:ff:ff:ff.ffff: ipx-#ffff 14
IPX network on interface is configured as 0x123, but tcpdump shows
0x4530000 and node number not same as MAC address. seems like net
number shifted to right by 2 bytes:
04530000.01:23:00:01:02:fb - incorrect
00000123.00:01:02:fb:33:e2 - correct
the same behavior is with xl0, fxp0 and with device ef's xl0f0,
fxp0f0
>How-To-Repeat:
compile kernel with IPX support:
options IPX
#ifconfig <iface> ipx 0x123
#tcpdump -p -i <face> -n -e ipx and ether host <iface mac>
address in outgoing packets must be 00000123.<iface mac>
>Fix:
unknown
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411180445.iAI4jLPC002002>