|
Title: Weird NAT Behavior Post by: jaxxstorm on Wednesday 01 August 2012, 06:34:06 am I'm seeing some really weird NAT behavior after initial setup and I can't really explain it.
I've got the following setup: Router -> DMZ -> Endian Firewall -> NAT -> Clients I know that the router is forward correctly because I change it so one of my servers is in the DMZ, all ports forward correctly. However, I just set up a NAT rule for HTTP and every time I access the website on port 80, it redirects all traffic to the Endian Firewall config page. My initial rule for testing is as follows: Uplink ANY TCP/80 192.168.4.7 : 80 ALLOW HTTP ALLOW from: Uplink ANY Title: Re: Weird NAT Behavior Post by: timupci on Wednesday 01 August 2012, 09:42:16 am What are you trying to achieve?
Does the Endian Firewall have an outside IP Address on RED? What part did you put the configuration into? Also please not that Endian Firewall will NOT send out packets to the RED and then allow them back in. IE you can not browse to your own external IP address. Title: Re: Weird NAT Behavior Post by: jaxxstorm on Friday 03 August 2012, 06:31:38 pm I'm trying to create a new gateway firewall, essentially having my modem/router pass all traffic from itself -> Endian and then set the default gateway of all network clients to the IP address of the Endian box so I can manage traffic better.
It's a convoluted method and I know I'd be better suited to just setting up a new gateway, but this a test environment so I'm just playing around. The router is definitely passing traffic to Endian, I just think I've either double NATed somehow, because it keeps forwarding all traffic to Endian's web interface. |