I'm not sure if this should be here or in the desktop (or distribution>SUSE) forum, but I'll give it a shot.

This is a very strange and very annoying problem with a SUSE 11 custom (built with SUSE studio) instalation.

The bsic problem is the defualt route is there when I boot, but gos away when I dial out using kinternet (so now the internet dosen't work, when I dial it). I can then add it using the command:
/sbin/route add default gw 10.0.0.1 modem0
The net now works nicley. That's not the end of the problem though. If I hang up, or the connection times out, kinternet 'helpfully' removes the default route that I've manualy set up, then (becuase I have dial on demand turned on) will dial the internet again (which is what I want) but the internet is now broken because the default route is gone. I can add it manually again, and the net works.

And I've just noticed that the default route will disapear for no reason if the conection is left idle (such as while writing this post).

This would be infuriating if it was a desktop, but this is the headless router that's suposed to be serving the internet to my whole network, making it unworkable.

By the way, when I say the default route is gone, I mean deleted, not showing up in route -n command, ect. It's not just replacing it with something odd, it's removing it completly.

This box used to work exactly the way I wanted it to, using kinternet to dial a PPPoE service. Now I've switched to using an actual modem the whole thing is acting weird.

Any help would be apreciated here, and the most helpful comment wins half a biro.

I figured this out on my own (after spending days on it, the solution comes to me after I start asking questions on forums).

In the YaST configuration invoked from kinternet (right click -> configure with yast), buried in the tabs there is an tick box that says "default route". I tick the box it says "The current default route is for PPPoE0 do you want to change it?" I say yes, and now it works the way it did before.

Looks like the defualt route was there, but it was being set to a connection that no longer existed (and therefore null I guess). I suppose it defaults to on if there's no existing connections and off if there is.