Oops my bad ... didn't read the docs right and tried to use the
gateway instead of the interface IP ... ignore the post!
Rudolf
[Snip]pets of what Rudolf Potucek <(E-Mail Removed)> wrote:
: Hi All!
: I have finally ventured into the realm of *real* networking and I
: have run into problems:
: I have a linux router (debian woody, 2.4.18-13, iproutes2) with three
: NICS. The basic configuration is as firewall/router with two uplinks
: to different networks. So far so good, but the problem is that one
: of the outgoing neetworks is, per necessity, behind a router on a
: private IP:
: My Network Router World
: 192.168.1.0/24 --- eth1 192.168.1.254
: eth0 aaa.bbb.ccc.ddd --- net1
: eth0 192.168.0.254
: |
: +--- router ------------- net2
: 192.168.0.1
www.xxx.yyy.zzz
: I have added a static route through eth2 to
www.xxx.yyy.zzz. In the
: default configuration this works well for outgoing connections but
: breaks for incoming connections because the kernel sees the original
: IP and replies on the DEFAULT route which breaks things.
: I tried following the "advanced routing" howto but I ran into two
: difficulties:
: (1) Adding a source route
: ip route add $IP_NET1 dev $IF1 src $IP1
: fails, presumably because ip route does not have a 'src' parameter.
: Is this because the kernel/iproute version is too old to do this?
: (2) Adding the route to an individual table does seem to work, i.e.
: I get not errors and the oute shows up in the appropriate tables, but
: this has no effect ... HOW do I correctly specify the route to the
:
www.xxx.yyy.zzz network?
: Thanks for all pointers,
: Rudolf
--
It would be really bad for my selfesteem to marry someone I don't love.
It would make me feel like I am selling myself.
-- Marije
Interesting. In the American system it would be good for your selfesteem:
"look I am important enough that this *rich* guy will marry me!"
--Rudolf