From: Lexx <lexx@paragina.homeip.net>
To: netfilter@lists.netfilter.org
Subject: Re: port forwarding form IP range
Date: Tue, 14 Mar 2006 12:54:10 +0200 [thread overview]
Message-ID: <4416A0D2.20900@paragina.homeip.net> (raw)
Try running ethereal on the macines to test your connections...
I hava a similar setup (in the nat way):
THIS IS NOT A QUESTION BUT AN ANSWER... (i'm just explaing what i did)
So my setup is like this:
1 external ip; more computers on the lan. What I required was: if one of
the internal computers on the lan tries to connect to a dnated port it
should start talking with the destined computer...
Basicaly it was the same from the nat point of view (dnat to the same
interface)...
i first did the rules as you did...
and if i sent something like
lanip1 -> extip:dnatport
it would be translated in to lanip1->lnaip2:dnatport
the lanip2 machine would send back
lanip2:dnatport->lanip1 which would go directly to machine lanip1....
The problem was that the lanip1 machine was expecting an answer from
extip:dnatport not lanip2 so it would disregard the packet sent back....
My soulution was addaing the following two rules
iptables -t nat -A POSTROUTING -o lan_interface -s
lan_network/subnetmask -d lan_network/subnetmask -j SNAT --to-source
lan_gw_ip
iptables -A FORWARD -i lan_interface -o lan_interface -j ACCEPT
what this two rules do is force the connection to be like
lanip1 - gw - lanip2 (so all packets pass through the gw)
in your case instead of the above two rules i think that you can also do
something like: (on the proxy machines; i might be wrong beacuase this
would render the gw connections table a bit off track):
iptables -A POSTROUTING -j SNAT --to-source lan_gw_ip
so all packet going to the proxy will go like lanip1 - gw - proxy
and all packets will come back proxy - lanip1 (but the source ip will be
the gw)
If you have a better way please post it... (my gw is using a similar
setup as i said)
Cheers,
Silviu
Rob Sterenborg wrote:
>On Mon, March 13, 2006 12:02, Nilesh wrote:
>
>
>>Hi Rob,
>>
>>The default FORWARD policy is ACCEPT.
>>
>>
>
>If this is a firewall that is connected to the internet, you'd better set it
>to DROP (or have a last rule that says DROP or REJECT) and make it work with
>the state match (RELATED and ESTABLISHED)...
>
>
>
>>Yes I am trying the rules
>>
>>iptables -I PREROUTING -t nat -s 192.168.0.10 -p tcp
>>--dport 80 -j DNAT --to 192.168.0.3:3128
>>iptables -I PREROUTING -t nat -s 192.168.0.10 -p tcp
>>--dport 3128 -j DNAT --to 192.168.0.3:3128
>>
>>iptables -A FORWARD -s 192.168.0.10 -i eth1 -d
>>192.168.0.1 -o eth1 -p tcp --sport 1024:65535 --dport
>>3128 -j ACCEPT.
>>
>>
>
>You are PREROUTING to 192.168.0.3 but you allow forwarding to 192.168.0.1.
>That doesn't match and therefore this will not work.
>
>
>
>>Rob, I am trying to forward all request coming from IP
>>192.168.0.10 port 3128 and 80 to 192.168.0.3 port
>>3128.
>>
>>
>
>Let's keep it simple at first : you can always make the rule more restrictive
>if it works (and if you need to).
>
>$ipt -t nat -A PREROUTING -i eth1 -s 192.168.0.10 -p tcp \
> --dport 3128 -j DNAT --to 192.168.0.3
>
>$ipt -A FORWARD -i eth1 -s 192.168.0.10 -d 192.168.0.3 \
> -p tcp --dport 3128 -j ACCEPT.
>
>I must say that I've never tried forwarding "back" to the same interface..
>Don't know for sure if it's going to work.
>
>
>
>>so 192.168.0.10 will use the 192.168.0.3 proxy server
>>not the 192.168.0.1 proxy server.
>>
>>
>
>
>
>
>Please don't top-post.
>
>
>
>
>
>Gr,
>Rob
>
>
>
>
>
>
>
>>--- Rob Sterenborg <rob@sterenborg.info> wrote:
>>
>>
>>
>>>On Mon, March 13, 2006 09:53, Nilesh wrote:
>>>
>>>
>>>>Thanks Leandro,
>>>>
>>>>I have tried with this rules but unfortunately not
>>>>working.
>>>>Squid server running on the 192.168.0.3 and its
>>>>working fine. I have not installed any firewall
>>>>
>>>>
>>>on
>>>
>>>
>>>>the 192.168.0.3.
>>>>In my Internet browser settings If I chnage the
>>>>settings from 192.168.0.1:3128 to 192.168.0.3:3128
>>>>
>>>>
>>>I
>>>
>>>
>>>>can surf the web.
>>>>but If I dont change to 192.168.0.3:3128 proxy
>>>>settings I get the connection timout error.
>>>>
>>>>I think DNAT is not working
>>>>
>>>>
>>>Probably you tell Netfilter to do DNAT, but are not
>>>allowing it.
>>>Do you have a FORWARD rule that allows this traffic
>>>or is your policy ACCEPT ?
>>>
>>>Please don't top-post.
>>>
>>>
>>>Gr,
>>>Rob
>>>
>>>
>>>
>>>
>>>>--- Leandro Silva <lansoweb@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>>>Hello !
>>>>>
>>>>>You can use something like that:
>>>>>
>>>>>iptables -I PREROUTING -t nat -s 192.168.0.10 -p
>>>>>
>>>>>
>>>tcp
>>>
>>>
>>>>>--dport 80 -j
>>>>>DNAT --to 192.168.0.3:3128
>>>>>iptables -I PREROUTING -t nat -s 192.168.0.10 -p
>>>>>
>>>>>
>>>tcp
>>>
>>>
>>>>>--dport 3128 -j
>>>>>DNAT --to 192.168.0.3:3128
>>>>>
>>>>>If you have iprange compiled for iptables you can
>>>>>use:
>>>>>
>>>>>iptables -I PREROUTING -t nat -m iprange
>>>>>
>>>>>
>>>--src-range
>>>
>>>
>>>>>192.168.0.10-192.168.0.20 -p tcp --dport 80 -j
>>>>>
>>>>>
>>>DNAT
>>>
>>>
>>>>>--to
>>>>>192.168.0.3:3128
>>>>>iptables -I PREROUTING -t nat -m iprange
>>>>>
>>>>>
>>>--src-range
>>>
>>>
>>>>>192.168.0.10-192.168.0.20 -p tcp --dport 3128 -j
>>>>>DNAT --to
>>>>>192.168.0.3:3128
>>>>>
>>>>>I hope this can help,
>>>>>Leandro
>>>>>
>>>>>2006/3/11, Nilesh <niluforalways@yahoo.com>:
>>>>>
>>>>>
>>>>>>Dear all,
>>>>>>
>>>>>>I have two squid proxy servers and two ISP
>>>>>>
>>>>>>1) 192.168.0.1 port 3128
>>>>>>2) 192.168.0.3 port 3128
>>>>>>
>>>>>>We have around 70 comps assigned IP's between
>>>>>>192.168.0.4 to 192.168.0.250
>>>>>>The default proxy we are using is 192.168.0.1
>>>>>>
>>>>>>
>>>>>which is
>>>>>
>>>>>
>>>>>>on the ISP 1.
>>>>>>Now I have configured 192.168.0.3 squid proxy
>>>>>>
>>>>>>
>>>>>server
>>>>>
>>>>>
>>>>>>on ISP 2 line.
>>>>>>Both ISP 1 and ISP 2 are landing (connected) on
>>>>>>
>>>>>>
>>>>>the
>>>>>
>>>>>
>>>>>>same Switch.
>>>>>>
>>>>>>Now I want setup the request coming from IP
>>>>>>
>>>>>>
>>>range
>>>
>>>
>>>>>>(192.168.0.10 to 192.168.0.20) for the
>>>>>>192.168.0.1:3128
>>>>>>Will be forward to 192.168.0.3:3128
>>>>>>So the users from this IP range will access
>>>>>>
>>>>>>
>>>only
>>>
>>>
>>>>>>192.168.0.3 proxy server.
>>>>>>
>>>>>>Could any one please help me which rules should
>>>>>>
>>>>>>
>>>I
>>>
>>>
>>>>>use
>>>>>
>>>>>
>>>>>>in IPTABLES .
>>>>>>
>>>>>>I have attached herewith my rc.firewall file.
>>>>>>
>>>>>>Please help me.
>>>>>>
>>>>>>Regards
>>>>>>Nilesh.
>>>>>>
>>>>>>
>
>
>
>
>
next reply other threads:[~2006-03-14 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 10:54 Lexx [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 13:13 port forwarding form IP range Nilesh
2006-03-13 11:39 Nilesh
2006-03-13 12:04 ` Seferovic Edvin
2006-03-13 11:37 Nilesh
2006-03-11 12:24 Nilesh
2006-03-11 12:40 ` Leandro Silva
2006-03-13 8:53 ` Nilesh
2006-03-13 9:15 ` Rob Sterenborg
2006-03-13 11:02 ` Nilesh
2006-03-13 11:09 ` Seferovic Edvin
2006-03-13 16:22 ` Rob Sterenborg
[not found] ` <20060314103323.21090.qmail@web50515.mail.yahoo.com>
2006-03-14 12:12 ` Rob Sterenborg
2006-03-20 6:54 ` Nilesh
2006-03-20 9:39 ` Nilesh
2006-03-20 12:39 ` Rob Sterenborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4416A0D2.20900@paragina.homeip.net \
--to=lexx@paragina.homeip.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.