RE: PPTP+NAT+MASQ anyone?

RE: PPTP+NAT+MASQ anyone?

[Rob Sterenborg]

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

> I've kept trying now. many times, to do NAT+MASQ+PPTP, but as 
> soon as I 
> compile 2.4.18 (the only one I've managed to patch-o-matic) 
> and boot it, it 
> refuses to -j MASQUERADE. (invalid argument). Are anyone running this?

Yup, on my test-box : 2.4.20-rc1 (still, but it's doing nothing at the
moment).
I had no problems patching it however.


Rob

[-- Attachment #2: Type: text/html, Size: 863 bytes --]

hostname forwarding

[bernard]

I'm using iptables to redirect external requests depending on their 
port/protocol like this :

	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
	hostname B:80 -> public ip -> iptables -> 192.168.1.1:80

It works pretty well, thanks to iptables :-)

Now I want to redirect on a hostname basis on different private ip's 
like this :

	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
	hostname B:80 -> public ip -> iptables -> 192.168.1.2:80

Does anyone know a solution ?

Thanks for your help.

Bernard

Re: hostname forwarding

[Patrick Maartense]

this is not possible using ipotables

Apache however can very well handle this ..


On Wed, 11 Dec 2002, bernard wrote:

> I'm using iptables to redirect external requests depending on their 
> port/protocol like this :
> 
> 	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
> 	hostname B:80 -> public ip -> iptables -> 192.168.1.1:80
> 
> It works pretty well, thanks to iptables :-)
> 
> Now I want to redirect on a hostname basis on different private ip's 
> like this :
> 
> 	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
> 	hostname B:80 -> public ip -> iptables -> 192.168.1.2:80
> 
> Does anyone know a solution ?
> 
> Thanks for your help.
> 
> Bernard
> 

-- 
---
Kind Regards
Patrick Maartense (using Pine on a Text Console)

RE: hostname forwarding

[Rob Sterenborg]

> Now I want to redirect on a hostname basis on different private ip's 
> like this :
> 
> 	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
> 	hostname B:80 -> public ip -> iptables -> 192.168.1.2:80
> 
> Does anyone know a solution ?

Iptables will only forward (resolved) IP adresses (and/or ports).
If Host-A has the same IP address as Host-B, then packets will be
forwarded to one and the same internet IP address.
You could accept http traffic on, let's say, port 81 and redirect
traffic for Host-B:81 to 192.168.1.2:80, but I don't think that's what
you want : people would have to type http://Host-B:81 to enter the site.


Rob

Re: hostname forwarding

[Raymond Leach]

[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]

On Wed, 2002-12-11 at 17:06, Patrick Maartense wrote:
> this is not possible using ipotables
> 
Ummm, what is the -s parameter for then?
iptables -t nat -A PREROUTING -p tcp -s <hostname A> --dport 80 -j
REDIRECT --to-destination 192.168.1.1:80
iptables -t nat -A PREROUTING -p tcp -s <hostname B> --dport 80 -j
REDIRECT --to-destination 192.168.1.2:80

Or am I missing something?

Ray
> Apache however can very well handle this ..
> 
> 
> On Wed, 11 Dec 2002, bernard wrote:
> 
> > I'm using iptables to redirect external requests depending on their 
> > port/protocol like this :
> > 
> > 	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
> > 	hostname B:80 -> public ip -> iptables -> 192.168.1.1:80
> > 
> > It works pretty well, thanks to iptables :-)
> > 
> > Now I want to redirect on a hostname basis on different private ip's 
> > like this :
> > 
> > 	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
> > 	hostname B:80 -> public ip -> iptables -> 192.168.1.2:80
> > 
> > Does anyone know a solution ?
> > 
> > Thanks for your help.
> > 
> > Bernard
> > 
-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(  Raymond Leach                       )
 ) Knowledge Factory                  (
(                                      )
 ) Tel: +27 11 445 8100               (
(  Fax: +27 11 445 8101                )
 )                                    (
(  http://www.knowledgefactory.co.za/  )
 ) http://www.saptg.co.za/            (
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   o                                o
    o                              o
        .--.                  .--.
       | o_o|                |o_o |
       | \_:|                |:_/ |
      / /   \\              //   \ \
     ( |     |)            (|     | )
     /`\_   _/'\          /'\_   _/`\
     \___)=(___/          \___)=(___/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: hostname forwarding

[Raymond Leach]

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]

OK, that makes sense...

On Thu, 2002-12-12 at 09:16, Blizzards wrote:
> The host A and Host B share the same ip address.
> In this case -s is no useful because resolving host a and host b return 
> the same address, and the 1st match win.
> You can use APACHE name virtual host to handle this correctly.
> 
> G.
> 
> >>
> >>    
> >>
> >Ummm, what is the -s parameter for then?
> >iptables -t nat -A PREROUTING -p tcp -s <hostname A> --dport 80 -j
> >REDIRECT --to-destination 192.168.1.1:80
> >iptables -t nat -A PREROUTING -p tcp -s <hostname B> --dport 80 -j
> >REDIRECT --to-destination 192.168.1.2:80
> >
> >Or am I missing something?
> >
> >Ray
> >  
> >
-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(  Raymond Leach                       )
 ) Knowledge Factory                  (
(                                      )
 ) Tel: +27 11 445 8100               (
(  Fax: +27 11 445 8101                )
 )                                    (
(  http://www.knowledgefactory.co.za/  )
 ) http://www.saptg.co.za/            (
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   o                                o
    o                              o
        .--.                  .--.
       | o_o|                |o_o |
       | \_:|                |:_/ |
      / /   \\              //   \ \
     ( |     |)            (|     | )
     /`\_   _/'\          /'\_   _/`\
     \___)=(___/          \___)=(___/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: hostname forwarding

[Blizzards]

The host A and Host B share the same ip address.
In this case -s is no useful because resolving host a and host b return 
the same address, and the 1st match win.
You can use APACHE name virtual host to handle this correctly.

G.

>>
>>    
>>
>Ummm, what is the -s parameter for then?
>iptables -t nat -A PREROUTING -p tcp -s <hostname A> --dport 80 -j
>REDIRECT --to-destination 192.168.1.1:80
>iptables -t nat -A PREROUTING -p tcp -s <hostname B> --dport 80 -j
>REDIRECT --to-destination 192.168.1.2:80
>
>Or am I missing something?
>
>Ray
>  
>

Re: hostname forwarding

[bernard]

Thank again for your valuable help.

So apache can take http requests to do that but what's about the 
other protocols ?

It seems that squid can do a transparent proxy for some of them.

Do I need to use a specific solutions for each different protocol I 
want to set and what solution to use for the most common (telnet, 
pop, imap, ftp, ...) ?

Bernard

>this is not possible using ipotables
>
>Apache however can very well handle this ..
>
>
>On Wed, 11 Dec 2002, bernard wrote:
>
>>  I'm using iptables to redirect external requests depending on their
>>  port/protocol like this :
>>
>>	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
>>	hostname B:80 -> public ip -> iptables -> 192.168.1.1:80
>>
>>  It works pretty well, thanks to iptables :-)
>>
>>  Now I want to redirect on a hostname basis on different private ip's
>>  like this :
>>
>>	hostname A:80 -> public ip -> iptables -> 192.168.1.1:80
>>	hostname B:80 -> public ip -> iptables -> 192.168.1.2:80
>>
>>  Does anyone know a solution ?
>>
>>  Thanks for your help.
>>
>>  Bernard
>>
>
>--
>---
>Kind Regards
>Patrick Maartense (using Pine on a Text Console)