Thanks for that. I have it working now. Here is my much neater route table. My rules look scarey but I think thats ok. Sorry Im still using a few tables :) ip ro add 0.0.0.0/0 dev ppp0 proto static table main ip ro add 0.0.0.0/0 dev eth0 proto static table eth0 ip ro add 0.0.0.0/0 via 202.2.2.17 dev eth1 proto static table eth1 ip ro add 0.0.0.0/0 via 202.3.3.129 dev eth2 proto static table eth2 ip ro add from 202.1.1.128/25 via 202.3.3.129 proto static table eth2 My question is tho, I have your route patch in my kernel, but if I do a ifconfig eth1 down and then ifconfig eth1 up, stuff that was headed out eth1 before the down/up now goes out the default route ppp0 until I re-add the eth1 route. I believe that with your patch the routes should stay? Thanks again > On Thu, 13 Dec 2001, Stephen wrote: > > > Julian I am already using a kernel patched with your routes-2.2.19 patch > > Oh! But did you read the documents? > > > here is an example of my rule and route list i am presently trying and the > > errors i am getting. I have 202.1.1.0/25 + 2 other ips on ppp0 my main > > static ip link. The 202.2.2 is my adsl on eth1. 202.3.3 is my cable > > on eth2 which i try to route all my clients from 202.1.1.128/25 out of by > > default. > > No, there are some rules you must follow: > > - remove all your default routes from table main > > - all directly connected networks must be added to table main, > it includes all host routes (/32). Don't try to introduce errors > by using extra tables. It could work if you do them correctly. > > As result, all direct routes (without gateway) are in > table main and the hosts from all networks can talk directly IP > and ARP without hiting wrong gatewayed route by mistake. >
