Bruce Marshall wrote:
On Monday 02 January 2006 07:27, Paul Cartwright wrote:
On Mon January 2 2006 5:10 am, Dave Howorth wrote:
The key word is 'reboot'. AFAIK, 'route' manipulates the running kernel, not the permanent settings. Set your gateway using Yast or by editing the network config files (sorry, I'd have to look it up to tell you exactly which one).
actually I did reboot, a number of times, and I also did if/up/down and network stop/start. What I'm trying to say is, wired routing wasn't a problem, the network came up and stays up. Wireless configuration is more of that "black box" syndrome.. I've been working on it for 3 days, and I still had to do manual configurations to get it to work, and I don't know if it will work when I reboot.
The only time I have seen this problem is when there is both a wired NIC and a wireless NIC in the same machine. And the network config really doesn't know which one should point to the gateway.
Yabbut, aren't you *supposed* to get this information from the DHCP server? I've been having similar problems with my laptop, in situations where a Windoze machine will *always* get *everything* it needs when it receives its dynamic IP (default route, gateway, nameservers, etc), but my SuSE machine is a crapshoot. I've been able to get by by manually using 'route add' and editing /etc/resolv.conf from the command line, but it's pretty pathetic when you have to borrow a nearby Win machine in order to pull the settings off of. There have been a couple situations where this has left me high and dry, like hotels with wireless internet. I don't know why, but this is one thing that the various Win flavors appear to handle much more dependably than SuSE.