-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Apr 12, 2008 at 2:43 AM, Koenraad Lelong wrote:

John Andersen schreef:

...

On Fri, Apr 11, 2008 at 3:39 AM, Koenraad Lelong wrote:

...

Hello, I have a laptop running 10.3 and the NIC's (wired and wireless) are managed with KNetworkmanager. It runs fine except that I seem unable to get the extra routes I set up in dhcp. Any thoughts ? -- Regards, Koenraad Lelong

Please explain Koenraad.

Usually when using dhcp one leaves routes to the dhcp client daemon because you are at the mercy of the dhcp server to determine what IP you will get at any given moment, and the routes are managed for you each with IP lease.

What additional routes are you trying to add?

Answering from home. Sorry for the confusion.

At work I have two Internet-connections : cable and adsl. Adsl provides my fixed IP-address, for mail and some other services, cable provides a higher-speed connection, for surfing the Internet. Each has it's own Suse-server which acts as firewall/proxy and each of these connect to a router connected to the Internet. Maybe this "drawing" helps :

Internet --- cable-router --- Suse 1 --- laptop |- other PC's Internet --- adsl-router --- Suse 2 --- desktop |- Other devices

My dhcp-server assigns a default gateway (Suse 1) that has access to the cable-connection. That gateway has no connection to the adsl router, so I set up a route in the dhcp-server to point at the "adsl-gateway" to access the router and those "other devices". I have also some vpn's via the adsl-router. For the far-end-addresses I also set up routes in the dhcp-server. On a desktop system, with non-KNetworkmanager setup, all is fine. If I execute "route" I see the extra routes and I can use them. But on my laptop I only see the default gateway, and I can't have access to those extra routes.

I hope this makes things more clear. A last remark : the laptop and the desktop run (Suse-)linux. It seems Windows can't handle those extra routes.

Regards, Koenraad Lelong.

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. - -- - ----------JSA--------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: http://getfiregpg.org iD8DBQFIAQg8v7M3G5+2DLIRAhzGAKCLVnWIm/izfEy1hk1Sll2JHxyYAwCgrmDC PDUD6JtwmUPkN9RglJp/ptc= =Or68 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, Apr 13, 2008 at 3:39 AM, Koenraad Lelong wrote:

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. --

You are exactly correct Koenraad, this does not solve your specific problem, but I think it is because you are using the wrong tool for the job. If you have custom routes that you need to setup each time it would seem that a tool designed principally for a roaming laptop user would not be the best choice. After all this routing would not be workable when you move the laptop to a coffee shop or something. To get things to work, I would switch back to Yast boot-time setup for those interfaces, or perhaps write a script to do the "route add" that you need. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org