From: "Carlos Fernandez Sanz" <cfs-netfilter@nisupu.com>
To: Antony Stone <Antony@Soft-Solutions.co.uk>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: Routing problem
Date: Fri, 13 Feb 2004 17:30:14 +0100 [thread overview]
Message-ID: <003301c3f24e$a8683b80$1530a8c0@HUSH> (raw)
In-Reply-To: 200402131550.25323.Antony@Soft-Solutions.co.uk
> >
> > 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.
next prev parent reply other threads:[~2004-02-13 16:30 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 [this message]
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
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='003301c3f24e$a8683b80$1530a8c0@HUSH' \
--to=cfs-netfilter@nisupu.com \
--cc=Antony@Soft-Solutions.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox