[Solved] Supermicro X9SCA-F and AOC-SG-12 Dual port Server LAN Adapter problem
-
I have no problems more than an year. Same configuration, no changes in hardware or software. Just upgrade to pfSense 2.1.1 and my VLANs goes crazy.
All my VLANs was on em0 and em1 interface. Just to be sure I changed them to igb0 interface, but this doesn't help at all.
By "default VLAN" I mean my untagged traffic, all my tagged traffic have a big lag now. And again I have no problems at all until version 2.1.1 upgrade.
I will now downgrade to 2.1, now my network is not usable. Is there any way to use the "old" driver?
-
You can probably load the old driver at boot. I've never tried it with an older driver but it works fine for newer. You need to get hold of the kernel modules, if_em.ko and if_igb.ko from FreeBSD 8.3. Either from a FreeBSD 8.3 image or I think Jim has them here: http://files.pfsense.org/jimp/ko-8.3/
Copy the modules to /boot/modules on your pfsense box. Now create a file /boot/loader.conf.local and add the following lines to it:if_em_load="yes" if_igb_load="yes"However I'd be very surprised to find you're the only person running VLANs on 82574L NICs and other people don't seem to be having a problem. :-\
Steve
-
Steve, thanks a million times!
I've changed only igb driver (because it is LAN and I can do this from remote location) and now it works! Just see the ping to this VLAN address:
64 bytes from 192.168.170.50: icmp_seq=28 ttl=128 time=0.394 ms
64 bytes from 192.168.170.50: icmp_seq=29 ttl=128 time=0.180 ms
64 bytes from 192.168.170.50: icmp_seq=30 ttl=128 time=0.152 ms
64 bytes from 192.168.170.50: icmp_seq=31 ttl=128 time=0.181 ms
64 bytes from 192.168.170.50: icmp_seq=32 ttl=128 time=0.231 ms
64 bytes from 192.168.170.50: icmp_seq=33 ttl=128 time=0.229 ms
64 bytes from 192.168.170.50: icmp_seq=34 ttl=128 time=0.227 msSo what to do with the next pfSense versions?
-
Nice. :)
Glad it worked out for you but you should consider why nobody else seems to be having those problems. It seems likely you have some odd driver setting in place or unusual combination of hardware.Those newer drivers were backported from FreeBSD 10. pfSense 2.2 will be built on 10. Try one of the snapshots if you can to see how it will run on your hardware.
Steve
-
You are right, I can not relay on this driver forever, but the problem is that this is a production firewall on a big customer at remote location. So it is not easy to test new snapshots, but I will try to upgrade firmware on the motherboard or just ask Supermicro for help. FYI all my other firewalls based on Supermicro and Intel chipset works just fine.
-
Running different software you mean or just slightly different hardware?
Perhaps the switch at that location is doing something odd?Steve
-
All my firewalls are with the latest pfSense version, hardware is different, because I get what is on stock at the time and is mainly based on Supermicro server boards. Switches are D-Link DGS-3100-48 (two connected with HDMI cable) and they work as one.
-
Hmm, odd. I can't believe nobody else has seen this. There were many other issues when the newer drivers were being backported, for a long while they weren't stable and were in fact backed out of the 2.1.1 snapshots at one point.
There might be something in this locked thread: https://forum.pfsense.org/index.php?topic=72763.0Otherwise maybe time to start a new thread with a more descriptive title.
Steve
-
After 2 years I have similar problems with the same hardware on different location. My pfSense work on that location more than 3 years without any problem, but now all connections are upgraded and introduction of 1Gbit Internet (via media converter) cause troubles.
After the speed upgrade it is impossible to get IP from my ISP via DHCP. I tested with two laptops and cheap router and it works. So I remember about my problems with this hardware combination and try to set interface to 100baseTX full-duplex and it works (I can get IP) but then I have 3-10% packets lost and lag is from 100ms to 1000 ms - connection is not usable at all.
I use pfSense 2.3.2-RELEASE (i386). I will replace the MB (this was the final solution with my previous problem), but I need something to keep my location up until that moment. Can I use some old drivers (this was the temporary solution for the other case) this time?
-
OK, I solved again. Here are the steps:
1. Remove pfSense and install VMware ESXi (free).
2. Install pfSense on ESXi as VM.
3. Configure Ethernet interfaces, but do not use AOC-SG-12 Dual port Server LAN Adapter ports. They will not work as expected.
4. Run tests - 850 MBps NAT.
