Strange network/DNS problem

English Network/Internet
1

I’m having a strange problem with my network connection/DNS. I turn computer the on and it recognizes and connects to wireless or wired but I can’t access any Internet resources or my router. If I ping the default gateway, I get no response and I get DNS errors from any network services that run at start up.
If I stop and start the network daemon then it all works fine until the next time I turn on my laptop. It does this for both wireless and wired connection.
I’ve tried to edit the network interface information in YaST but it says that configuration is handled by knetworkmanager and I have no idea where that information is accessed.
I should point out that it all worked fine until I tried to connect to open WAP at my school and couldn’t so I connected to the wired network. Next morning I had this problem when connecting to my home network.

My questions are 1. What could be the cause of this error and 2. where does one configure the network interfaces when using knetworkmanager?

Thanks
mike

2

What version of openSUSE? Gnome or KDE?

Do either of the two commands listed below show any difference in output between
when it works and when it does not?


/sbin/route -n
cat /etc/resolv.conf
3

I’m using openSuSE 11.3 with KDE4

Here are the results of the two commands. Note that for some reason SuSE named my wireless adapter eth1.

First route -n when I get DNS results

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 eth1

then when I can’t

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 vmnet8
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 eth1
192.168.43.0    0.0.0.0         255.255.255.0   U     0      0        0 vmnet1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 eth1

I’ve been wondering if the vm interfaces are responsible but I don’t know where to go to remove them. In other distros, I could edit /etc/network/interfaces and get rid of them.

Here is resolv.conf, it’s the same for good and bad respectively.

# Generated by dhcpcd for interface eth1
search gateway.2wire.net
nameserver 192.168.1.254

# Generated by dhcpcd for interface eth1
search gateway.2wire.net
nameserver 192.168.1.254

thanks
mike

4

Had the problem again with a different WAP. However restarting the network daemon didn’t fix the problem. I noticed that the resolv.conf file only contained the settings for my home nameserver and that there was an additional file called resolv.conf.netconfig which contained the information for the router to which I was connecting. I copied that info to resolv.conf, restarted the network daemon and it worked fine.
So it seems to me that there is perhaps an issue between resolv.conf and the network daemon. If anyone has any further advice or suggestions on where to look to fix this, I would appreciate it.

5

Turns out that vmware was indeed the culprit. I removed vmware from the RC5.d folder and rebooted and it all worked fine. I guess it was routing everything to the virtual machine and when I restarted the network daemon it would overwrite the route tables and remove the vmnet entries.:
So now I’ve gone ahead and uninstalled vmware-player (I prefer VirtualBox anyway) and it works.

6

I had the same problem and fixed it by removing
/etc/resolv.conf
and then running dns resolver that created a new resolv.conf file.