Not able to ping anything

Hi friends,

I am Suse 10.3 user. I successfully gets connected to a network but I can’t ping anything other then the 192.168.1.1
I am not sure whats wrong as I face this problem with some networks while with others it works just fine. I wonder even after getting connected successfully I am not able to ping anything.

Can anyone provide some pointers or solution to this problem.
I can see my inet addr in ifconfig output.

Please help !!!

So i guess your IP ist 192.168.1.1.
At first you should post the ping command you use.
In other words we got to bring the problem from a wide range of possible alternatives hopefully to a single one.

Ok, so you can’t ping anything but can you get web pages in a web browser? Sometimes network admins will deny ping traffic. At the college I went to, the only pings that I could get replies on were when I pinged hosts that were inside the school’s network, but I could still get web pages.

Well my problem is that I can’t browse internet even after i get sucessfully connected. I wanted to say I can’t even ping. Its a private network so I can change anything I want in it. I am not restricted by any means. I guess its just some little tweek that I am missing.:frowning:

Also it happens with some networks only not all of them. I can easily browse as i am doing now in the same OS but a different network.

Any ideas why would that happen.

On Wed, 13 Aug 2008 21:46:02 GMT
Shadow Fax <Shadow_Fax@no-mx.forums.opensuse.org> wrote:

>
> Well my problem is that I can’t browse internet even after i get
> sucessfully connected. I wanted to say I can’t even ping. Its a private
> network so I can change anything I want in it. I am not restricted by
> any means. I guess its just some little tweek that I am missing.:frowning:
>
> Also it happens with some networks only not all of them. I can easily
> browse as i am doing now in the same OS but a different network.
>
> Any ideas why would that happen.
>
>

Are you trying to ping over the internet? or just within your own private
network?

Pinging over the 'net will be on-again/off-again depending on who you ping.
I have my router/firewall set up to drop ping packets, as many admins do.
You can get my webpage, email server, ssh server etc… but no pings.

ping yahoo.com

works… does that work on yours?

Pinging in your own private network often depends on firewall settings too…
can’t say how the windows firewall (cough) handles it… but I can
configure the linux firewall to drop pings too. So again, it depends.

Ping is usually touted as a diagnostic tool… you use it when something
doesn’t work. But you’ve stated that browsing and surfing work fine…
uh… so where’s the problem?

Loni

(Actually, I want the “Machine that goes PING!” for some testing…)


L R Nix
lornix@lornix.com

On Thu, 14 Aug 2008 00:27:15 GMT
L R Nix <lornix@lornix.com> wrote:

> On Wed, 13 Aug 2008 21:46:02 GMT
> Shadow Fax <Shadow_Fax@no-mx.forums.opensuse.org> wrote:
>
> >
> > Well my problem is that I can’t browse internet even after i get
> > sucessfully connected. I wanted to say I can’t even ping. Its a private
> > network so I can change anything I want in it. I am not restricted by
> > any means. I guess its just some little tweek that I am missing.:frowning:
> >
> > Also it happens with some networks only not all of them. I can easily
> > browse as i am doing now in the same OS but a different network.
> >
> > Any ideas why would that happen.
> >
> >
>
> Are you trying to ping over the internet? or just within your own private
> network?
>
> Pinging over the 'net will be on-again/off-again depending on who you ping.
> I have my router/firewall set up to drop ping packets, as many admins do.
> You can get my webpage, email server, ssh server etc… but no pings.
>
> ping yahoo.com
>
> works… does that work on yours?
>
> Pinging in your own private network often depends on firewall settings
> too… can’t say how the windows firewall (cough) handles it… but I can
> configure the linux firewall to drop pings too. So again, it depends.
>
> Ping is usually touted as a diagnostic tool… you use it when something
> doesn’t work. But you’ve stated that browsing and surfing work fine…
> uh… so where’s the problem?
>
> Loni
>
> (Actually, I want the “Machine that goes PING!” for some testing…)
>

Duh! Had a blonde attack!

If you can ping some things, but cannot surf… check your dhcp settings,
and check your default route.

if you type (as root):

route -n

You should get output resembling the following:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.13.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.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.13.254 0.0.0.0 UG 0 0 0 eth0

The last line (0.0.0.0) is the default gateway.

Assuming yours is 192.168.1.1, you can add it manually by:

route add default gw 192.168.1.1

which should help.

Settings for default gateway are in Yast->Network Settings->Routing(tab), but
if you’re using a dynamic IP (DHCP), it should be already set. Generally
only need this if you’re using static IP’s.

Which brings up another issue: DNS resolvers… Do you have proper DNS
entries set up in /etc/resolv.conf?

if you:

cat /etc/resolv.conf

You should get something like:

nameserver 192.168.1.1

There may be other lines, comments and other directives, but the ‘nameserver’
line is important. Generally, for most people, it’s their router/firewall,
which if 192.168.1.1 is yours… would be appropriate as shown.

That may be changed using the Yast->Network Settings->Hostname/DNS (tab)

Again, shouldn’t need to deal with this if you’re using DHCP, but for static
IP you would.

Loni


L R Nix
lornix@lornix.com