Plant, Dean
2007-Feb-02 09:34 UTC
[CentOS] Default router on different subnet - Is it possible?
In the below example normal Internet traffic is routed as shown from node1 to internet1. The node1 defaultrouter points to the firewall and the firewall points to internet1. For node2 is it possible to add it's own link to the Internet passing through the same default router and firewall as node1. The links do not need to failover or provide any redundancy. node1---node1 defaultrouter--firewall--internet1(default route node1) node2--/ \-internet2(default route node2) I know a default route should be on the same local subnet but is there any routing trickery (or maybe iptables) I can do on node2 to get around this. Thanks Dean
Rodrigo Barbosa
2007-Feb-02 14:19 UTC
[CentOS] Default router on different subnet - Is it possible?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Feb 02, 2007 at 09:34:16AM -0000, Plant, Dean wrote:> In the below example normal Internet traffic is routed as shown from > node1 to internet1. The node1 defaultrouter points to the firewall and > the firewall points to internet1. For node2 is it possible to add it's > own link to the Internet passing through the same default router and > firewall as node1. The links do not need to failover or provide any > redundancy. > > node1---node1 defaultrouter--firewall--internet1(default route node1) > node2--/ \-internet2(default route node2) > > I know a default route should be on the same local subnet but is there > any routing trickery (or maybe iptables) I can do on node2 to get around > this.Nope. The only place you can implement this kind of stuff is on the firewall, using source based routing. You can configure the firewall routing table (using iproute) to route node1 traffic through internet1, and node2 traffic thorugh internet2. []s - -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFw0hgpdyWzQ5b5ckRAs0QAJ45B6vqdYsvfCywTD54GurRyDsC6ACeIlGt MHHyWUegtD5PL66YQPXo1dY=4bex -----END PGP SIGNATURE-----