Unable to ping modem or router in Suse 10 using static IP

[nileshkumar]

Recently i have installed Suse Linux Enterprise Desktop 10 sp1 10.1-0, but after installing Suse (Sled 10) i am now not able to ping my modem (IP add. 192.168.1.1), i have given static ip as 192.168.1.3, but it is pining 192.168.1.3 (i.e. self).
Also i have tried ping by removing firewall, but that is also not working, then i have given the "Nameserver as 192.168.1.1" (ip of modem), but even then it is not working. then tried to modify /etc/resolve.conf by manually putting the value as " nameserver 192.168.1.1" but even that is not working.
I am having an ADSL2 Modem for broadband connection which is working absolutely fne in Windows XP, but not in Sled 10.

[whych]

Did you set up the adsl connection when you installed sles? (ie did sles find the modem on install)
If not, you probably need to set it up/install it first.
If it has, you need to set up your login info for your isp.
It probably won't have an internal ip address. If it's not connected it wont have an ip address.
Nameservers, etc should be automatic after setup and not require anything extra.

[D-cat]

As root, type ifconfig to see if the ethernet interface is configured the way you want and is up.

[nileshkumar]

well thank u sir,
Now i am able to ping to modem, i can't say what exactly went into the way, but now i am posting this reply from suse, so thank to you and to this forum for giving me reply.

[nileshkumar]

Hello friends,
I am here again with the same problem, today after 2 days when restarted the Suse Linux Enterprise desktop 10 SP1 10.1-0 (Sled 10), again i am not able to ping the modem, and the o/p of the above command is as given below

Slinux-9uh7:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:18:A7:5C:4F
inet addr:192.168.1.3 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::230:18ff:fea7:5c4f/64 Scope:Link
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)
Interrupt:209 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9424 (9.2 Kb) TX bytes:9424 (9.2 Kb)

Slinux-9uh7:~ # route -n
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 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

also i think that their must be some service or configuration that is changing every time i am booting up and thus making me unable to ping to modem.

[D-cat]

Okay, I'm stumpped. That looks like it should work.

Have you tried ifup eth0 just for s**** & giggles?

[nileshkumar]

well i have tried that also but that is also not working.

[D-cat]

Seeing as absolutely no packets have traversed eth0, I'm wondering if this is a physical issue, like a bad cable or the net card is not seated straight.

It might also be the net card module has an issue with static setups... does your router support dhcp static serving (as in a dhcp server that can be configured to always issue the same IP to a certain MAC address)? You might have better luck configuring the box via dhcp and setting the router to always issue the server the same IP?

[nileshkumar]

Off course i have not tried the DHCP option as i want to configure the LAN myself.
But this is definetly not an Physical issue as once i was able to ping to modem, but after restarting again i was unable to ping. then other thing is that every thing is working fine in windows.

[gogalthorp]

Try a complete shutdown ie power off then boot only to Linux. There was a problem with some cards that windows on exiting was putting them into a state where Linux could not restart them on a warm boot.