From: "Carlos Fernandez Sanz" <cfs-netfilter@nisupu.com>
To: Scott MacKay <scottmackay@yahoo.com>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: Routing problem
Date: Sat, 14 Feb 2004 09:47:06 +0100 [thread overview]
Message-ID: <000f01c3f2d7$1ff24f50$1530a8c0@HUSH> (raw)
In-Reply-To: 20040213171620.97236.qmail@web13904.mail.yahoo.com
Scott,
By "carrier expects traffic to come from one WAN IP" I don't mean it has to
have that origin IP but come from a router with that IP.
Obviously they assumed that the regular setup is
Internet <----> their router <-----> our router <------> Box with IP #1
(could be a firewall) <-----> NAT
(i.e. there would be one router whose job in life is to get traffic from
their router and direct it to us)
However we are a small company and we need to have everything in one box,
i.e. the router that connects with the carrier, the firewall, the web
server, etc :-)
----- Original Message -----
From: "Scott MacKay" <scottmackay@yahoo.com>
To: "Carlos Fernandez Sanz" <cfs-netfilter@nisupu.com>; "netfilter"
<netfilter@lists.netfilter.org>
Sent: Friday, February 13, 2004 18:16
Subject: Re: Routing problem
> AH, I think I get what you are saying.
> You have a linux doing NAT, 1 public IP on the outside
> and 1 private on the inside. You also have a spare
> public IP which you want to put on a client so they
> can do some funky things which requires them having a
> real IP address.
> 1 question about your statement. Where you say
> "carrier expects traffic to come from one WAN IP"
> kinda goes against what you implied by "public IP 2".
> If you have 2 pubic IPs, they they cannot expect your
> traffic to come from 1 WAN IP. Even if you NAT a
> private address explicitly to the 2nd public IP
> address that counts as 2. Do you have 1 or 2 public
> IP addresses?
> If you are given 2, then you should be able to do the
> config mentioned, putting the client on the same side
> as the router's public IP (since they are both in the
> same class C). If you have 1, well you are SOL.
>
>
>
>
>
>
>
>
> --- Carlos Fernandez Sanz <cfs-netfilter@nisupu.com>
> wrote:
> > > >
> > > > Before you ask: I can't connect this special
> > computer to the same place
> > I
> > > > connect the linux box (which would be the
> > obvious solution) because the
> > > > carrier expects traffic to come from one WAN IP,
> > owned by the linux box.
> > >
> > > How do they expect you to use any of the other IPs
> > in the pool they have
> > given
> > > you?
> >
> > I do use them by redirecting traffic from the linux
> > box to the destination
> > boxes (such as all trafic for public IP 2 goes to
> > 192.168.21.2, for
> > example). This works fine, *except* in this
> > particular case, where any
> > NATing is not an option. I need the computer behind
> > the linux box to
> > actually own the public address, because it signs
> > packets with it.
> >
> >
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> http://taxes.yahoo.com/filing.html
>
next prev parent reply other threads:[~2004-02-14 8:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 15:39 Routing problem Carlos Fernandez Sanz
2004-02-13 15:50 ` Antony Stone
2004-02-13 16:30 ` Carlos Fernandez Sanz
2004-02-13 17:12 ` Antony Stone
2004-02-14 8:41 ` Carlos Fernandez Sanz
2004-02-14 9:09 ` Antony Stone
2004-02-14 15:15 ` Carlos Fernandez Sanz
2004-02-14 15:19 ` Carlos Fernandez Sanz
2004-02-14 15:38 ` Antony Stone
2004-02-16 10:13 ` Problems with kernel 2.6.1 and iptables Jan Kaastrup
2004-02-16 10:26 ` Ray Leach
2004-02-16 10:47 ` Antony Stone
2004-02-16 11:19 ` Ray Leach
2004-02-16 13:18 ` Alexis
2004-02-16 14:05 ` Jan Kaastrup
2004-02-13 17:16 ` Routing problem Scott MacKay
2004-02-14 8:47 ` Carlos Fernandez Sanz [this message]
2004-02-13 16:53 ` John A. Sullivan III
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 7:23 Michelle Konzack
2004-07-27 7:42 ` Sven Schuster
2004-07-27 8:06 ` Michelle Konzack
2004-07-27 14:21 ` Sven Schuster
2004-07-28 8:32 ` Michelle Konzack
2003-08-13 18:26 GG Noris
2002-09-20 14:29 Routing Problem Tom Fischer
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='000f01c3f2d7$1ff24f50$1530a8c0@HUSH' \
--to=cfs-netfilter@nisupu.com \
--cc=netfilter@lists.netfilter.org \
--cc=scottmackay@yahoo.com \
/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