Can't get OpenSuse 13.1 to connect to a specific router

I am unable to connect to a specific router with a wired connection after a new installation of OpenSuse 13.1 on new hardware. I have spent several days trying to diagnose this issue. This is part of an effort to replace the two working computers with newer computers that have more memory and support USB 3.0. So far I have not been able to make the change because of this issue.
I would greatly appreciate it i someone could help me to resolve this issue.

I have been running the same version of the software on two other computers since January, connecting to the same routers without any issues. OpenSuse was installed on the new computer from the same DVD as the other two. One router is for an internal network, and the other router, the one I can’t connect to, is for a Frontier Communications DSL connection. the two older computers can connect to the Frontier router, the new computer can’t.

The light on the router and on the Ethernet card shows that the cable is connected. When OpenSuse gets to a later part of its initialization during the boot process, the light goes out. Network Manager reports it as the cable is unplugged. If I restart the computer or shut it down, the light on the router goes back on as soon as OpenSuse shuts down.

I started with traditional networking. I searched the internet for answers and tried a number of things listed there, but none of them worked. Finally, I switched to Network Manager. That made the boot process run MUCH faster, and it started to work. I then performed the online updates, and after the required restart the issue came back up, and I haven’t been able to get it to work since then.

I have no such issues with the router for my internal network. Whether the cable is connected during a boot or if I connect it later, it works correctly.

I have reinstalled OpenSuse a few times with different options, and once taking all of the default options. The same thing occurs. During installation, the light on the router goes out during the later part of the installation, when the networking is being configured.

I downloaded Mint 17 and Ubuntu 14.04. The same issue occurred when I booted the computer from them on “live dvds”.

The motherboard has a built-in Ethernet connection, but I have it disabled in the bios. I have a PCI Express card installed to provide two Ethernet connections to be able to connect to both my internal and external networks. The same issue occurs with the motherboard connection if I take out the card and enable the motherboard bios. All of the Ethernet devices are by Realtek.

Below I will paste the results of a number of diagnostics commands I ran based on information requested on other internet posts. At the time I had only the Frontier router plugged in, my internal router was not connected.

Thank you.

/usr/sbin/hwinfo --netcard

45: PCI 700.0: 0200 Ethernet controller                         
  [Created at pci.319]
  Unique ID: QgzS.ciCxRpua525
  Parent ID: _axC.L+o1sJPk4X9
  SysFS ID: /devices/pci0000:00/0000:00:0a.0/0000:05:00.0/0000:06:01.0/0000:07:00.0
  SysFS BusID: 0000:07:00.0
  Hardware Class: network
  Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
  SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  SubDevice: pci 0x8168 
  Revision: 0x06
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp7s0
  I/O Ports: 0xb000-0xbfff (rw)
  Memory Range: 0xd2204000-0xd2204fff (ro,non-prefetchable)
  Memory Range: 0xd2200000-0xd2203fff (ro,non-prefetchable)
  IRQ: 98 (2 events)
  HW Address: 68:1c:a2:12:29:f9
  Link detected: no
  Module Alias: "pci:v000010ECd00008168sv000010ECsd00008168bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #43 (PCI bridge)

46: PCI 800.0: 0200 Ethernet controller
  [Created at pci.319]
  Unique ID: I+SI.ciCxRpua525
  Parent ID: 2i_g.L+o1sJPk4X9
  SysFS ID: /devices/pci0000:00/0000:00:0a.0/0000:05:00.0/0000:06:02.0/0000:08:00.0
  SysFS BusID: 0000:08:00.0
  Hardware Class: network
  Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
  SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."                                                                                             
  SubDevice: pci 0x8168                                                                                                                               
  Revision: 0x06                                                                                                                                      
  Driver: "r8169"                                                                                                                                     
  Driver Modules: "r8169"                                                                                                                             
  Device File: enp8s0                                                                                                                                 
  I/O Ports: 0xa000-0xbfff (rw)                                                                                                                       
  Memory Range: 0xd2104000-0xd2104fff (ro,non-prefetchable)                                                                                           
  Memory Range: 0xd2100000-0xd2103fff (ro,non-prefetchable)                                                                                           
  IRQ: 99 (no events)                                                                                                                                 
  HW Address: 68:1c:a2:12:29:fa                                                                                                                       
  Link detected: no                                                                                                                                   
  Module Alias: "pci:v000010ECd00008168sv000010ECsd00008168bc02sc00i00"                                                                               
  Driver Info #0:                                                                                                                                     
    Driver Status: r8169 is active                                                                                                                    
    Driver Activation Cmd: "modprobe r8169"                                                                                                           
  Config Status: cfg=no, avail=yes, need=no, active=unknown                                                                                           
  Attached to: #44 (PCI bridge) 

/usr/sbin/hwinfo --network

58: None 00.0: 10701 Ethernet                                   
  [Created at net.124]
  Unique ID: 6KEL.ndpeucax6V1
  Parent ID: QgzS.ciCxRpua525
  SysFS ID: /class/net/enp7s0
  SysFS Device Link: /devices/pci0000:00/0000:00:0a.0/0000:05:00.0/0000:06:01.0/0000:07:00.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp7s0
  HW Address: 68:1c:a2:12:29:f9
  Link detected: no
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #38 (Ethernet controller)

