VLAN Problem VIA based Nexgate NSA-1041 since 1.2.3 RC2
-
You could try the manual way
ifconfig fxp0 -rxcsum -txcsum -
sorry.. did not work. the option disappears but it still not work..
i had a look at a packet capture. At the DHCP discover on the WAN interface i can not see a VLAN tag.
other packet from my network come with a correct VLAN tag.the vlan id is 10 and the following value appears in the ip packet:
Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0\. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0i think the vlan tagging is not working correctly…
-
If it's not working properly, it must be something specific to your fxp chip revision.
I'm using VLANs heavily on fxp cards on 1.2.3-RELEASE and it works just fine for me, either with onboard NICs or add-in cards. It does look like yours have tso, you might try disabling that if it isn't already:
sysctl -w net.inet.tcp.tso=0The output of these commands might also help:
# pciconf -lv | grep fxp0 fxp0@pci0:0:11:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 # ifconfig -m fxp0 fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=2009 <rxcsum,vlan_mtu,wol_magic>capabilities=2049 <rxcsum,vlan_mtu,polling,wol_magic>ether 00:02:b3:03:80:28 inet6 fe80::202:b3ff:fe03:8028%fxp0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX <full-duplex>) status: active supported media: media autoselect media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none media 100baseTX mediaopt hw-loopback</full-duplex></rxcsum,vlan_mtu,polling,wol_magic></rxcsum,vlan_mtu,wol_magic></up,broadcast,running,simplex,multicast> -
TSO is already disabled.
# sysctl -w net.inet.tcp.tso net.inet.tcp.tso: 0here the infos:
# pciconf -lv | grep fxp0 fxp0@pci0:0:9:0: class=0x020000 card=0xffffffff chip=0x12098086 rev=0x10 hdr=0x00# ifconfig -m fxp0 fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=2198 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic>capabilities=21db <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,tso4,wol_magic>ether 00:10:f3:0e:19:ce inet6 fe80::210:f3ff:fe0e:19ce%fxp0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX <full-duplex>) status: active supported media: media autoselect media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none media 100baseTX mediaopt hw-loopback</full-duplex></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,tso4,wol_magic></vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic></up,broadcast,running,simplex,multicast> -
Looks like yours has a later chip revision and claims to do VLANs in hardware. Mine doesn't claim such support, not sure any of them do.
Perhaps it's a problem along those lines, but unfortunately it's a bit beyond my level of expertise. It might be interesting to try a stock FreeBSD 7.2 install on there to see if you have similar problems, or it may be easier to try a pfSense 2.0 beta snapshot to see if the problem persists on FreeBSD 8.
-
So i have tested a pfSense 2.0 snapshot.
The same tests as before were made but the problem also exists in this version with the same behaviour.to complete the tests here the outputs:
# ifconfig -m fxp0 fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=2198 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic>capabilities=21db <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,tso4,wol_magic>ether 00:10:f3:0e:19:ce inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::210:f3ff:fe0e:19ce%fxp0 prefixlen 64 scopeid 0x1 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active supported media: media autoselect media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none media 100baseTX mediaopt hw-loopback</full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,tso4,wol_magic></vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic></up,broadcast,running,simplex,multicast># ifconfig fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=2198 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic>ether 00:10:f3:0e:19:ce inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::210:f3ff:fe0e:19ce%fxp0 prefixlen 64 scopeid 0x1 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active fxp1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=2198 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic>ether 00:10:f3:0e:19:cf inet6 fe80::210:f3ff:fe0e:19cf%fxp1 prefixlen 64 scopeid 0x2 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active ... fxp1_vlan10: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 00:10:f3:0e:19:cf inet6 fe80::210:f3ff:fe0e:19ce%fxp1_vlan10 prefixlen 64 scopeid 0xa inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active vlan: 10 parent interface: fxp1</full-duplex></performnud,accept_rtadv></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic></up,broadcast,running,simplex,multicast>Any idea how to proceed?
I have found the following lines in the FreeBSD Release Notes:
The fxp(4) driver has been improved. Changes include:
- Rx checksum offload support for 82559 or later controllers has been added
- VLAN hardware tag insertion/stripping support and Tx/Rx checksum offload for VLAN frames support have been added. Note that the VLAN hardware assistance is available only on 82550 or 82551-based controllers.
pfSense recognize my card as a "Intel 82559ER". Can the VLAN hardware support be the issue? Like using VLAN hardware tag but my card cannot do this?
-
Try this:
ifconfig fxp0 -vlanhwtag -vlanhwfilterNot sure about the hwfilter but try it anyhow, if it doesn't work, try just -vlanhwtag
That should disable the hardware tagging. If that works, install the shellcmd package and add a command in there for that. Might help for now.
-
Solved!
at first sight.only disabling hwtag.
ifconfig fxp0 -vlanhwtagI will do some more tests on the system till it goes back as my carp slave (with many VLANs ;-)).
Thanks a lot for your help!
-
Hey mibo
would you know where I can find a pdf manual for the nsa 1041 ?
I have been given one but no instructions for hardware i.e. the pin header info
for power reset etcany help appreciated, thanks
-
Hi Fakster,
have a look at the user manual:
http://www.nexcom.com/ProductModel_Download.aspx?id=97c0aec4-d471-49af-b4f5-78f12f0c57a8
