From: Leonardo Carneiro <lscarneiro@veltrac.com.br>
To: netfilter@vger.kernel.org
Subject: Re: access problem
Date: Tue, 17 Mar 2009 14:23:39 -0300 [thread overview]
Message-ID: <49BFDC9B.7080602@veltrac.com.br> (raw)
Hi Paulo,
tks for the tip, i already have a internal DNS, but i don't have a
external one =/
anyother ideas?
paulobruck1 escreveu:
> Em Seg, 2009-03-16 Ã s 16:41 -0300, Leonardo Carneiro escreveu:
>
>> Hi everyone.
>>
>
> Hi Leonardo
>
>
>> I'm new in the list and hope have a nice time here.
>> First of all, sorry about my poor enlgish, i'm from Brasil.
>>
>>
> welcome...80)
>
>
>
>> I've got a standard scenario with a private network (192.168.1.0/24)
>> beeing natted by a internet server (192.168.1.1) running iptables 1.3.0.
>>
>> In the private network I have a application server (192.168.1.2) running
>> a service on port 5222. The port is properly forwarded in internet
>> server, and users across the internet can access the service through the
>> public IP of the internet server.
>>
>> Users on the private network can access the service through the private
>> IP of the server, but cannot access using the public ip. Accessing using
>> the public ip would be very usefull, since lots of users have notebooks
>> and they access the service inside and outside the private network
>>
>> those are interface infos and the rules forwarding the port to the
>> application server:
>> eth0: public IP
>> eth1: private network, 192.168.1.1
>>
>>
> If you like your intenal users use this ip, install a Internal DNS for
> them and use at your externat ip use a dns too. Example:
>
> Internal DNS
> aplicationsserver IN A 192.168.1.1
>
> EXternal DNS
> applicationserver IN A XXX.XXX.XXX.XXX
> ( your public IP that is redirect to 192.168.1.1)
>
>
> Thats all...
>
>
> best regards
>
>
>
>> iptables -A PREROUTING -p tcp -m tcp -d [private_ip] -i eth0 --dport
>> 5222 -j DNAT --to-destination 192.168.1.2
>> iptables -A FORWARD -p tcp -m tcp -d 192.168.1.2 -i eth0 -o eth1 --dport
>> 5222 -j ACCEPT
>>
>> I've done some tests, adding some rules like
>>
>> iptables -A PREROUTING -p tcp -m tcp -d [private_ip] -i eth1 --dport
>> 5222 -j DNAT --to-destination 192.168.1.2
>> iptables -A FORWARD -p tcp -m tcp -d 192.168.1.2 -i eth0 -o eth1 --dport
>> 5222 -j ACCEPT
>>
>> or just
>>
>> iptables -A PREROUTING -p tcp -m tcp -d [private_ip] -i eth1 --dport
>> 5222 -j DNAT --to-destination 192.168.1.2
>>
>> but i just cannot connect using the public ip =S
>>
>> sometimes the server answer the request, but using the private ip, no
>> the public ip requested by the host, and sometimes the server just not
>> answer the request.
>>
>> any ideas how can i solve this?
>>
>> tks in advance.
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
>
next reply other threads:[~2009-03-17 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 17:23 Leonardo Carneiro [this message]
2009-03-18 11:26 ` access problem Brian Austin - Standard Universal
2009-05-26 13:20 ` Leonardo Carneiro
-- strict thread matches above, loose matches on Subject: below --
2009-03-16 19:41 Leonardo Carneiro
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=49BFDC9B.7080602@veltrac.com.br \
--to=lscarneiro@veltrac.com.br \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox