I had an odd one today. For some reason, our WAN interface changed its IP to 0.0.0.0 with a NM of 255.0.0.0. Needless to say, we lost all of our IPSec tunnels in the process along with web access. Checking the WAN interface configuration page, I saw that the IP was properly configured there, but the dashboard had the all 0's IP address, and the ARP table didn't show any entry at all for the WAN interface.
I was able to able to get the interface back by rebooting the box (only later to realize I probably could have used ifconfig to bounce the interface) and everything came back. It just sucks that I had to do that. I saw on the forums that someone had a similar problem when they ran out of MBUF's, but that wasn't our issue, as per the info that I pulled from netstat and a few other commands (while we had the problem): kern.ipc.nmbclusters: 25600 Mem: 247M Active, 90M Inact, 133M Wired, 48K Cache, 112M Buf, 1510M Free 2311/1571/3882/25600 mbuf clusters in use (current/cache/total/max) The NIC in question is an Intel(R) PRO/1000 Network Connection 7.2.3 model: em1@pci0:3:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00 class = network subclass = ethernet Anyone else run into this before? I'd like to find a fix before it happens again. Kenny Armstrong Systems Engineer, KyroneX [email protected]
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
