From: "antonio.dibacco" <antonio.dibacco@aruba.it>
To: Rob Sterenborg <rob@sterenborg.info>
Cc: netfilter@lists.netfilter.org
Subject: Re: Routing through PtP and iptables
Date: Sat, 13 May 2006 12:41:25 GMT [thread overview]
Message-ID: <20060513124125.7833.qmail@mx1.aruba.it> (raw)
In-Reply-To: <000601c67679$67d1c940$0101000a@sterenborg.info>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
The two boxes will never be placed on the same LAN.
Thank you for your attention
Rob Sterenborg Scrive:
> netfilter-bounces@lists.netfilter.org scribbled on :
>
>> Hi all,
>>
>> I have two identical linux boxes (A e B), each one with two
>> interfaces: an ethernet (eth0 with ip 192.168.1.50) and an hdlc
>> (hdlc0). The two boxes are only connected via a link through their
>> hdlc interfaces. Because they have to be exactly the same, if I have
>> to assign an ip address to hdlc0 of A then the hdlc0 of B should have
>> the same ip address. Each one should have a default route that cannot
>> coincide with the hdlc interface. Every linux box has a web server.
>> When I connect with my notebook to box A I want to reach the web
>> server on A typing in my browser http://192.168.1.50 and I want to
>> reach web server on B typing http://192.168.1.50:8080 .
>> Some one knows how could it be possible?
>>
>> Thank you for your help,
>> Antonio.
>
> If Server A has IP 192.168.1.50, you *cannot* have a server B also on
> 192.168.1.50 in the samen LAN. You would have 1 IP address for multiple
> servers and that just isn't going to work.
>
> What you *can* do is :
> Server A = 192.168.1.50
> Server B = 192.168.1.51
> Forward requests to 192.168.1.50:8080 to 192.168.1.51(:8080 or whatever
> you like)
>
>
> Gr,
> Rob
>
>
prev parent reply other threads:[~2006-05-13 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 21:35 Routing through PtP and iptables Antonio Di Bacco
2006-05-12 23:56 ` Pascal Hambourg
2006-05-13 10:38 ` Rob Sterenborg
2006-05-13 12:41 ` antonio.dibacco [this message]
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=20060513124125.7833.qmail@mx1.aruba.it \
--to=antonio.dibacco@aruba.it \
--cc=netfilter@lists.netfilter.org \
--cc=rob@sterenborg.info \
/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