John Andersen schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
...
If I were you, I would simplify that whole scenario to having one SUSE server with three nics (you could force it to work with just two but why bother).
Two nics go to external interfaces (cable and adsl) and one nic for internal, and also to serve as your internal dhcp server.
That way, the only thing that needs extra routes defined is that single suse server. Then with something like Shorewall you set up your routing. Its much easier to configure dual ISPs and routes with shorewall in my opinion.
If you use an wireless router for laptops, put it inside, on the internal network, shut of dhcp on it, and use it as an access point only.
One machine to configure, set up dhcp, handle routes, manage vpns, traffic shaping, etc.
They way you have it you have pushed the routing problem to every internal machine. Thats overly complex and unnecessary. Any cheap PC with three knicks and a 2 gig hard drive can server as your router/firewall.
I appreciate your input, in fact I was considering using a triple homed firewall/router, but not to solve this problem. Doing this would be a work-around of the problem which is : why can't KNetworkmanager handle routes like ifup (or whatever it is) can. I will think it over again since I hope to replace some servers in the near future, but for now I want to keep what I have. Regards, Koenraad Lelong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org