59: None 00.0: 10701 Ethernet
  [Created at net.124]
  Unique ID: zejA.ndpeucax6V1
  Parent ID: I+SI.ciCxRpua525
  SysFS ID: /class/net/enp8s0
  SysFS Device Link: /devices/pci0000:00/0000:00:0a.0/0000:05:00.0/0000:06:02.0/0000:08:00.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp8s0
  HW Address: 68:1c:a2:12:29:fa
  Link detected: no
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #39 (Ethernet controller)

60: None 00.0: 10700 Loopback
  [Created at net.124]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

tail -f /var/log/messages
2014-06-26T13:19:47.937360-05:00 lh2 systemd[1]: Started Stop Read-Ahead Data Collection.
2014-06-26T13:20:05.721562-05:00 lh2 systemd[1]: Stopping Network Manager...
2014-06-26T13:20:05.739586-05:00 lh2 systemd[1]: Stopped Network Manager.
2014-06-26T13:20:11.849264-05:00 lh2 systemd[1]: Starting Network Manager...
2014-06-26T13:20:11.940473-05:00 lh2 systemd[1]: Started Network Manager.
2014-06-26T13:20:12.049525-05:00 lh2 kernel:    58.996559] r8169 0000:07:00.0 enp7s0: link down
2014-06-26T13:20:12.049543-05:00 lh2 kernel:    58.996635] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
2014-06-26T13:20:12.049546-05:00 lh2 kernel:    58.996647] r8169 0000:07:00.0 enp7s0: link down
2014-06-26T13:20:12.154911-05:00 lh2 kernel:    59.101716] r8169 0000:08:00.0 enp8s0: link down
2014-06-26T13:20:12.154921-05:00 lh2 kernel:    59.101784] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready


tail -f /var/log/NetworkManager
2014-06-26T13:20:12.051431-05:00 lh2 NetworkManager[930]: <info> (enp8s0): carrier is OFF
2014-06-26T13:20:12.052031-05:00 lh2 NetworkManager[930]: <info> (enp8s0): new Ethernet device (driver: 'r8169' ifindex: 3)
2014-06-26T13:20:12.052540-05:00 lh2 NetworkManager[930]: <info> (enp8s0): exported as /org/freedesktop/NetworkManager/Devices/1
2014-06-26T13:20:12.052997-05:00 lh2 NetworkManager[930]: <info> (enp8s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
2014-06-26T13:20:12.053443-05:00 lh2 NetworkManager[930]: <info> (enp8s0): bringing up device.
2014-06-26T13:20:12.154562-05:00 lh2 NetworkManager[930]: <info> (enp8s0): preparing device.
2014-06-26T13:20:12.155140-05:00 lh2 NetworkManager[930]: <info> (enp8s0): deactivating device (reason 'managed') [2]
2014-06-26T13:20:12.155663-05:00 lh2 NetworkManager[930]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
2014-06-26T13:20:12.156683-05:00 lh2 NetworkManager[930]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
2014-06-26T13:20:12.166903-05:00 lh2 NetworkManager[930]: <info> ModemManager available in the bus

ifconfig
enp7s0    Link encap:Ethernet  HWaddr 68:1C:A2:12:29:F9  
          UP BROADCAST 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)

enp8s0    Link encap:Ethernet  HWaddr 68:1C:A2:12:29:FA  
          UP BROADCAST 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)

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:65536  Metric:1
          RX packets:120 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:9096 (8.8 Kb)  TX bytes:9096 (8.8 Kb)

tcpdump -i enp7so -n
tcpdump: enp7so: No such device exists
(SIOCGIFHWADDR: No such device)

tcpdump -i enp8so -n
tcpdump: enp8so: No such device exists
(SIOCGIFHWADDR: No such device)

ethtool enp7s0
Settings for enp7s0:
        Supported ports:  TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: no

        
ethtool enp8s0
Settings for enp8s0:
        Supported ports:  TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: no

Well,
From what you posted IMO the system seems pretty emphatic it doesn’t think that the physical link state is up.

Recommend… For diagnosis…

  • Swap patch cable with another
  • Verify it really is a patch cable and not a cross-over cable
  • Connect to a different router port
  • Connect to a different router
  • Connect to a hub instead of a router
  • Open up the specs for your NIC and verify it’s recognized correctly and the device driver is appropriate
  • Use a different NIC, for starters it looks like you have 2 although both appear to be the same manufacturer. If another is available try it.

Your first objective is to see if you can find a physical network configuration where your link state looks good (green lights) and is reported good.
Only after that, <then> figure out how that configuration can be fit into your network.

AFAIK the physical link state has nothing to do with software (at least a wired connection). Software may be made not to work with hardware, but AFAIK that should still not affect the link state lights on the NICs.

TSU

similar problem found when installing new modem, fault seen
only on one machine (of 5)

solution:-

delete or rename file /etc/resolv.conf

then try connection again

hth

cp -v /etc/resolv.conf.netconfig /etc/resolv.conf

Then try to reconfigure/reconnect. :wink:

It was the port on the router! Thank you to everyone for your assistance.

I had previously ruled out the cable and router port because they were being used by one of the other two OpenSuse computers I mentioned in my original post before I assembled the new computer. But I guess things break and I should have known to check everything. Not checking everything cost me many hours of unnecessary diagnostic time, and multiple unnecessary re-installations.