What is wrong with the network settings in opensuse 11?

English Network/Internet
#1

Hi,

I recently started installing and setting up my opensuse 11 system. Up to now I was very please with the system but as usual and with each release in the end when I thought that my system is spick & span I discover the most stupid and hilarious bug ever that makes me loose hours and hours of time and finally makes me decide to boot back to windows because with all the hassle you have there, at least you have a decent working system. And again, with opensuse 11 I’m running into the same story as usual.

Here is what happens :

I have two network cards in my laptop, a gigabit lan network card eth0 and a wifi card. I started yast to configure the eth0 card with static IP. I filled in all the necessary IP’s (I’ve done this tons of times with previous suse version with no issue at all), saved the settings and then it comes. If I have software repositories defined in yast it will throw out an error message while saving the network settings that it is not able to connect to download.opensuse.org. Whatever it is going to search for there ?? The network is configured to use the network manager which allows me to use the wifi card when needed in an easy way (at least it was in opensuse 10.3).

I ran ifconfig and got this output :

eth0 Link encap:Ethernet HWaddr 00:15:C5:4A:69:2A
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2581 errors:0 dropped:0 overruns:0 frame:0
TX packets:2238 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2597996 (2.4 Mb) TX bytes:326332 (318.6 Kb)
Interrupt:18

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:152 errors:0 dropped:0 overruns:0 frame:0
TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11740 (11.4 Kb) TX bytes:11740 (11.4 Kb)

wlan0 Link encap:Ethernet HWaddr 00:18:DE:22:B9:AE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-22-B9-AE-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 seems to be correct but no, I cannot connect to the internet or ping hostnames of websites. I can only ping IP addresses. Strange. Looks like a DNS issue although the nameserver settings where correctly set up in yast.
Edited /etc/resolv.conf and added the smae settings as I had in opensuse 10.3. Now it resolves the ip address when I ping the hostname but got a 100% packet loss and the message that the destination host is not reachable. Restarted the network manager and checked /etc/resolv.conf. Surprise, the file was empty again, thanks to the network manager.

Second operation, reconfigure the **** thing in yast with network manager on and DHCP config. Nothing else.
Saved the stuff, restarted the network manager and checked ifconfig.
Got the exact same ifconfig output as at was with the fixed IP while I needed to get 192.168.1.102 as IP.

OK, reboot the system and checked again. Still the same fixed IP output. Third solution, leave network manager on and set both cards to “Not configured”. Saved and rebooted the pc.

Cool, now it configures the network with dhcp while it is not supposed to be configured. I got IP 192.168.1.102 while I need 192.168.1.3 because it is a server !!!

Back to the beginning. Restarted yast and disabled the network manager and used the traditional ifup. Configured both with dhcp and fixed ip config but exactly the same issue, no resolve and no internet.

All this was done in the console TTY1. That I got the brilliant idea to start KDE and check the knetworkmanager applet. Although there was a config set up in yast there was nothing of all this to find in Knetworkmanager. Quickly added a new eth0 config with fixed IP and activated it. Sweeeeeet… internet is working.

But as soon as I reboot, whatever setup choosen in yast, I have no internet connection. I always have to log in to kde, check the knetwork manager (and most of the time start it manually because it is not loading) and manually start the connection.

There was a crash issue with knetwork manager so I did an online update and updated the recommended and security patches.
I think this even made it worse.

I hope someone has to answer to solve this or do I have to kill someone to get a network connection ?

This is the very basic part of a modern operating system and this is not even working in a brand new release of opensuse, beats me. I lost almost two hurs today only to get a correct and simple basic network connection which takes me 10 seconds in windows to set it up. I must be dreaming, this is a nightmare.

Sorry if I sound a bit short but I’m not used to spend 2 hours on a simple stupid basic thing I’ve configured for years. This makes me so mad !

#2

Sorry for your frustration. Actually there have been quite a bit of
issues with Network Manager under version 11 as a perusal of this forum
would indicate. DNS not being/staying populated when static IP’s are
assigned is one of them. It is my recommendation that you switch your
system to use ifup although I do not know the ramifications that will have
on your WiFi as I don’t use WiFi thus I would not be aware of any
inconveniences you might encounter.

The alternative is to continue using Network Manager yet work around its
limitations (such as losing your DNS settings after every reboot or having
no active interface). What you need to do is force an entry
into /etc/resolv.conf as this is the file that
has issues when using Network Manager and static IP’s.

The entry would look
something like this:

nameserver xxx.xxx.xxx.xxx
search xxxxxx.net

where xxx’s are IP ranges or your search domain name.

Once you have done that, the recalcitrant DNS problems should go away, but
beware they will likely return over and over. You could come up with a
script to run when you log in as a workaround I suppose.

Again I am speaking from my own work on this issue, I switched to ifup.

#3

OK, done that, running on ifup and this works for the moment but it makes me loose the ease of use of KNetworkmanager for my wifi.

Working now but still a very unhappy and dissapointed customer customer !!
After a fix with online update and more than a month after the release it is still not fixed.

#4

I am new in open suse 11 i have one computer with DSL connection , i m not able to connect with the internet … some one please help me please send me the set by step instructions
to— reachujjual@gmail.com

#5

You didn’t pay for it so you’re not a customer.

Since you’re not a contributor either - you don’t really any place to whine about it. Take what you’re given or be quiet.

#6

Best you start your own topic instead of tacking it on the end of someone else’s. It will also get you the answers you require,as it stands,people will think you have the same problem as the original poster & you will subsequently get answers which may not be beneficial to your situation

Andy

#7

On Sun, 17 Aug 2008 10:26:02 GMT
Chrysantine <Chrysantine@no-mx.forums.opensuse.org> wrote:

>
> LRE;1850006 Wrote:
> > Working now but still a very unhappy and dissapointed customer customer
> > !!.
> You didn’t pay for it so you’re not a customer.
>
> Since you’re not a contributor either - you don’t really any place to
> whine about it. Take what you’re given or be quiet.

Wow, pretty harsh. I can imagine that attitude scares many a person away.

Loni

–
L R Nix
lornix@lornix.com