@DB9:
Hi,
I'm running into a rather strange problem using these interfaces on pfSense 2.2.6.
I have two Digitus DN-3023 USB 3.0 NICs in my system which use the AX88179 chip:
ugen0.7: <ax88179 asix="" elec.="" corp.="">at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (124mA)
ugen0.8: <ax88179 asix="" elec.="" corp.="">at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (124mA)
I've successfully configured pfSense as follows:
Internet
|
Provider's router
|
10.1.1.0/24
|
WAN
pfSense
LAN1, LAN2 (vlans 3, 4)
|
10.1.3.0/24
10.1.4.0/24
|
Switch
| | |
Clients (distributed over the two vlans)
Everything was working as expected until I tried to update a Ubuntu PC (hash sum errors on downloaded packages). I noticed that also the md5sum of a downloaded Ubuntu ISO image was incorrect. (http://releases.ubuntu.com/wily/ubuntu-15.10-desktop-amd64.iso).
When I connect directly to my provider's router I can update and can download a non-corrupted ISO image without any problem. So it has to be something in pfSense.
Comparing the corrupted ISO on a binary level against a non-corrupted one along with some packet dumps, it seems like the corruption occurs at the beginning / end of packets in the download stream.
At first I wanted to blame the 802.1Q setup, maybe these NICs aren't supported that well. I tried playing with the MTU on the LAN interfaces, reducing it to 1496 to compensate for the inserted vlan tags. This seemed to fix the issue. I was able to update and download the iso, but some websites would not load at all. I think this is due to the destination unreachable due to fragmentation ICMP traffic the WAN interface was sending out. So back to the standard MTU of 1500.
Now I've disabled all vlan setup and the LAN interface (only one remaining) is running directly on the interface. But I'm still experiencing the corrupted downloads.
I still have a feeling this issue is related to these NICs, hence I'm posting in this topic
I think it's strange that such a low level issue, has so little impact. Only some HTTP streams are affected, everything else seems to work like a charm.
There's a third realtek interface in the system (on the mainbord), but this is not yet supported by the FreeBSD driver, so no other Interfaces to troubleshoot
Does anyone have the slightest idea what might be going on here?</ax88179></ax88179>
I know this is old but i wanted to supply a likely very plausible answer to this in case anyone else runs into this issue.
If the provider is a DSL provider, and the providers modem is in bridge mode to connect to the pfsense, you MUST in almost all cases change the WAN port on the pfsense to an MTU of 1492, not 1496. DSL uses a tagging on the packets simular to your vlan tags, and any packets exceeding 1492 cannot get through properly.
This is confirmed on XO Communications DSL, CenturyLink DSL, Qwest DSL(bought by CenturyLink), and Integra DSL as well. This could, and most likely was the cause of the issues quoted above, and most likely had nothing to do with the ASIX nics, or the fact they were USB.