unable to route to internet, local network is fine

Hi All

I am having a bit of a problem. I did an update two days ago, and ever since I have lost my Internet connection. My local network is fine as I can remote into the other PC’s, and they have Internet access. In fact, I have SSH -X on to one of my headless boxes in order to launch Firefox to get to the forum.

I am fairly new to SuSE linux, but have been using *buntu for the last 6yrs or so… but am not sure what to look for as it’s almost as if port 80 is blocked… but the firewall is off.

Any thoughts or suggestions?

Thanks!

Not able to edit my post, so here is the info I wanted to add:

openSUSE 12.2 64bit
Gigabyte MB w/ on-board LAN
AMD X6 1090t
16GB DDR3

Linksys WRT160NL w/ DD-WRT
Cisco SG 100D-08

eth0      Link encap:Ethernet  HWaddr 1C:6F:65:D5:D2:56  
          inet addr:192.168.1.108  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52797892 errors:0 dropped:85648 overruns:0 frame:0
          TX packets:28941551 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:73703574784 (70289.2 Mb)  TX bytes:2399117269 (2287.9 Mb)

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:12134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1011376 (987.6 Kb)  TX bytes:1011376 (987.6 Kb)


On Mon 17 Dec 2012 03:16:01 AM CST, bluedalek wrote:

Not able to edit my post, so here is the info I wanted to add:

openSUSE 12.2 64bit
Gigabyte MB w/ on-board LAN
AMD X6 1090t
16GB DDR3

Linksys WRT160NL w/ DD-WRT
Cisco SG 100D-08

Code:

eth0 Link encap:Ethernet HWaddr 1C:6F:65:D5:D2:56
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52797892 errors:0 dropped:85648 overruns:0 frame:0
TX packets:28941551 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:73703574784 (70289.2 Mb) TX bytes:2399117269 (2287.9 Mb)

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:12134 errors:0 dropped:0 overruns:0 frame:0
TX packets:12134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1011376 (987.6 Kb) TX bytes:1011376 (987.6 Kb)


Hi
If your not using dhcp, you need to set the gateway and dns addresses
via YaST.

What do you see from the route command?


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 23:38, 3 users, load average: 0.15, 0.19, 0.22
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

On 12/16/2012 9:16 PM, bluedalek wrote:
>
> Not able to edit my post, so here is the info I wanted to add:
>
>
> openSUSE 12.2 64bit
> Gigabyte MB w/ on-board LAN
> AMD X6 1090t
> 16GB DDR3
>
> Linksys WRT160NL w/ DD-WRT
> Cisco SG 100D-08
>
>
> Code:
> --------------------
> eth0 Link encap:Ethernet HWaddr 1C:6F:65:D5:D2:56
> inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:52797892 errors:0 dropped:85648 overruns:0 frame:0
> TX packets:28941551 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:73703574784 (70289.2 Mb) TX bytes:2399117269 (2287.9 Mb)
>
> 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:12134 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12134 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1011376 (987.6 Kb) TX bytes:1011376 (987.6 Kb)
>
>
> --------------------
>
>
What is the result of:


/sbin/route -n
cat /etc/resolv.conf

Can you ping google.com by IP?


ping -c3 74.125.255.65


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Hi guys, thanks for the replies… here is the info you’ve asked for:

What is the result of:


/sbin/route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0


cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!

Can you ping google.com by IP?


ping -c3 74.125.255.65

PING 74.125.255.65 (74.125.255.65) 56(84) bytes of data.

--- 74.125.255.65 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

I am unable to post attachments,but this is how I have YaST setup:

  • Network Card Setup
    – General
    Activate device : on NFSroot
    Firewall Zone : Firewall Disabled
    Device Control : not selected
    MTU : not set

– Address
Device Type: Ethernet
Configuration Name: eth0
Statically Assigned IP : 192.168.1.108
Subnet Mask : /24
Hostname : linux-2nvc.site

– Hardware
Device Name: eth0
Seconds : 5
Kernel Module : r8169

Thanks again!

You do not have any nameservers defined. In Yast under ‘Hostname’ or
something add the following for the first, second, and third nameservers:

192.168.1.1
8.8.8.8
8.8.4.4

Save and give it a try.

Good luck.

There is something more than mere nameservers.
The Ping test to an IP address returned 100% loss, which means that a problem exists which must be resolved before considering name resolution… unless of course outbound ICMP is blocked.

Since your default gateways appears to be set and <assuming it’s correct> then I think you need to take a look at your DG/Firewalling device. Perhaps it’s setup to filter for clients, eg by MAC address if this is a home router.

If DG is a corporate/enterprise, then you may need to consider whether network authentication is required (and much more).

HTH,
TSU

On 12/17/2012 5:16 PM, tsu2 wrote:
>
> ab;2511391 Wrote:
<snip>
>> Good luck.
>
> There is something more than mere nameservers.
> The Ping test to an IP address returned 100% loss, which means that a
> problem exists which must be resolved before considering name
> resolution… unless of course outbound ICMP is blocked.
>
> Since your default gateways appears to be set and <assuming it’s
> correct> then I think you need to take a look at your DG/Firewalling
> device. Perhaps it’s setup to filter for clients, eg by MAC address if
> this is a home router.
>
> If DG is a corporate/enterprise, then you may need to consider whether
> network authentication is required (and much more).
>
> HTH,
> TSU
>
>
tsu2;

After the OP responded, I double checked that the IP was correct(could be a
senior moment on my part). Ping also failed here after the OP responded, and
the IP was no longer listed by nslookup. That IP was working again this morning
and was again listed by nslookup. Google must have rotated that server out
between my post and the time the OP could try the IP.

Anyway, I don’t think “forums.opensuse.org” changes their IP; so you should try:


ping -c3 130.57.66.6


P.V.
“We’re all in this together, I’m pulling for you” Red Green

>> There is something more than mere nameservers.
>> The Ping test to an IP address returned 100% loss, which means that a
>> problem exists which must be resolved before considering name
>> resolution… unless of course outbound ICMP is blocked.

Yes, I considered all of that, but discarded it because…

> After the OP responded, I double checked that the IP was correct(could be
> a senior moment on my part). Ping also failed here after the OP
> responded, and the IP was no longer listed by nslookup. That IP was
> working again this morning and was again listed by nslookup. Google must
> have rotated that server out between my post and the time the OP could try
> the IP.

This happens a lot, especially with sites as big as Google. For what it’s
worth, pinging Google’s own DNS severs is very reliable (unless, as tsu2
mentioned, ICMP is blocked) and also gives you as couple of
easy-to-remember IPs for testing wherever you are: 8.8.8.8 or 8.8.4.4

> Anyway, I don’t think “forums.opensuse.org” changes their IP; so you
> should try:
>


> ping -c3 130.57.66.6
> 

True… historically it hasn’t changed often, but there are more-reliable
servers to use, like those which are not primarily accessed by a domain
name (DNS servers, for example; yet another reason I use Google’s DNS
servers).

Good luck.