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. Now when I bring up kinternet check connection, it shows: Default route- invalid default route: cannot read /proc/net/route: SUccess under name service is says name server ok, and gives me the address of my router, 192.168.10.1 this is on SUSE 10.0 KDE 3.5, wireless Intel Pro 2915ABG. -- Paul Cartwright Registered Linux user # 367800
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. Now when I bring up kinternet check connection, it shows:
Default route- invalid default route: cannot read /proc/net/route: SUccess
under name service is says name server ok, and gives me the address of my router, 192.168.10.1
this is on SUSE 10.0 KDE 3.5, wireless Intel Pro 2915ABG.
from a konsole window I ran : route and there was no default gateway. 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??? -- Paul Cartwright Registered Linux user # 367800
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). Cheers, Dave
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.
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. -- Paul Cartwright Registered Linux user # 367800
On Mon, 2006-01-02 at 07:27 -0500, 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.
Sorry I obviously phrased that badly! What I meant was - you said that you did a reboot, and I'm saying that was what caused you to lose the effect of the route command. You made your system work in a way that doesn't persist over a reboot. You need to use a different technique to fix it permanently - use Yast or edit config files directly.
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.
Sadly, I don't think you'll find anybody that will disagree with you. Wired networking is inherently simpler and it's also been around in a relatively stable form for MUCH longer. So the configuration procedures are much better established and simpler for the user. But it sounds like you did get your wireless going. So you've found all the important factors. Now you just need to make the changes permanent. You're almost there. And IMHO, rebooting after you've made the changes is an excellent thing to do because it tests that you have made the right changes. If you don't reboot and next month do something else (change a printer?) and the month after do something else etc, then when you finally do reboot you may find a whole bunch of things stop working and you won't have a clue what the reason is. It could be any one, or any combination of all the things you've done since the last reboot. It's much easier to make sure each set of changes are persistent individually, in my experience. Cheers, Dave
On Mon January 2 2006 10:11 am, Dave Howorth wrote:
actually I did reboot, a number of times, and I also did if/up/down and network stop/start.
Sorry I obviously phrased that badly! What I meant was - you said that you did a reboot, and I'm saying that was what caused you to lose the effect of the route command. You made your system work in a way that doesn't persist over a reboot. You need to use a different technique to fix it permanently - use Yast or edit config files directly.
what happened was, I got wireless working. THEN I updated KDE to 3.5 and rebooted. That's when I lost wireless. I had rebooted to get wireless working, made no changes to it, THEN did the KDE upgrade. At least that's my story and I'm sticking to it! I'll go back and check my settings and reboot..
Sadly, I don't think you'll find anybody that will disagree with you. Wired networking is inherently simpler and it's also been around in a relatively stable form for MUCH longer. So the configuration procedures are much better established and simpler for the user.
and of course windows makes it work and is supported by most tech support groups...
But it sounds like you did get your wireless going. So you've found all the important factors. Now you just need to make the changes permanent. You're almost there.
that's what I'm trying to do !
And IMHO, rebooting after you've made the changes is an excellent thing to do because it tests that you have made the right changes. If you don't reboot and next month do something else (change a printer?) and the month after do something else etc, then when you finally do reboot you may find a whole bunch of things stop working and you won't have a clue what the reason is. It could be any one, or any combination of all the things you've done since the last reboot. It's much easier to make sure each set of changes are persistent individually, in my experience.
exactly. It is much easier to trouble shoot ONE change.. I do try and reboot after changing anything important, or adding software.. always install kernel changes by themselves,etc..
Cheers, Dave
happy new year!! -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.bellsouth.net/p/PWP-pcartwright/key.asc
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.
On Mon January 2 2006 10:23 am, Bruce Marshall wrote:
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.
that might be the problem, eth0 is a wired LAN card, eth1 is the wireless. In my case ( at home) they should BOTH point to the gateway, because it is my wireless router, and that should be part of the wireless setup, or did it just ask for DHCP server.. now I forget.. -- Paul Cartwright Registered Linux user # 367800
On Monday 02 January 2006 10:33, Paul Cartwright wrote:
On Mon January 2 2006 10:23 am, Bruce Marshall wrote:
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.
that might be the problem, eth0 is a wired LAN card, eth1 is the wireless. In my case ( at home) they should BOTH point to the gateway, because it is my wireless router, and that should be part of the wireless setup, or did it just ask for DHCP server.. now I forget..
If they are both on the same subnet... (probably) they *can't* both point to the same gateway. If they did, which path should the system take? This is most likely your problem and you can test that by deleting the wired nic from your config until you sort it out.
On Mon January 2 2006 11:56 am, Bruce Marshall wrote:
If they are both on the same subnet... (probably) they *can't* both point to the same gateway. If they did, which path should the system take?
ok, so they are on the same subnet, 192.168.10.X
This is most likely your problem and you can test that by deleting the wired nic from your config until you sort it out.
that's not a permanent fix, what is the real answer? I want to be able to use the wireless at home, do I just use it ewxclusively and disable the wired NIC at home? what other options would you suggest? -- Paul Cartwright Registered Linux user # 367800
On Mon, 2006-01-02 at 12:12 -0500, Paul Cartwright wrote:
On Mon January 2 2006 11:56 am, Bruce Marshall wrote:
If they are both on the same subnet... (probably) they *can't* both point to the same gateway. If they did, which path should the system take?
ok, so they are on the same subnet, 192.168.10.X
This is most likely your problem and you can test that by deleting the wired nic from your config until you sort it out.
that's not a permanent fix, what is the real answer? I want to be able to use the wireless at home, do I just use it ewxclusively and disable the wired NIC at home? what other options would you suggest?
Yes, use one or the other but not both. You only invite trouble if you try to use both at the same time. Not saying it can't be done but it is troublesome. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Monday 02 January 2006 12:12, Paul Cartwright wrote:
On Mon January 2 2006 11:56 am, Bruce Marshall wrote:
If they are both on the same subnet... (probably) they *can't* both point to the same gateway. If they did, which path should the system take?
ok, so they are on the same subnet, 192.168.10.X
This is most likely your problem and you can test that by deleting the wired nic from your config until you sort it out.
that's not a permanent fix, what is the real answer? I want to be able to use the wireless at home, do I just use it ewxclusively and disable the wired NIC at home? what other options would you suggest?
That's what I do... (disable one) I don't know what would happen if you made them both DHCP but the problem is there can only be *ONE* default gateway and that gw point to an ethx (either 0 or 1 in your case) If this is a laptop that you want to move around to different environments then you need to look into some of the net configuration schemes such as netgo. Check the archives on those.
On Mon January 2 2006 12:27 pm, Bruce Marshall wrote:
That's what I do... (disable one) I don't know what would happen if you made them both DHCP but the problem is there can only be *ONE* default gateway and that gw point to an ethx (either 0 or 1 in your case)
I guess I didn't think about "only one" default gateway.. this dual-card setup is kinda new to me!
If this is a laptop that you want to move around to different environments then you need to look into some of the net configuration schemes such as netgo. Check the archives on those.
found it at freshmeat and downloaded it. I'll be traveling in 2 weeks, so I have time to play with it! -- Paul Cartwright Registered Linux user # 367800
On Monday 02 January 2006 07:33, Paul Cartwright wrote:
On Mon January 2 2006 10:23 am, Bruce Marshall wrote:
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.
that might be the problem, eth0 is a wired LAN card, eth1 is the wireless. In my case ( at home) they should BOTH point to the gateway, because it is my wireless router, and that should be part of the wireless setup, or did it just ask for DHCP server.. now I forget..
-- Paul Cartwright Registered Linux user # 367800
If it's a problem with which NIC is default on startup, right-click on the kinternet icon then select settings>various settings>startup (tab). From there you can select which NIC is default at startup. Once you have the default NIC setup for startup, if you want to change NIC's, just right click on the kinternet icon>interface and select the interface you want to use at that time, and switch back anytime for the other NIC. Bernd
On Mon, 2006-01-02 at 10:23 -0500, 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.
I use plugd and hot plugging to set up the networking. If I unplug the wired connection and then plug in the PCMCIA card my wireless becomes active with all the correct settings working. The same works in reverse automatically. There is a setting in YaST networking for setting this up. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Mon January 2 2006 12:16 pm, Ken Schneider wrote:
I use plugd and hot plugging to set up the networking. If I unplug the wired connection and then plug in the PCMCIA card my wireless becomes active with all the correct settings working. The same works in reverse automatically. There is a setting in YaST networking for setting this up.
both wired and wireless cards are internal. This is a DELL XPS M140 laptop. I saw that hot plug option, but I can't use it. -- Paul Cartwright Registered Linux user # 367800
On Mon, 2006-01-02 at 12:25 -0500, Paul Cartwright wrote:
On Mon January 2 2006 12:16 pm, Ken Schneider wrote:
I use plugd and hot plugging to set up the networking. If I unplug the wired connection and then plug in the PCMCIA card my wireless becomes active with all the correct settings working. The same works in reverse automatically. There is a setting in YaST networking for setting this up.
both wired and wireless cards are internal. This is a DELL XPS M140 laptop. I saw that hot plug option, but I can't use it.
Doesn't it have a button you can use to turn off the wireless? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Mon January 2 2006 12:27 pm, Ken Schneider wrote:
Doesn't it have a button you can use to turn off the wireless?
so the answer is, when I'm not using wireless to just right-click and disable it? -- Paul Cartwright Registered Linux user # 367800
On Mon, 2006-01-02 at 12:48 -0500, Paul Cartwright wrote:
On Mon January 2 2006 12:27 pm, Ken Schneider wrote:
Doesn't it have a button you can use to turn off the wireless?
so the answer is, when I'm not using wireless to just right-click and disable it?
Or, as is the case on some laptops, use the button on the front to turn off the wireless card. The other thing you can use is netgo. Available from: http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Mon January 2 2006 12:57 pm, Ken Schneider wrote:
so the answer is, when I'm not using wireless to just right-click and disable it?
Or, as is the case on some laptops, use the button on the front to turn off the wireless card.
the onlu buttons on the front of this thing are multimedia, this thing is designed for media.. quickstart so you can [play DVDs without waiting for an OS to boot. where the LAN card is, there is no button, but the right-click method might work.
The other thing you can use is netgo. Available from: http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netg o got it, and I'll look at it!
-- Paul Cartwright
On Mon, 2006-01-02 at 12:25 -0500, Paul Cartwright wrote:
On Mon January 2 2006 12:16 pm, Ken Schneider wrote:
I use plugd and hot plugging to set up the networking. If I unplug the wired connection and then plug in the PCMCIA card my wireless becomes active with all the correct settings working. The same works in reverse automatically. There is a setting in YaST networking for setting this up.
both wired and wireless cards are internal. This is a DELL XPS M140 laptop. I saw that hot plug option, but I can't use it.
I just came across this page: http://susewiki.org/index.php?title=WLAN_setup_with_ifplugd which might perhaps work for you, Paul. Cheers, Dave
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.
On Mon, 2006-01-02 at 10:10 +0000, 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'.
The keyword is not necessarily 'reboot', it may also be 'rcnetwork restart' which restarts the network and re-reads the new network configuration. Of course if the network settings are not correct in YaST no amount of reboots or rcnetwork restart commands will help. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (8)
-
bernd -
Bruce Marshall -
Dave Howorth -
Dave Howorth -
David McMillan -
James Knott -
Ken Schneider -
Paul Cartwright