From: Ralph van Etten <ralph@brothom.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] Source based routing with two internet connections
Date: Tue, 03 Jul 2001 18:59:01 +0000 [thread overview]
Message-ID: <marc-lartc-99418675705361@msgid-missing> (raw)
Hi,
The next question is probably a FAQ but I'm really getting desperate and I
haven't found anything in the HOW-TO, the docs or archives about the
problems I have.
I have a Linux box with two connections to the internet (a fast and a
slow connection) and a private internal network. The linux box does
masquerading. Some PCs (PC B) on the private LAN must use the fast
connection, the rest of the hosts must use the slow connection.
internet internet
\ /
slow connection\ / fast connection
124.124.124.124 \ eth1 eth2/ 123.123.123.123
+-------------+
| Linux box |
| |
+-------------+
eth0| 192.168.11.2
|
----+-----+------+------
| |
| | 192.168.11.70
+--------+ +--------+
| PC a | | PC b |
+--------+ +--------+
Its almost exacly the same as described in the Adv. Routing HOW-TO.
The default route is set to eth1 and PC A and PC B can connect to the
internet using the slow link.
Then, when I use the following commands (fast is a name in
/etc/iproute2/rt_tables) :
#ip rule add from 192.168.11.70 table fast pref 102
#ip route add 0/0 dev eth2 table fast
#ip route flush cache
PC A can still connect to the internet using the slow link, but PC B
can't connect to the internet using the fast link.
When I do a traceroute or look at the packets on the interfaces I can see
that packets from PC B are routed to the fast link.
When I ping a host on the internet from PC B, the host which is pinged
send replies on eth2, but the linux box doesnt forward them to PC B.
So, I think there is something wrong with masquerading.
Masquerading is set up using ipchains :
ipchains -A forward -i eth2 -j MASQ -l
With -l the ping requests from PC B show up in the syslog.
I'm using kernel 2.2.17, I've compiled the kernel with all the relevant
networking options for advanced routing. Does this kind of routing work
with 2.2.17 ?
I really have no idea what is wrong and was hoping someone else has a
similar setup working and can give me some clues on how to get it to work.
Thanks,
Ralph.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-07-03 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 18:59 Ralph van Etten [this message]
2001-07-04 7:26 ` [LARTC] Source based routing with two internet connections Arthur van Leeuwen
2001-07-04 18:32 ` Ralph van Etten
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-99418675705361@msgid-missing \
--to=ralph@brothom.nl \
--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.