From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Two Interfaces and two link
Date: Mon, 27 Jan 2003 22:31:29 +0000 [thread overview]
Message-ID: <marc-lartc-104370675427347@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104370484424590@msgid-missing>
Viaris,
It sounds like this is what you are trying to describe:
+--------------------+
gateway | | gateway
.201 <--------| your box |---------> .233
eth1 | | eth0
200.9.189.202/29 | | 165.98.111.234/29
+--------------------+
: IF-ETH0 --> 165.98.111.234 Gw 165.98.111.233 Netmask 255.255.255.248
: IF-ETH0 --> 200.9.189.202 GW 200.9.189.201 Netmask 255.255.255.248
I presume from below that the second line here is actually eth1
: Host that I need to route is: 200.9.189.241
Where do you need to route this host? Is it reachable via 200.9.189.201?
If so, then you need no "ip rule" commands:
# ip route add 200.9.189.241 via 200.9.189.201
: ip route add 165.98.111.232 dev eth0 src 165.98.111.234 table T1
: ip route add default via 165.98.111.233 table T1
: ip route add 200.9.189.200 dev eth1 src 200.9.189.202 table T2
: ip route add default via 200.9.189.201 table T2
: echo 200 office_priv >> /etc/iproute2/rt_tables
: ip rule add from 200.9.189.241 table office_priv
: ip route add default via 200.9.189.202 dev eth1 table Pedro
: ip route flush cache
What on earth are you trying to do here? Where do you define table
"Pedro"? Why are you creating a default route to your own ethernet IP?
(Hint: this is distinctly not what you want.)
: Now, if I run the command route -n, the output is:
The conventional "route -n" command does not show you anything other than
the main routing table. In order to observe your routing tables, you
should use:
# ip route show # -- table main is implied
# ip route show table main # -- or explicit
# ip route show table office_priv # -- or another table....
: All the traffic http is send to interface eth0, all work fine, But I cant
: send any specific host fot the other interface (ETH1), since the host
: 200.9.189.241 I load the web pages http://visualroute.visualware.com/ in
: this site say that my Ip is 165.98.111.234, if I did the routing for this
: host, Why the trafic of this host continue outgoing for the ETH0?, I need
: that this host have outgoing in the interface ETH1.
If you wish to reach the host 200.9.189.241 via eth1 then get rid of all
of the "ip rule" cruft you have introduced, and use simply:
# ip route add 200.9.189.241 via 200.9.189.201
Good luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-27 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 21:59 [LARTC] Two Interfaces and two link Viaris
2003-01-27 22:31 ` Martin A. Brown [this message]
2003-01-28 1:56 ` Viaris
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=marc-lartc-104370675427347@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.