Re: [pfSense] Interface stops working
On 12/11/13 10:32 AM, Walter Parker wrote: I have a pfSense 2.0.3 box with 5 interfaces, two of which are on motherboard ethernet controllers using the NVIDIA nForce4 CK804 MCP9 Networking Adapter chipset. I had a freenas box that kept disappearing from the network - not very friendly for an iscsi server. After migrating to nas4free and still experiencing the problem, I switch it to linux and the problem still persisted. I ended up narrowing it down to the nvidia network interface on the motherboard (00:08.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a3)). I don't think it's a hardware issue as such, but the reverse-engineered open source drivers not being a perfect match for the hardware. I disabled that interface and replaced with intel nics and have never had a problem. If you can't replace the nics, try playing with these kernel module options: http://helpful.knobs-dials.com/index.php/Forcedeth_notes https://bbs.archlinux.org/viewtopic.php?pid=1082381 Then replace the nics :) There's a stack of reports of issues in google about nvidia and forcedeth. They caused me great pain. Good luck. These two connections connect to the upstream IP (WAN) and to the old IP space for the local network (LAN). I've been seeing the the connection between the upstream ISP and the WAN go down (can reach it from the outside world, can't reach the outside world from it). When this happens, I can get to box by connecting to a box on the LAN network and then making a local connection to the LAN interface. If ifconfig down the WAN interface and then ifconfig up the WAN interface from the CLI, it comes back and works just find. The first time this happened, a Google search suggested that I was running out of mbufs (because the error message said no buffers). So I increased the number of buffers to 128K. The page that I ready said that problem with the mbuf could be do to bad wiring causing excessive packet loss on the interface This time, I did not get a no buffers error message and according to netstat -m, there where plenty of mbufs. Any ideas as to why traffic stops on my WAN interface until it is reset? Is cabling still a got idea or is it likely to be something else? The system in question is a two proc system with dual core Opteron 280 running on a Supermicro Server Class Motherboard with 4GB of ECC RAM. Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Interface stops working
Sorry Walter, I was too euphoric: It was just getting better with the upgrade, it is not solved. Regards, Adrian. On 25/11/13 18:37, Adrian Zaugg wrote: Am 12.11.13 00:32 schrieb Walter Parker: Any ideas as to why traffic stops on my WAN interface until it is reset? I had a similar problem and solved it with a firmware upgrade on the switch - a cisco sg-300 series. Regards, Adrian. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Interface stops working
Am 12.11.13 00:32 schrieb Walter Parker: > Any ideas as to why traffic stops on my WAN interface until it is reset? I had a similar problem and solved it with a firmware upgrade on the switch - a cisco sg-300 series. Regards, Adrian. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
[pfSense] Interface stops working
I have a pfSense 2.0.3 box with 5 interfaces, two of which are on motherboard ethernet controllers using the NVIDIA nForce4 CK804 MCP9 Networking Adapter chipset. These two connections connect to the upstream IP (WAN) and to the old IP space for the local network (LAN). I've been seeing the the connection between the upstream ISP and the WAN go down (can reach it from the outside world, can't reach the outside world from it). When this happens, I can get to box by connecting to a box on the LAN network and then making a local connection to the LAN interface. If ifconfig down the WAN interface and then ifconfig up the WAN interface from the CLI, it comes back and works just find. The first time this happened, a Google search suggested that I was running out of mbufs (because the error message said no buffers). So I increased the number of buffers to 128K. The page that I ready said that problem with the mbuf could be do to bad wiring causing excessive packet loss on the interface This time, I did not get a no buffers error message and according to netstat -m, there where plenty of mbufs. Any ideas as to why traffic stops on my WAN interface until it is reset? Is cabling still a got idea or is it likely to be something else? The system in question is a two proc system with dual core Opteron 280 running on a Supermicro Server Class Motherboard with 4GB of ECC RAM. Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
