Wired Internet connection [Solved]

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

Wired Internet connection [Solved]

Postby orange_angel » Tue Apr 19, 2011 12:15

Hi everyone, I have a problem that I can't find the solution to. So I'm hoping someone can help me.

I recently got a new computer and installed Sabayon on it (just as I had on my last one). At the beginning wireless didn't work, but I used a cabel instead and get some updates from the Internet and wireless started working.

Now I'm at another place with no access to a wireless connection, so I plugged in a cable instead, but that gives me no useful Internet connection. The connection works just fine when I'm in Windows on the same computer.

The NetworkManager tells me I'm connected with Internet access, but when I try to view a web page, nothing happens and after a while the browser tells me: Error 7 (net::ERR_TIMED_OUT): The operation timed out.

Here's a bit more info:

Code: Select all
# ifconfig
eth0      Link encap:Ethernet  HWaddr 14:fe:b5:a2:47:b4 
          inet addr:83.209.90.34  Bcast:83.209.95.255  Mask:255.255.248.0
          inet6 addr: fe80::16fe:b5ff:fea2:47b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2961 (2.8 KiB)  TX bytes:74266 (72.5 KiB)
          Interrupt:52 Base address:0x4000

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:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1080 (1.0 KiB)  TX bytes:1080 (1.0 KiB)

# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=34.8 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=34.9 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=35.0 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=51 time=35.1 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=51 time=35.0 ms
64 bytes from 8.8.8.8: icmp_req=6 ttl=51 time=34.8 ms
64 bytes from 8.8.8.8: icmp_req=7 ttl=51 time=34.9 ms
64 bytes from 8.8.8.8: icmp_req=8 ttl=51 time=35.0 ms

--- 8.8.8.8 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7001ms
rtt min/avg/max/mdev = 34.802/34.977/35.123/0.230 ms


# ping 209.85.135.147
PING 209.85.135.147 (209.85.135.147) 56(84) bytes of data.

--- 209.85.135.147 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5000ms

ping 209.85.135.147
PING 209.85.135.147 (209.85.135.147) 56(84) bytes of data.

--- 209.85.135.147 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5000ms

# lspci
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 (rev 34)

# dmesg | grep eth0
[    9.126033] r8169 0000:06:00.0: eth0: RTL8168b/8111b at 0xffffc900057e4000, 14:fe:b5:a2:47:b4, XID 0c200000 IRQ 52
[   20.095450] r8169 0000:06:00.0: eth0: link down
[   20.095456] r8169 0000:06:00.0: eth0: link down
[   21.988859] r8169 0000:06:00.0: eth0: link up
[   33.418771] eth0: no IPv6 routers present
[  116.447546] r8169 0000:06:00.0: eth0: link down
[  116.447555] r8169 0000:06:00.0: eth0: link down
[  116.448122] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  118.131723] r8169 0000:06:00.0: eth0: link up
[  118.132333] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  128.738000] eth0: no IPv6 routers present


The ip-address and other things are the same as in Windows. It's not a static ip and the cable is plugged directly into the wall. This is what Windows tells me (the labels are in Swedish):

Code: Select all
ipconfig

IP-konfiguration för Windows

Ethernet-anslutning Anslutning till lokalt nätverk:

   Anslutningsspecifika DNS-suffix . : blixtvik.net
   Länklokal IPv6-adress . . . . . . : fe80::bca2:4cae:c719:b39a%16
   IPv4-adress . . . . . . . . . . . : 83.209.90.34
   Nätmask . . . . . . . . . . . . . : 255.255.248.0
   Standard-gateway. . . . . . . . . : 83.209.88.1

Tunnelanslutning: 6TO4 Adapter:

   Anslutningsspecifika DNS-suffix . : blixtvik.net
   IPv6-adress . . . . . . . . . . . : 2002:53d1:5a22::53d1:5a22
   Standard-gateway. . . . . . . . . : 2002:c058:6301::c058:6301

Tunnelanslutning: Teredo Tunneling Pseudo-Interface:

   Anslutningsspecifika DNS-suffix . :
   IPv6-adress . . . . . . . . . . . : 2001:0:5ef5:73b8:c7e:1a8d:ac2e:a5dd
   Länklokal IPv6-adress . . . . . . : fe80::c7e:1a8d:ac2e:a5dd%17
   Standard-gateway. . . . . . . . . :


Since I could ping 8.8.8.8 I tried setting the DNS-adress to that, but that made no difference. The other thing I've tried is to disable IPv6, which removed the message "eth0: no IPv6 routers present", but didn't do much else.

