Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Carlos Fernandez Sanz" <cfs-netfilter@nisupu.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Routing problem
Date: Fri, 13 Feb 2004 16:39:48 +0100	[thread overview]
Message-ID: <002c01c3f247$9d3ee350$1530a8c0@HUSH> (raw)

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

I have a small problem setting up a routing exception here.

We have a small LAN with NAT-based internet access. Nothing special here. 
The router is a Linux box, with two NICs. One of them has a private address. The other one has a WAN address (it's a requirement of our provider that we use this address even if we have public addresses). 

Anyway, one of our users needs to go out using a public IP, and NAT doesn't do, because he needs to establish a connection encrypted where the IP address is part of a signature.

We do have spare IPs. The problem is that I can't add a route to him, route returns "network is unreachable".

Suppose NIC A in the linux box (route) is 192.168.21.1. NIC B is our public IP 1 (of a pool of five) A.B.C.1. Everyone gets out using this IP and NAT.
Now I want someone in the LAN to own the public IP A.B.C.2, however he is connected to the internal switch. 
I tried to do this

route add A.B.C.2 gw A.B.C.2 dev eth0 

But I get "network unreachable".

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. 

All suggestions welcome.

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

             reply	other threads:[~2004-02-13 15:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 15:39 Carlos Fernandez Sanz [this message]
2004-02-13 15:50 ` Routing problem 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
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='002c01c3f247$9d3ee350$1530a8c0@HUSH' \
    --to=cfs-netfilter@nisupu.com \
    --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