WIreless won't surf internet unless wired card has IP even if not plugged in
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
WIreless won't surf internet unless wired card has IP even if not plugged in
Hello
I have a problem and have not been able to find any information on this yet.
I have Suse 9.2 on an IBM T-30 notebook. Everything was configure correctly except the sound card but that is for later. The problem I have is if I plug in the wired card into the lan and boot I can surf the net just fine as would be expected whether I use DHCP or static. Also on the same note I can surf the internet on wireless if I unplug the wired card and leave it configured static. If I remove the static and unset the IP address for the wired card then the wireless stops surfing the net. I can still browse the internal network though so my problem is the gateway because I cannot ping outside of the lan. Even if I put all the static info in the wireless card it still will not surf. As soon as I replace the IP in the wired card it is up and running again even with the wired card unplugged from the lan.
A static IP and gateway are not acceptable on this laptop as it travels allot and needs to be free to get on many diff networks and configurations.
Also no matter what kwifimanager shows good signal strength and IP address for the wifi card.
I also have an IBM T-40 that I loaded last night and it works no matter what I do to it. The only diff I can see between the 2 systems other than hardware is the T-40 set up the wireless as eth0 and the wired as eth1 the T-30 did not it set the wired up as eth0 and the wireless and wlan0.
Any help will be greatly appreciated until then I will keep looking.
Post the output of netstat -rn with the wired interface up and down. I'm betting that even though you have told it what default route to use, it's not using it.
I agree, the way SuSE uses its dhcp client is a real bitch. I bet that if you ps -aux | grep ifdhcp you notice that you'll have multiple instances of it, and since those daemons are running they constantly screw up the default route. I had the exact same problem as you. What I did was downloaded dhclient, which is part of the dhcp package at ISC, and told those startup daemon to go to hell.
Then you can just "sudo dhclient <interface>" whenever you need a IP
Thanks for the quick replies. I have been looking around and playing a bit and through the use of netstat -rn as suggested above I have figured out that Suse will only assign the route to the wired card if both are set to DHCP. If I set the wired card static or remove it then all is fine. It does not matter if the wired card is eth0 or eth1 as it is in my case. I have added these lines to both the ifcfg files with the respective configs applied
I agree, the way SuSE uses its dhcp client is a real bitch. I bet that if you ps -aux | grep ifdhcp you notice that you'll have multiple instances of it, and since those daemons are running they constantly screw up the default route. I had the exact same problem as you. What I did was downloaded dhclient, which is part of the dhcp package at ISC, and told those startup daemon to go to hell.
Then you can just "sudo dhclient <interface>" whenever you need a IP
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.