Dave Howorth wrote:
On Sun, 2006-01-01 at 21:05 -0500, Paul Cartwright wrote:
On Sun January 1 2006 8:18 pm, Paul Cartwright wrote:
ok, well I thought I had this working, THEN I went ahead and upgraded KDE to 3.5. When i rebooted, I now have no wireless connection AGAIN. ... ok, so from the command line I added : route add default gw 192.168.10.1 eth1
and POOF, I now have internet back. So why am I having to do all these backflips to get this crap working???
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).
Why reboot? While it should be added to the settings, issuing the route command should keep it going until a reboot is really necessary. He can also restart networking, change run levels etc. The only software reason I know of, for requiring a reboot, is a kernel change.