conected to router but no internet

[whych]

Like you say, it's all a bit confusing.
But looking at the router manual, it has a network blocklist that will only allow listed network cards external access, hence the suggestion to turn off the router firewall.

The only other thing we haven't tried is a traceroute to an ipaddress.
Perhaps traceroute to an ip on the internal net and one to an external ip will tell us where it gets dropped.

[hcvv]

Yes, forgot completley we have traceroute. Hello sd3782, do you know traceroute? Use it instead of ping and see what we get. I am realy curious.

[sd3782]

Thanks again for your replies.

The confusion is that I can ping the DNS successfully, but that is the only outside host I can ping. Or so I thought when I started writing this reply...

I've tried 'traceroute 130.57.4.15' and got the following result:

traceroute to 130.57.4.15 (130.57.4.15), 30 hops max, 40 byte packets using UDP
Unable to look up.........

OK, so I use the -n flag to avoid DNS lookup, which otherwise fails for everything. Now I get the following:

 1  192.168.1.1 (192.168.1.1)  0.835 ms   0.741 ms   0.683 ms
 2  10.231.40.1 (10.231.40.1)  6.869 ms   5.599 ms   8.286 ms
 3  81.100.0.109 (81.100.0.109)  8.062 ms   8.040 ms   7.873 ms
 4  212.43.162.57 (212.43.162.57)  8.645 ms   23.894 ms   19.572 ms
 5  195.50.91.69 (195.50.91.69)  7.181 ms   7.707 ms   7.437 ms
 6  4.69.139.97 (4.69.139.97)  7.533 ms   10.637 ms   12.396 ms
 7  4.69.137.70 (4.69.137.70)  80.894 ms 4.69.137.66 (4.69.137.66)  80.633 ms   80.409 ms
 8  4.69.134.70 (4.69.134.70)  81.016 ms 4.69.134.78 (4.69.134.78)  86.059 ms   92.152 ms
 9  4.68.16.5 (4.68.16.5)  86.453 ms 4.68.16.133 (4.68.16.133)  87.018 ms   81.850 ms
10  4.68.127.150 (4.68.127.150)  79.116 ms   76.715 ms   79.142 ms
11  12.122.131.138 (12.122.131.138)  167.708 ms   164.091 ms   163.232 ms
12  12.122.1.2 (12.122.1.2)  155.805 ms   156.015 ms   153.407 ms
13  12.122.2.53 (12.122.2.53)  155.868 ms   162.838 ms   158.638 ms
14  12.122.31.85 (12.122.31.85)  155.083 ms   155.106 ms   155.798 ms
15  12.122.30.25 (12.122.30.25)  156.679 ms   155.855 ms   155.416 ms
16  12.123.156.5 (12.123.156.5)  180.372 ms   181.498 ms   172.828 ms
17  12.127.106.34 (12.127.106.34)  162.825 ms   162.023 ms   162.886 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

I'm afraid it doesn't mean much to me. So I tried to ping some of the above. I can still ping the router on 192.168.1.1, but the following were interesting:

PING 10.231.40.1 (10.231.40.1) 56(84) bytes of data.
From 10.231.40.1: icmp_seq=3 Packet filtered
From 10.231.40.1 icmp_seq=3 Packet filtered

I got the above the first time I tried, but then every other time I get nothing back.

... and successfully pinged 81.100.0.109

... and successfully pinged 212.43.162.57

... and 195.50.91.69 ... and 4.69.139.97 (it would be easier to list of the above I can't ping.)

They are: 10.231.40.1 (see above), 12.122.131.138, 12.122.1.2, all the rest beginning 12, except for 12.123.156.5, which I can ping with success.

A bit confusing, but I hope that this may shed some light on the problem.

In other news, it's certainly not a problem with the router, because I have tried this in my office and at a friends house (where I have connected to the internet before) and was again able to ping the routers, but not connect to the internet.

Sam

[whych]

sd3782
If you try and open the router homepage at 192.168.1.1 with firefox with eth0 running, will it allow you to connect?
If it does, try resetting the router and its firewall to allow all connections (ie, turn the firewall off) and try again.
It looks like something in the router settings is blocking your access.

I would also turn off the router dhcp and set a manual ipaddress and network for eth0 and try again.
(This means you have a dumb router that will allow all traffic to connect to the outside.)
If you have another pc (ie the mac laptop) connected to the router as well, you should be able to see it from the linux box and vice versa as well. This would mean the internal net works fine.
You should also now be able to reach the outside world.
You can start tying down the access once it all works.

[sd3782]

Thanks to Henk and whych for your help, but I'm going to re-install Linux and go back to the start. It's annoying because it took me ages to set up sound and DVD, etc. But I should be able to do it quicker next time and I'll take plenty of back-ups.

I feel like I've tried everything, the internal network is fine, but it's not anything to do with the router, because it doesn't work on any of the other networks I've tried, at work, or friends' houses.

But it's good to know there is plenty of help out there when I need it next.

Thank you.

[buckmaster60]

Not sure if this is the same issue, but for me the /etc/resolv.conf file does not change or get updated when I connect to different networks. I have to manually run dhcpcd wlan0 to get resolv.conf to reflect my new location dns. I'm working figuring out why.