I was messing with this a bit also. I have this:
/sbin/iptables -t nat -A PREROUTING -p TCP -i eth0 --dport 80 -j DNAT
--to-destination 192.168.0.2:80
From the firewall (192.168.0.1) I can do this:
{0}:wally:/etc/init.dtelnet 192.168.0.2 80
Trying 192.168.0.2...
Connected to 192.168.0.2.
On Thu, Sep 20, 2001 at 08:56:52AM -0600, Robert L. Harris wrote:
{0}:wally:/etc/init.dtelnet 192.168.0.1 80
Trying 192.168.0.1...
telnet: Unable to connect to remote host: Connection refused
may seem like a silly suggestion, but i beleive iptables has the same
rule as in ipchains where you
This is a masq'ing firewall so that is in my firewall rules already. Good
thought though.
Thus spake Adam McDaniel ([EMAIL PROTECTED]):
On Thu, Sep 20, 2001 at 08:56:52AM -0600, Robert L. Harris wrote:
{0}:wally:/etc/init.dtelnet 192.168.0.1 80
Trying 192.168.0.1...
telnet: Unable to
Hi,
Could someone please tell me why this command won't forward any www calls to
192.168.1.1 (firewall + gateway) to 192.168.1.2 (apache server).
iptables -t nat -A PREROUTING -p TCP --dport 80 -j DNAT --to-destination
192.168.1.2:80
What I can't figure is why that doesn't work, when the
Hereward Cooper wrote:
Hi,
Could someone please tell me why this command won't forward any www calls to
192.168.1.1 (firewall + gateway) to 192.168.1.2 (apache server).
iptables -t nat -A PREROUTING -p TCP --dport 80 -j DNAT --to-destination
192.168.1.2:80
What I can't figure is why that
On Tuesday 18 September 2001 03:32 pm, Hereward Cooper wrote:
Hi,
Could someone please tell me why this command won't forward any www calls
to 192.168.1.1 (firewall + gateway) to 192.168.1.2 (apache server).
iptables -t nat -A PREROUTING -p TCP --dport 80 -j DNAT --to-destination
On Tue, Sep 18, 2001 at 08:32:59PM +0100, Hereward Cooper wrote:
Could someone please tell me why this command won't forward any www
calls to 192.168.1.1 (firewall + gateway) to 192.168.1.2 (apache
server).
iptables -t nat -A PREROUTING -p TCP --dport 80 -j DNAT --to-destination
7 matches
Mail list logo