VNET connectivity issues after upgrading 11.3 (FreeNAS) -> 12.0

[hopeajonne]

It seems that jail VNET somehow drops some inbound packages, most noticeable when doing HTTPS requests from within the jail.

• fetch -v http://archive.org from host system -> ok
• fetch -v http://archive.org from jail without VNET -> ok
• fetch -v http://archive.org from jail with VNET -> sends request and doesn't get anything in return
• fetch -v http://www.debian.org from host system -> redirect to https -> ok
• fetch -v http://www.debian.org from jail without VNET -> redirect to https -> ok
• fetch -v http://www.debian.org from jail with VNET -> redirect to https -> hangs trying to establish connection

Trying to download a torrent file over HTTP from archive.org gets HTTP response but download stalls.

Doing fetch -v https://extranet.www.sol.net/files/misc/ca-root-nss.crt.src however works fine.

Things I tried to no avail:

• Turning hardware offloading on and off
• Messing with MTU
• Turning DHCP/BPF on and off
• Making a new jail
• Using 11.4 release

I'm using ASIX AX88179-based USB3 adapter (d-link dub-1312) since onboard adapter is realtek garbage and I have that disabled in BIOS. Since upgrade the adapter also started dropping out, i sometimes see ue0: link state changed to DOWN/UP messages in log but NAS seems to be working fine, however it sometimes drops out of network entirely and only manual reboot helps. Don't know if it's related or not.

 

[jgreco]

Ethernet chipsets listen to the network for packets, and to prevent swamping the system with interrupts for packets not belonging to them, are also responsible for filtering packets and only delivering those intended for their host. (I do not wish to get into a debate of "that's the switch's job" with anyone, thankyouverymuch, I know how modern networks work, some of us were here during the old days though.)

Bearing in mind that I do NOT have one of these to play with, I would nevertheless suggest that it is entirely possible that the device is only capable of being configured to receive packets for common (read: "Windows-like") configurations, or that perhaps the device driver isn't correctly configuring the silicon. The named chipset looks like it is probably covered by the axge driver, which also suggests that the driver isn't a vendor-provided driver. Because VNET is highly dependent on the competence and correctness of the networking hardware, I feel like this is not an implausible possibility. Because USB ethernet devices are not supported under FreeNAS/TrueNAS and only happen to work because nobody bothered to strip them out of the FreeBSD system, I suspect there won't be a bunch of help from iX developers on this, but you can try reporting it with "Report a Bug" (see the top bar). If you do, please post the Jira issue here, along with any resolution.

You might want to turn on the Realtek and see if the problem goes away. If so, you might try ... other options? I dunno.

 

[hopeajonne]

Well, the thing is, this setup used to work perfectly back in 11.3, it only started having issues in 12.0.

I switched on realtek adapter and the problem is gone, however it doubt it will be stable (although tbh it's probably about as stable as it is with usb adapter, huh)

I don't have many options - i'm using a pretty shitty J1900 MoBo with integrated CPU with only one PCIex1 slot already occupied by a sata card, it does have a serial port but i doubt it would work better than USB, lol. So in terms of long-term solutions for proper ethernet i really only have 3 options:

• use a USB adapter
• hunt down a motherboard with GOOD™ ethernet chip
• hunt down a PCIe card that has both SATA and Ethernet

I can't get a PCIe card because i'm using mini-ITX case/mobo which only allows for one slot.

....and of course last option would be just moving everything i have in jails away onto another computer entirely and forgetting FreeBSD jails like it was a bad dream.

I guess I'll live with realtek adapter for now and make the issue... here it is: https://jira.ixsystems.com/browse/NAS-113168

 

[jgreco]

Yeah, I don't doubt it worked, or maybe even just seemed to. I would be totally un-shocked to find that a driver tweak for a new adapter, or a change in VNET, or some new feature resulting in an additional MAC address, or maybe you added another VM, or maybe there's a bug in the VNET constructor code in TrueNAS, or any of a bunch of other things might have changed and broke you. I don't have an exact answer, just decades of experience that "stuff happens." Still, do post back if you get a resolution. I'm definitely curious.