You may find that the internal web server is sending its reply IP
packets directly to the internal client, instead of via the firewall.
This can occur if the internal client and the internal web server have
the same subnet mask. The internal web server sends the packets straight
back to the in
You may find that the internal web server is sending its reply IP
packets directly to the internal client, instead of via the firewall.
This can occur if the internal client and the internal web server have
the same subnet mask. The internal web server sends the packets straight
back to the in
Hanasaki JiJi, 2003-11-29 05:50:12 +0100 :
> i have a firewwall with 2 nics .. its running iptables. the outside
> nic forwards port 80 to an internal webserver on an internal ip. this
> works great. if an internal host hits the external ip. traffic does
> not go to the internal web server.
Hanasaki JiJi, 2003-11-29 05:50:12 +0100 :
> i have a firewwall with 2 nics .. its running iptables. the outside
> nic forwards port 80 to an internal webserver on an internal ip. this
> works great. if an internal host hits the external ip. traffic does
> not go to the internal web server.
i have a firewwall with 2 nics .. its running iptables. the outside
nic forwards port 80 to an internal webserver on an internal ip. this
works great. if an internal host hits the external ip. traffic does
not go to the internal web server. if an external host hits the
external ip traffic
i have a firewwall with 2 nics .. its running iptables. the outside
nic forwards port 80 to an internal webserver on an internal ip. this
works great. if an internal host hits the external ip. traffic does
not go to the internal web server. if an external host hits the
external ip traffic
6 matches
Mail list logo