I had a weird thing happen this morning. I have a WAN, a LAN, a DMZ, and a OPT2
interface. Each of these has its own NIC.
For some reason PFSense stopped routing outgoing packets from the DMZ to the
WAN. (It may have just been new connections only. I saw some traffic still
going from an FTP
- Joe Laffey j...@laffey.tv wrote:
I had a weird thing happen this morning. I have a WAN, a LAN, a DMZ,
and a OPT2
interface. Each of these has its own NIC.
For some reason PFSense stopped routing outgoing packets from the DMZ
to the
WAN. (It may have just been new connections only.
On Mon, 22 Jun 2009, Tim Nelson wrote:
- Joe Laffey j...@laffey.tv wrote:
I had a weird thing happen this morning. I have a WAN, a LAN, a DMZ,
and a OPT2
interface. Each of these has its own NIC.
For some reason PFSense stopped routing outgoing packets from the DMZ
to the
WAN. (It may
On Mon, Jun 22, 2009 at 1:42 PM, Joe Laffeyj...@laffey.tv wrote:
While I forgot to look when it happened, this was one of my thoughts, as
well. But then I thought to myself, wouldn't this cause connections from the
LAN to the WAN to fail as well? Or is the state table subdivided equally
Hello,
Im running pfSense 1.2.3 RC1 on standard PC hardware,
and everything runs perfect exept the DynDNS updater.
The new IP isnt sent to dyndns.org...
If I manually click on the Save button in the Dynamic DNS menu the
IP is updated.
When I click on Monitor it give the following error:
On Mon, Jun 22, 2009 at 5:33 PM, Bjoern Hellermailingli...@hellercom.de wrote:
Hello,
Im running pfSense 1.2.3 RC1 on standard PC hardware,
and everything runs perfect exept the DynDNS updater.
The new IP isnt sent to dyndns.org...
If I manually click on the Save button in the Dynamic DNS
