Ken Schneider wrote:
On Wed, 2005-11-30 at 19:08 +0800, John Summerfield wrote:
This is on a laptop. How wireless interfaces work on non-portable computers is, I think, a different matter altogether.
I installed SUSE 10 while disconnected from my LAN and all was well. Wireless cam up on boot, I got IP address etc, updated resolve.conf and set routes and life was good as far as those things go.
I then reinstalled, while attached to LAN by wire and air, and now I can get an IP address, but the other things don't happen.
I've used find and grep and vim till I'm blue in the face and I don't see what to change. Yast doesn't give me any options that I can find, and I can't find any likely references to resolv.conf or the various interfaces I've used.
Please tell me, what do I change?
The most desired behaviour is this: If wire is plugged in, it's configured with IP address etc, routes are set up and resolv.conf is reconfigured.
Install ifplugd package and adjust settings for card using YaST.
I get 3 Mbytes over the air, so wire's not a great concern. However, if it's there I expect it to be used.
If wireless is plugged in, it's configured with IP address etc, local routes are set up. If wire is not plugged in, then all routes are set up and resolv.conf is reconfigured.
If two (or more) wireless devices work, the fastest is configured with default routes and resolv.conf is reconfigured, if there is no wire.
Don't. Use one or the other or you are just asking for problems.
I have builtin wireless, I may want a pc card as well to detect other networks. Think wardriving, detecting rogue access points, testing stuff. Note, one can have two wires to the LAN and use bonding to make one faster link. Some might like to try it with wireless too.
Just for the moment, I will settle for wireless working as my primary interface (as it is).
This is the most important for the moment: at present wireless networking is plain broken.