-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 15 April 2003 11:05, Martin A. Brown scrawled: > Torsten, > > This is not really a LARTC question (unless you fetch mail from an > arbitrary number of servers, in which case you'll need the > link-load-sharing multiple routing tables solution). > > I'm guessing you solution is quite easy....see below. > > : I have a Debian-Woody-3.0 Router with 3 NIC's. Kernelversion 2.4.18 > > [ nice netmap snipped ] > > : Mail-Traffic over ISDN-Router > : WWW-Traffic over DSL-Router > : But why? > > [ interface definitions snipped ] > > : Is this correct? > > Well, yes. But not complete. > > : ### my route: > : Kernel IP routing table > : Destination Gateway Genmask Flags Metric Ref Use > : Iface > : 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 > : eth2 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 > : 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 > : 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 > : 0 0 eth0 and now my firewall-script: > > Are you fetching mail from a particular mailserver? If so: > > # mailserver=213.165.64.20 > # route add -host $mailserver gw 192.168.2.1 > > Or > > # mailserver=213.165.64.20 > # ip route add $mailserver via 192.168.2.1 > > -Martin Wouldnt setting up ip rules to forward the appropriate traffic through the proper gateway be better? Ashok - -- - ----------------------------------------------------------------------------- My public key: gpg --recv-keys --keyserver blackhole.pca.dfn.de DCB44F2E http://pgp.mit.edu:11371/pks/lookup?search=N+N+Ashok+%28CSE+MSU%29+%3Cnnashok%40yahoo.com%3E&op=index [Fingerprint: 4D6D B9F3 D2B6 A22A F4E5 5763 4615 E956 DCB4 4F2E ] - ----------------------------------------------------------------------------- "...there is nothing so unnatural as the commonplace." Sir Arthur Conan Doyle in "Adventures of Sherlock Holmes: A Case of Identity" - ----------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+nEX9RhXpVty0Ty4RAufDAJsE4zY/mnP0RLRdJsVEpNmlv8JWRACgiK/a k6zwQXUERfKE0EFYO/e2LG0= =YIXJ -----END PGP SIGNATURE-----
