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.

(Remove *public* IPs as necessary)

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

Hello

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

GATEWAYDEV='eth1'
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
DHCLIENT_PRIMARY_DEVICE='yes'

It is still the same way. It does not like the Wifi card as the leader so to speak unless the wired card is removed from the config all together.

I will keep looking for a solution to this and will look into the suggestions above more.

I need a setup that the user does not have to intervene to use as the T-30 is for the production department and not computer savvy.


Thanks again though.

This worked for me! thanks.