I’ve recently installed Open SUSE 11.0 on a pc. I’m connecting the PC to the internet through a router. However, I’m not getting any connection to the router from the PC.
Every time I try to ping the gateway: 192.168.2.1, it displays the message “Destination Host Unreachable”
I try running the Yast2 Network Settings wizard and it stops automatically without any message. But it doesn’t do anything to help me connect to the internet.
Please find the Overview of my system:
RTL8111/816B PCI Express Gigabit Ethernet controller
MAC:00:1d:92:ee:0a:af
Device Name: eth0
Started automatically at boot
IP address: 192.168.2.101, subnet mask 255.255.255.0
Hostname/DNS
NameServer1: 192.168.2.1
Routing:
Default Gateway: 192.168.2.1
Global Options:
-Traditional method with ifup
Hostname to send: AUTO
Change default route via DHCP
The funny thing is that it had worked for sometime after I had rebooted the machine several times. I got connected to the net and downloaded several software patches.
However, today when I booted it again and tried to activate some network services from Yast (HTTP, FTP), I found that they were closing automatically. On trying to connect to the internet, I realized it wasn’t working any more.
If you can’t login to the router, then the fault is with the eth card
Try running config via Yast - see if it comes back to life
I might also try rolling back the network driver packages to those on the DVD
You can force it via software management
go to versions tab in each package and select the radio button for the oos package
you need your dvd enabled in the repo
I’m sorry to say that I’m not very familiar with Linux. could you be a little more elaborate on where and how to make the changes that you suggested?
In the mean while there has been another problem. I got tired with connecting to the network. So I tried to repair the linux. Now after it finishes its scan, it finds errors in cups, ntp, hal etc. And if I do a repair on them, the system never boots up. It gives one of the Linux Kernel error messages. It’s badly messed up!
To be honest - I could describe how to repair it but it is virtually the same as a new install. Basically - you would choose update, but there will loads of dependancy conflicts because you will have installed packages and done updates since you first installed. If you want to try this route ask.
Otherwise, I would suggest;
choose New Installation.
it will find your existing install/partitions
just make sure the /home partition is marked *do not format
incidentally, do you have other OS’s on here or is it just Suse?
I think I will have to do a new install as you are suggesting.
No, the system just contains Linux. And one more thing, I don’t have a /home partition. Since I had wanted to set it up as a home server, I had created a /srv partition. So I am assuming that I should not format it right?
Could you tell me the reason why the system got stuck in repairing itself? Is it because of the new updates that I had installed? The system did not understand that they were updates and tried to repair them and thereby messed itself up?
Whatever it is, it is a hell lot of a trouble (especially because I had downloaded all the updates for over 4 hours).
Another point I want to mention is that I have an additional LAN card on the machine apart from the default one. Should I try to disable the default one and load the additional one? (I don’t know why I’m asking because finding a driver for the new card would be another headache)
>
> I’ve recently installed Open SUSE 11.0 on a pc. I’m connecting the PC to
> the internet through a router. However, I’m not getting any connection
> to the router from the PC.
> Every time I try to ping the gateway: 192.168.2.1, it displays the
> message “Destination Host Unreachable”
>
> I try running the Yast2 Network Settings wizard and it stops
> automatically without any message. But it doesn’t do anything to help
> me connect to the internet.
>
>
> Please find the Overview of my system:
>
> RTL8111/816B PCI Express Gigabit Ethernet controller
> MAC:00:1d:92:ee:0a:af
> Device Name: eth0
> Started automatically at boot
> IP address: 192.168.2.101, subnet mask 255.255.255.0
>
> Hostname/DNS
> NameServer1: 192.168.2.1
>
> Routing:
> Default Gateway: 192.168.2.1
>
> Global Options:
> -Traditional method with ifup
> Hostname to send: AUTO
> Change default route via DHCP
>
> The funny thing is that it had worked for sometime after I had rebooted
> the machine several times. I got connected to the net and downloaded
> several software patches.
>
> However, today when I booted it again and tried to activate some
> network services from Yast (HTTP, FTP), I found that they were closing
> automatically. On trying to connect to the internet, I realized it
> wasn’t working any more.
>
> Please help.
>
> Thanks,
>
> Soubhik
>
>
I seems like your default route is not set… but of course, from the above,
it is set.
Your setup looks perfect, dns/route/ip address… all specified and proper.
An observation though:
If you are HARD setting the values (static IP), why do you have “Change
default route via DHCP” enabled? This will delete your current route
settings… effectively clearing them… causing you to see “route not set”
type errors… coincidently, exactly what you are seeing.
It is strange…And this is not happening for the first time. I restarted the machine and logged in as ‘root’ and the connection to LAN is now working. It is being able to ping the router 192.168.2.1 and access external websites.
Any clue? I just want to understand how to get the connection working if it stops again tomorrow.
And for the records, I did not have to use the ‘route add…’ command.
Hello
I have the same problem with suse 11.0 and for that matter exactly the same problem with ubuntu 8.04.
It must be simply a bug in the new linux versions.
On two computers in my lan I have suse installed in dual boot with windows. The motherboards have the same nic: Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC.
One motherboard is the Asrock AliveNF5-eSATA2+ (64bits) the other the Asrock939SLI32-eSATA2 (32 bits).
Suse 10.3 works fine on both computers. No network problems with my speedtouch 780 modem. I have upgraded both to suse 11.0. 64 bits and 32 bits respectively. The AliveNF5 has network and internet connection, the 939SLI has not although the network connection manager has exactly the same configuration. Ubuntu 8.04 contrary to Kubuntu 7.10 has precisely the same problem on the 939SLI. Unfortunately I cannot install Ubuntu on the AliveNF5 for the reason I have sata disks installed on raid and jbod. The live-cd of (k)ubuntu won’t even start on this one.
What puzzles me is that despite the identical nic only one computer shows this problem. That would exclude the nic as the source of the problem.
I have tried all possible configurations with yast but nothing works.
It is also strange that one can access the manual configuration window of the network manager, but if you modify anything there the button confirming the changes fades and does not work any more. What is the use of such a tool?
In my opinion it is a bug in suse 11.0 and (k)ubuntu 8.04
This may help you, it worked for me using 10.3 with a Realtek 8111C on-board ethernet chip.
Suse loads a r8169 driver (which does not work)check as root in terminal
lspci | grep thernet
to check what driver is detected
lsmod | grep r*
to check what module is loaded
I found this link to a rpm source for the r6168 driver RepoView: bitshuffler’s Home Project (openSUSE_10.3_update)
I downloaded for my 64bit system and left clicked on this file and install with YAST.
As root, in a terminal type command
insmod lib/modules/2.6.22.18-0.2-default/updates/r8168.ko
to install the r8168 driver and to stop running r8169 driver, edit /etc/modprobe.d/blacklist
by adding
blacklist r8169