Please help- Netgate embedded firewall loosing internet connectivity
-
I just installed my netgate today and am having issues. We have speakeasy SDSL and the internet connection is set up with a static IP. I set up traffic shaping, NAT rules and pointed my DNS servers to opendns. Every two hours I loose internet connectivity. I am desperate for help please help me find a resolution to this
Speakeasy has no issues and to prove it, when the internet went down I unplugged my internet modem and plugged back in. No connection still. After power cycling my netgate everything worked
-
What version of pfSense are you using?
What NICs are in use for WAN and LAN interfaces?
When the internet "goes down"
-
can you still ping the pfSense box?
-
Is there anything noted in the pfSense logs at around that time?
-
Can you ping the ADSL modem?
-
-
What version of pfSense are you using?
It came preinstalled with 1.2.3-RC2
built on Sat Jun 20 20:29:59 UTC 2009What NICs are in use for WAN and LAN interfaces?
Instantly upon receiving my package, the port closest to the power input is used for LAN
When the internet "goes down"
* can you still ping the pfSense box?
* Is there anything noted in the pfSense logs at around that time?
* Can you ping the ADSL modem?The system logs do not shpw much info. I just see things there mainly about the startup logs. Maybe I am looking at the wrong logs?
I did not try pinging anything while connection is down yet but this is what I did do. I am guessing that the internet is going down due to inactivity. I ran a ping test on my application server and had it ping the netgate IP throughout the entire night. My internet is still working. I think it is because of inactivity but I checked the settings for inactivity and they were all blank. Maybe I am looking at the wrong page? Maybe there is a bug?
-
What NICs are in use for WAN and LAN interfaces?
Instantly upon receiving my package, the port closest to the power input is used for LAN
The question isn't about their physical location - but the types of NIC. At the very least you need to identify the driver or interface name (eg, fxp or fxp0).