Any other ideas?
orange_angel
Young Hen
 
Posts: 22
Joined: Tue Jun 29, 2010 16:37

Re: Wired Internet connection

Postby onyx » Tue Apr 19, 2011 12:41

Firstly: is this new place running a firewall or something? If so, it could be doing a packet inspection, and dropping packets from linux browsers.

Secondly: it appears from your post that you haven't checked DNS resolving, just pinged a known DNS server. So what do you get if you ping sabayon.org? ( I get 149.132.176.64)
Add the router's address to your /etc/resolv.conf. Some routers play up unless they are first in line for DNS calls.

Thirdly: given Windows works, do this: Start- Run. type cmd, press Enter. (DOS window - windows terminal)
type: ipconfig /all > ipconf.txt
type: type c:\windows\system32\drivers\etc\hosts >> ipconf.txt

then put that ipconf.txt (which is in your user's directory) up here for us to read. And do the similar thing for your Sabayon installation;

cat /etc/resolv.conf >linif.txt
cat /etc/hosts >>linif.txt

Fourthly: load traceroute if you can, and use that to help diagnose the issue. (In Windows it's called tracert, and is usually already there.)
onyx
Baby Hen
 
Posts: 13
Joined: Thu Jan 13, 2011 10:54
Location: NZ

Re: Wired Internet connection

Postby orange_angel » Wed Apr 20, 2011 8:46

onyx wrote:Firstly: is this new place running a firewall or something? If so, it could be doing a packet inspection, and dropping packets from linux browsers.


We don't have a router here, the cable goes directly to the wall. I've had no problem using LInux here before, and to my knowledge nothing is changed except the new computer.

onyx wrote:Secondly: it appears from your post that you haven't checked DNS resolving, just pinged a known DNS server. So what do you get if you ping sabayon.org? ( I get 149.132.176.64)
Add the router's address to your /etc/resolv.conf. Some routers play up unless they are first in line for DNS calls.


It looks like DNS resolving works, cause I get 149.132.176.64 back too. But there's no router here so I can't add it's address to /etc/resolv.conf

Code: Select all
$ ping sabayon.org
PING sabayon.org (149.132.176.64) 56(84) bytes of data.


onyx wrote:Thirdly: given Windows works, do this: Start- Run. type cmd, press Enter. (DOS window - windows terminal)
type: ipconfig /all > ipconf.txt
type: type c:\windows\system32\drivers\etc\hosts >> ipconf.txt

then put that ipconf.txt (which is in your user's directory) up here for us to read. And do the similar thing for your Sabayon installation;

cat /etc/resolv.conf >linif.txt
cat /etc/hosts >>linif.txt


The output from Windows (sorry it's in Swedish):
Code: Select all
IP-konfiguration för Windows

   Värddatornamn . . . . . . . . . . : FridasDator
   Primärt DNS-suffix. . . . . . . . :
   Nodtyp. . . . . . . . . . . . . . : Hybrid
   IP-routning aktiverat . . . . . . : Nej
   WINS-proxy aktiverat. . . . . . . : Nej
   Söklista för DNS-suffix . . . . . : blixtvik.net

Ethernet-anslutning Anslutning till lokalt nätverk:

   Anslutningsspecifika DNS-suffix . : blixtvik.net
   Beskrivning . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Fysisk adress . . . . . . . . . . : 14-FE-B5-A2-47-B4
   DHCP aktiverat. . . . . . . . . . : Ja
   Autokonfiguration aktiverat . . . : Ja
   Länklokal IPv6-adress . . . . . . : fe80::bca2:4cae:c719:b39a%16(Standard)
   IPv4-adress . . . . . . . . . . . : 83.209.90.34(Standard)
   Nätmask . . . . . . . . . . . . . : 255.255.248.0
   Lånet erhölls . . . . . . . . . . : den 19 april 2011 12:53:11
   Lånet upphör. . . . . . . . . . . : den 19 april 2011 14:13:15
   Standard-gateway. . . . . . . . . : 83.209.88.1
   DHCP-server . . . . . . . . . . . : 83.209.88.1
   IAID för DHCPv6 . . . . . . . . . : 571801269
   DUID för DHCPv6-klient. . . . . . : 00-01-00-18-15-38-C2-76-02-80-37-EC-02-00

   DNS-servrar . . . . . . . . . . . : 87.96.254.52
                                       87.96.254.67
   NetBIOS över TCP/IP . . . . . . . : Aktiverat

Trådlös anslutning Trådlös nätverksanslutning 3:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #
2
   Fysisk adress . . . . . . . . . . : 88-53-2E-0B-B7-DE
   DHCP aktiverat. . . . . . . . . . : Ja
   Autokonfiguration aktiverat . . . : Ja

Trådlös anslutning Trådlös nätverksanslutning 2:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
   Fysisk adress . . . . . . . . . . : 88-53-2E-0B-B7-DE
   DHCP aktiverat. . . . . . . . . . : Ja
   Autokonfiguration aktiverat . . . : Ja

Trådlös anslutning Trådlös nätverksanslutning:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6230
   Fysisk adress . . . . . . . . . . : 88-53-2E-0B-B7-DD
   DHCP aktiverat. . . . . . . . . . : Ja
   Autokonfiguration aktiverat . . . : Ja

Kort för mobilt bredband Mobil bredbandsanslutning:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Dell Wireless 5540 HSPA Mini-Card Network
 Adapter
   Fysisk adress . . . . . . . . . . : 02-80-37-EC-02-00
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Ethernet-anslutning Bluetooth-nätverksanslutning:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Fysisk adress . . . . . . . . . . : 88-53-2E-0B-B7-E1
   DHCP aktiverat. . . . . . . . . . : Ja
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: isatap.{CC560455-9C84-44CE-99D3-C0B66A49EE94}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: isatap.{D6549354-7206-4CAF-9ED0-98B5CCD54B18}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: isatap.{A9280F26-3B14-4803-A2A1-0962F3849810}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: isatap.blixtvik.net:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . : blixtvik.net
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: 6TO4 Adapter:

   Anslutningsspecifika DNS-suffix . : blixtvik.net
   Beskrivning . . . . . . . . . . . : Microsoft 6to4 Adapter
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja
   IPv6-adress . . . . . . . . . . . : 2002:53d1:5a22::53d1:5a22(Standard)
   Standard-gateway. . . . . . . . . : 2002:c058:6301::c058:6301
   DNS-servrar . . . . . . . . . . . : 87.96.254.52
                                       87.96.254.67
   NetBIOS över TCP/IP . . . . . . . : Inaktiverat

Tunnelanslutning: isatap.{888D9E63-17D8-4195-9B88-146F3C344975}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: Teredo Tunneling Pseudo-Interface:

   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja
   IPv6-adress . . . . . . . . . . . : 2001:0:5ef5:79fd:1cb6:29d7:ac2e:a5dd(Stan
dard)
   Länklokal IPv6-adress . . . . . . : fe80::1cb6:29d7:ac2e:a5dd%17(Standard)
   Standard-gateway. . . . . . . . . :
   NetBIOS över TCP/IP . . . . . . . : Inaktiverat

Tunnelanslutning: isatap.{A090A02A-2B04-493D-B8D6-E12411A2935F}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter #6
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost
127.0.0.1       localhost


And Sabayon:
Code: Select all
# cat /etc/resolv.conf
# Generated by resolvconf
search blixtvik.net
nameserver 87.96.254.52
nameserver 87.96.254.67

# cat /etc/hosts
# /etc/hosts: Local Host Database
#
# This file describes a number of aliases-to-address mappings for the for
# local hosts that share this file.
#
# In the presence of the domain name service or NIS, this file may not be
# consulted at all; see /etc/host.conf for the resolution order.
#

# IPv4 and IPv6 localhost aliases
83.209.90.34    FridasLinuxDator        # Added by NetworkManager
127.0.0.1       localhost.localdomain   localhost       sabayon
::1     FridasLinuxDator        localhost6.localdomain6 localhost6
::1             localhost

#
# Imaginary network.
#10.0.0.2               myname
#10.0.0.3               myfriend
#                                                                                                                   
# According to RFC 1918, you can use the following IP networks for private                                         
# nets which will never be connected to the Internet:                                                               
#                                                                                                                   
#       10.0.0.0        -   10.255.255.255                                                                         
#       172.16.0.0      -   172.31.255.255                                                                         
#       192.168.0.0     -   192.168.255.255                                                                         
#                                                                                                                   
# In case you want to be able to connect directly to the Internet (i.e. not                                         
# behind a NAT, ADSL router, etc...), you need real official assigned                                               
# numbers.  Do not try to invent your own network numbers but instead get one                                       
# from your network provider (if any) or from your regional registry (ARIN,                                         
# APNIC, LACNIC, RIPE NCC, or AfriNIC.)                                                                             
#                                     

onyx wrote:Fourthly: load traceroute if you can, and use that to help diagnose the issue. (In Windows it's called tracert, and is usually already there.)


This is from Windows:
Code: Select all
C:\Users\Frida>tracert 149.132.176.64

Spårar väg till www.sabayon.disco.unimib.it [149.132.176.64]
över högst 30 hopp:

  1     1 ms     1 ms   <10 ms  193.111.152.229
  2     1 ms     1 ms   <10 ms  193.111.152.229
  3     1 ms     1 ms     1 ms  ronn-bb-l3s-1-vlan1.cenara.com [195.38.0.28]
  4     4 ms     4 ms    11 ms  semal0001-rc3.ip-only.net [212.112.177.49]
  5     5 ms     5 ms     5 ms  kbn-b3-link.telia.net [213.248.100.113]
  6     5 ms     5 ms     5 ms  kbn-bb2-link.telia.net [80.91.247.112]
  7    11 ms    11 ms    11 ms  hbg-bb2-link.telia.net [80.91.247.226]
  8    20 ms    20 ms    21 ms  ffm-bb2-link.telia.net [80.91.249.88]
  9    36 ms    36 ms    36 ms  mno-b1-link.telia.net [80.91.246.159]
 10    44 ms    44 ms    45 ms  213.248.71.162
 11    44 ms    44 ms    45 ms  rt-mi2-rt-mi3.mi3.garr.net [193.206.134.142]
 12     *       72 ms     *     rt-mi3-ru-unibicocca.mi3.garr.net [193.206.129.1
22]
 13    52 ms    49 ms    49 ms  149.132.254.2
 14    46 ms    48 ms    48 ms  149.132.252.70
 15    45 ms    45 ms    45 ms  vm.sabayon.disco.unimib.it [149.132.176.65]
 16     *        *        *     Begäran gjorde timeout.


And this is Sabayon:
Code: Select all
$ traceroute sabayon.org
traceroute to sabayon.org (149.132.176.64), 30 hops max, 60 byte packets
 1  193.111.152.229 (193.111.152.229)  0.640 ms  1.169 ms  1.309 ms
 2  193.111.152.229 (193.111.152.229)  1.473 ms  1.655 ms  1.775 ms
 3  ronn-bb-l3s-1-vlan1.cenara.com (195.38.0.28)  0.587 ms  0.877 ms  1.041 ms
 4  semal0001-rc3.ip-only.net (212.112.177.49)  4.179 ms  4.190 ms  4.308 ms
 5  kbn-b3-link.telia.net (213.248.100.113)  5.641 ms  5.640 ms  5.631 ms
 6  kbn-bb2-link.telia.net (80.91.246.254)  53.148 ms  25.368 ms kbn-bb2-link.telia.net (80.91.247.112)  5.705 ms
 7  hbg-bb2-link.telia.net (80.91.249.207)  12.638 ms  12.699 ms hbg-bb1-link.telia.net (80.91.254.0)  11.319 ms
 8  ffm-bb2-link.telia.net (213.248.65.121)  22.177 ms ffm-bb2-link.telia.net (80.91.248.85)  22.155 ms ffm-bb2-link.telia.net (80.91.247.142)  19.960 ms
 9  mno-b1-link.telia.net (80.91.249.39)  35.983 ms  35.988 ms  35.249 ms
10  213.248.71.162 (213.248.71.162)  38.837 ms  44.663 ms  38.847 ms
11  rt-mi2-rt-mi3.mi3.garr.net (193.206.134.142)  38.946 ms  45.742 ms  38.916 ms
12  rt-mi3-ru-unibicocca.mi3.garr.net (193.206.129.122)  78.038 ms  81.721 ms  81.347 ms
13  149.132.254.2 (149.132.254.2)  52.853 ms  48.565 ms  48.544 ms
14  149.132.252.70 (149.132.252.70)  46.059 ms  45.949 ms  45.903 ms
15  vm.sabayon.disco.unimib.it (149.132.176.65)  39.504 ms  39.519 ms *
16  vm.sabayon.disco.unimib.it (149.132.176.65)  39.491 ms  39.476 ms  46.115 ms


This is so strange, traceroute works the same in Sabayon as in Windows, and when I do that I can actually see that data is transmitted on the graph in the NetworkManager, but when I try a web browser nothing is transmitted and if nothing is sent I can't get anything back.
orange_angel
Young Hen
 
Posts: 22
Joined: Tue Jun 29, 2010 16:37

Re: Wired Internet connection

Postby onyx » Wed Apr 20, 2011 9:21

Ok, so given that your networking works for the DNS, and traceroute tunneling, the only answer is that the network card in that machine has a chipset that the linux driver does not like, so it's borking http traffic. If it's a desktop pc it's cheap and easy to drop another pci network card in. Realtek is real cheap and really reliable. RTL8169 based PCI cards give you gigabit networking with other machines...that speed not needed for the net though. If it's a laptop you'll have to try finding a USB based NIC.

Or check the kind of NIC it is with lspci, then do some research to see if others are having issues with the same card, and maybe have some workarounds.

Sure is a weird one, but not unheard of.
onyx
Baby Hen
 
Posts: 13
Joined: Thu Jan 13, 2011 10:54
Location: NZ

Re: Wired Internet connection

Postby orange_angel » Wed Apr 20, 2011 10:24

Thanks for the help! It's a laptop with a network card called Intel Corporation Centrino Advanced-N 6230, searching for it only brings up questions about how to get wireless to work and I've already solved that problem.

The difference between the network here and the network where the wired connection worked is that there's no router here. Could a router make the connection work? We used to have a router here too, but we haven't bought a new one since it stopped working, so if that would solve the problem I would be happy to buy a new router.
orange_angel
Young Hen
 
Posts: 22
Joined: Tue Jun 29, 2010 16:37

Re: Wired Internet connection

Postby onyx » Wed Apr 20, 2011 10:41

That card is wireless only http://www.intel.com/products/wireless/adapters/6230/index.htm, so there is another in the system, most likely part of the mainboard, that is providing the wired connection. What is the name/brand/model of the laptop?

In order to get packets of data out to the internet, which is what you were doing with traceroute, you have a router there somewhere; probably inside the modem you use (eg ADSL modems are routers, routing from one/multiple ethernet connections to a LAN out to the internet). Yes, a couple of years back you could get sole routers that passed traffic from the LAN to a modem, but they are scarce now because the modem does it all.
onyx
Baby Hen
 
Posts: 13
Joined: Thu Jan 13, 2011 10:54
Location: NZ

Re: Wired Internet connection

Postby onyx » Wed Apr 20, 2011 10:44

Incidentally, did you try another web browser? Just in case the first is broken or set to get data from proxy or something?
onyx
Baby Hen
 
Posts: 13
Joined: Thu Jan 13, 2011 10:54
Location: NZ

Re: Wired Internet connection

Postby dunsurfin » Wed Apr 20, 2011 11:31

onyx wrote:In order to get packets of data out to the internet, which is what you were doing with traceroute, you have a router there somewhere; probably inside the modem you use (eg ADSL modems are routers, routing from one/multiple ethernet connections to a LAN out to the internet). Yes, a couple of years back you could get sole routers that passed traffic from the LAN to a modem, but they are scarce now because the modem does it all.


Cable routers are very common now and may be a workaround. They attach to a modem or other ethernet cable and are not expensive.
Self-righteousness is a loud din raised to drown the voice of guilt within us - Eric Hoffer

Don't believe what it says on the right - I am anything but sagely; More oniony!
dunsurfin
Sagely Hen
 
Posts: 1333
Joined: Sun Jan 07, 2007 21:38
Location: Newcastle upon Tyne UK

Re: Wired Internet connection

Postby orange_angel » Wed Apr 20, 2011 12:54

Yes I've tried other web browsers and I can't get anything to download with equo either, but I didn't realise that the Network Controller only had something to do with wireless connections. My Ethernet controller is called Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit and searching for that on the net does give me some interesting results, so I'll take a look at them when I get the time. The computer is a Dell XPS L502x.
orange_angel
Young Hen
 
Posts: 22
Joined: Tue Jun 29, 2010 16:37

Re: Wired Internet connection

Postby orange_angel » Wed Apr 20, 2011 18:15

When I searched for Realtek RTL8111/8168B I found some results that mention that it was possible that the kernel used the wrong module (r8169) and that it was better to use the driver module from Realteks website (r8168). So I changed the module to r8168, but that made no difference. There is apparently som performance issues with rev 6 of the network controller (see https://bugs.launchpad.net/ubuntu/+sour ... bug/699761 ) and I have that.

I'll go and buy a router tomorrow, if I get a wireless one I know I can at least use that connection and it would be practical to be able to use more than one internet connection here anyway.

There's just one thing I'm wondering about, in the output from ethtools -i eth0, there's no firmware-version specified, shouldn't it be something there?

Code: Select all
# ethtool -i eth0
driver: r8168
version: 8.023.00-NAPI
firmware-version:
bus-info: 0000:06:00.0
orange_angel
Young Hen
 
Posts: 22
Joined: Tue Jun 29, 2010 16:37

Next

Return to Networking and Wireless

Who is online

Users browsing this forum: No registered users and 2 guests

cron