HTTP Port-forwarding
Hi,
I have these rules below to enable:
a) http port-forwarding in requests
b) masquerading rules for http replies.
It does seem to work OK but is very slow. After hours of looking I think the problem as to why it is so slow may be in my Iptables rules.
Can you see a double up or something that may cause a problem ? Or would you say it all looks fine and my problem is elsewhere ?
Thank you ..
$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT DROP
$IPTABLES -P FORWARD DROP
# http requests: # Port-Forwarding setup $IPTABLES -t nat -A PREROUTING -i $ETH0 -p tcp --dport 80 -d 66.xxx.xx.100 -j DNAT --to 192.168.0.10:80
# http replies: # ENABLE NAT echo "1" > /proc/sys/net/ipv4/ip_forward
# NAT Forwarding Setup
$IPTABLES --table nat --append POSTROUTING --out-interface $ETH0 -j MASQUERADE $IPTABLES -A FORWARD -i $ETH1 -j ACCEPT
$IPTABLES -A FORWARD -i $ETH0 -j ACCEPT
$IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
Signature · 3 lines
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.5.1 - Release Date: 27/02/2005
Quoted 28 lines · Rudi Starcevic
Hi,
I have these rules below to enable:
a) http port-forwarding in requests
b) masquerading rules for http replies.It does seem to work OK but is very slow. After hours of looking I think the problem as to why it is so slow may be in my Iptables rules.
Can you see a double up or something that may cause a problem ? Or would you say it all looks fine and my problem is elsewhere ?
Thank you ..
$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT DROP
$IPTABLES -P FORWARD DROP# http requests: # Port-Forwarding setup $IPTABLES -t nat -A PREROUTING -i $ETH0 -p tcp --dport 80 -d 66.xxx.xx.100 -j DNAT --to 192.168.0.10:80# http replies: # ENABLE NAT echo "1" > /proc/sys/net/ipv4/ip_forward
Quoted 6 lines
# NAT Forwarding Setup
$IPTABLES --table nat --append POSTROUTING --out-interface $ETH0 -j MASQUERADE
$IPTABLES -A FORWARD -i $ETH1 -j ACCEPT
$IPTABLES -A FORWARD -i $ETH0 -j ACCEPT
$IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
you're basically not running a firewall at all--i would look elsewhere. the usual suspects:
* DNS resolution timing out
* Network interface speed/duplex mismatches
-j
--
"Another day, another box of stolen pens."
--The Simpsons