for a long time now i used Windows XP. this is the first time i work with suse/linux or something equal.
i installed openSUSE from the dvd (v 10.3). everything works fine…nearly everything. i’m not able to connect to my local network. (DSL Router: FRITZ!Box Fon WLAN 7050, +3 other Computers running WinXP)
I tried everything, but no matter what i did, everytime i tried to ping my router or a computer in the network i got this:
prophet:~ # ping 192.168.178.1
connect: Network is unreachable
all settings are exactly as i used them with winXP.
(i set them in YaST2)
My System:
Mainboard: Gigabyte P35-DS4(onboard: Giga-byte RTL8111/8168B PCI Express Gigabit Ethernet controller)
CPU: Intel Core²Duo (don’t know which number)
RAM: 4GB DDR2 800(G-Skill)
Graphics: ASUS EAX1950Pro
250GB-HDD + DVD-Writer
i hope u can help me.
Sebastian
(i’m sorry for my bad english, i hope u have no problems to understand)
That card has some issues reported with earlier kernels on 64 bit Suse.
So let’s just check that’s OK, and a couple of otherthings while we’re at it. Please issue these commands in a console/terminal window and copy/paste the results back here:
I’m facing the same problem when i configure my card through Yast network module.
Try to install Knetwormanager (i assume you use Kde) and configure your network with this.
For me it’s the only way to have my network cards working.
eem i had the same problem some times… if you want to install knetwork manager , remember to do it with yast before trying to configure your network card…
Those commands show that the ethernet card is recognised. It is getting an IP address 192.168.178.26 and it knows where that gateway to the internet is in the device at address 192.168.178.1.
Ordinarily it would be working and connecting to the internet. The puzzle is why you can’t ping 192.168.178.1 when you’re on the same IP subnet. Maybe there’s a setting in the router preventing that or maybe the firewall has a strange setting. Try turning the firewall off in Yast → Security → Firewall until you get connected, just to limit the possible problems.
Also check that the ethernet card is assigned to the external zone in the firewall at Yast → network devices → network settings → edit → general → firewall zone → external zone.
And just for completeness, what do you get from this command in a console: cat /etc/resolv.conf
Oh and are you using a router to get to the internet or which device are you using?
the network card don’t get the ip address from my router, i set it manually. i set the gateway too.
i connect to the internet with a router (name is in my first post). now i disabled the firewall, and set the firewall zone to external (was disabled)…maybe because i disabled the firewall one minute before? now it runs again. (but while it was disabled, i wasn’t able to ping my router or any other computer too.)
prophet:~ # cat /etc/resolv.conf
nameserver 192.168.178.1
search local
now i’ll try again to get my ip over dhcp. i’ll write if it works (don’t believe so)
That’s very nice to hear. For other readers with this problem: First check the network setup in terms of:
For DHCP →
ping: If you can ping your router successfully
route: If “route” displays the IP address of the router in the last line
ifconfig: If the card is getting an IP address on the same subnet as the router
resolv.conf: If cat /etc/resolv.conf shows name servers or the IP of the router
Check those first and get them right before you think about drivers
Then use this to get your cards’ descriptions at more fundamental level:
sudo /sbin/lspci | grep thernet
And then use that information to see if the card is problematic and in need of a driver install, which is a fairly rare requirement because Linux is way far ahead of microsoft in supplying the full suite of drivers.
Let me share with you what has happened to me regarding this problem:
I usually copy the suse installation from another stable server instead of installing everything from scratch.
The old server had a maxwell ethernet chipset. After booting the cloned root partition and change the eth driver to realtek, the system worked FINE for hours.
After the first reboot… GONE. Nothing would make the realtek board work again (I even thought that the board had gone burst). So I got the cloned image back and it worked until the first boot.
Intriging, isn’t it? I got the driver from realtek web site and everything is fine now.
Today, when I try to connect Internet I cann`t do it =( It was very suddenly, because yesterday all work well and I do nothing with system.
When I look that Internet fall off I go to console and try to ping some adress and my ADSL router.
As u already suspect I gave this message:
connect: Network is unreachable
I read post higher, but it wasn`t of use…
This is my config
suse-home:/home/andrew # ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:85:B2:E7:2E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65 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:3912 (3.8 Kb) TX bytes:0 (0.0 b)
Interrupt:21
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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:200 (200.0 b) TX bytes:200 (200.0 b)