Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Network problem - powerline adapter

  1. #1

    Default Network problem - powerline adapter

    I've had some problems with the network when it comes to internet on this machine. I use it primarily in the workgroup as a file server, but I use it when I want to go on the internet as well. in long periods it works fine, but suddenly it does not connect to the internett. I have maybe done something wrong with network settings. When I go to the network settings in Yast I get a error message that says:

    Code:
    More than one interface asks to control the hostname via DHCP. If you keep the current settings, the behavior is non deterministic.
    
    Involved configuration files:
    ifcfg-en2s0 dhcp
    I thought the only interface I use is en2s0? I need some guidance with this problem, because it's really annoying to wait or restart the adapter to get the internett up and running again.

    Dag R

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Network problem - powerline adapter

    No stale config files?
    Code:
    ls -l /etc/sysconfig/network/ifcfg-*

  3. #3

    Default Re: Network problem - powerline adapter

    I don't know what you mean by stale in this connection, but in Norwegian understanding of the word we think of food getting old and start to rotten. But here is what output of what you asked for:

    Code:
    dagr@opensuse:~> ls -l /etc/sysconfig/network/ifcfg-*
    -rw------- 1 root root 178 jan.  14 22:56 /etc/sysconfig/network/ifcfg-enp2s0
    -rw------- 1 root root 147 jan.  11 17:15 /etc/sysconfig/network/ifcfg-lo

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Network problem - powerline adapter

    I meant some leftover (now irrelevant) config file lurking. That looks as expected.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Network problem - powerline adapter

    Hang on - you mentioned en2s0, but your config file is named 'ifcfg-enp2s0'. What is actually reported by ifconfig?
    Code:
    /sbin/ifconfig

  6. #6

    Default Re: Network problem - powerline adapter

    It's nothing. There is't anything in the file (/sbin/ifconfig).

    Dag R

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Network problem - powerline adapter

    Quote Originally Posted by dagring View Post
    It's nothing. There is't anything in the file (/sbin/ifconfig).

    Dag R
    It's not a file. It's a command. Run
    Code:
    /sbin/ifconfig -a
    and
    Code:
    /usr/sbin/hwinfo --netcard
    Please enclose the output within code tags (refer to the '#' button in the forum editor).
    Last edited by deano_ferrari; 17-Jan-2018 at 16:48.

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,799

    Default Re: Network problem - powerline adapter

    Good old ifconfig is not installed by default anymore .

    One is supposed to use ip.

    Normally a problem like this is checked from inside to outside. Thus the the first step is
    Code:
    ip addr
    to see which NICs are configured and how.
    As the OPs story seems to imply that he can connect within the LAN, I assume that that is OK, but nevertheless it is good to show it.

    Next step would be a ping to an address inside the LAN to prove that connecting inside is OK. As I said above, that seems to be OK according to the OPs statement
    Code:
    ping -c1 <IP-address>
    where <IP-address> must be replaced by an IP address of a functioning system in the LAN, preferable the router.

    Then to go outside the LAN we need a route, most often the default route, pointing o the router that connects the LAN to to he outside world:
    Code:
    ip route
    When a default route shows via the router, it must be possible to ping to the internet:
    Code:
    ping -c1 130.57.66.6
    Whne that connection is OK, there is connection to the internet.

    Last step is to check if DNS functions:
    Code:
    ping -c1 forums.opensuse.org
    When one of these steps fails, testing next step(s) is useless. First that problem ust be solved.

    So please @dagring .........
    Henk van Velden

  9. #9

    Default Re: Network problem - powerline adapter

    Quote Originally Posted by deano_ferrari View Post
    It's not a file. It's a command. Run
    Code:
    /sbin/ifconfig -a
    Code:
    /sbin/ifconfig -a
    bash: /sbin/ifconfig: Ingen slik fil eller filkatalog
    and
    Code:
    /usr/sbin/hwinfo --netcard
    Code:
    dagr@opensuse:~> /usr/sbin/hwinfo --netcard
    25: PCI 200.0: 0200 Ethernet controller                         
      [Created at pci.378]
      Unique ID: c3qJ.1WVRdh9En64
      Parent ID: 8otl.om932x2mw06
      SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: network
      Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
      SubDevice: pci 0x8505 "P8 series motherboard"
      Revision: 0x09
      Driver: "r8169"
      Driver Modules: "r8169"
      Device File: enp2s0
      I/O Ports: 0xd000-0xd0ff (rw)
      Memory Range: 0xd0004000-0xd0004fff (ro,non-prefetchable)
      Memory Range: 0xd0000000-0xd0003fff (ro,non-prefetchable)
      IRQ: 47 (7983018 events)
      HW Address: 9c:5c:8e:89:6a:f0
      Permanent HW Address: 9c:5c:8e:89:6a:f0
      Link detected: yes
      Module Alias: "pci:v000010ECd00008168sv00001043sd00008505bc02sc00i00"
      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: #29 (PCI bridge)
    d
    Please enclose the output within code tags (refer to the '#' button in the forum editor).
    The first command said no file or folder, the second gave some more information.

    Dag R

  10. #10

    Default Re: Network problem - powerline adapter

    Quote Originally Posted by hcvv View Post
    Good old ifconfig is not installed by default anymore .

    One is supposed to use ip.

    Normally a problem like this is checked from inside to outside. Thus the the first step is
    Code:
    ip addr
    Code:
    ip adress
    Object "adress" is unknown, try "ip help".
    to see which NICs are configured and how.
    As the OPs story seems to imply that he can connect within the LAN, I assume that that is OK, but nevertheless it is good to show it.

    Next step would be a ping to an address inside the LAN to prove that connecting inside is OK. As I said above, that seems to be OK according to the OPs statement
    Code:
    ping -c1 <IP-address>
    Code:
    dagr@opensuse:~> ping -c1 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=5.84 ms
    
    --- 192.168.1.1 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 5.843/5.843/5.843/0.000 ms
    where <IP-address> must be replaced by an IP address of a functioning system in the LAN, preferable the router.
    Code:
    
    
    Then to go outside the LAN we need a route, most often the default route, pointing o the router that connects the LAN to to he outside world:
    Code:
    ip route
    Code:
    dagr@opensuse:~> ip route
    default via 192.168.1.1 dev enp2s0 
    192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.9
    When a default route shows via the router, it must be possible to ping to the internet:
    Code:
    ping -c1 130.57.66.6
    Code:
    dagr@opensuse:~> ping -c1 130.57.66.6
    PING 130.57.66.6 (130.57.66.6) 56(84) bytes of data.
    
    --- 130.57.66.6 ping statistics ---
    1 packets transmitted, 0 received, 100% packet loss, time 0ms
    Whne that connection is OK, there is connection to the internet.

    Last step is to check if DNS functions:
    Code:
    ping -c1 forums.opensuse.org
    Code:
    ping -c1 forums.opensuse.org
    PING forums.opensuse.org (130.57.66.6) 56(84) bytes of data.
    64 bytes from 130.57.66.6 (130.57.66.6): icmp_seq=1 ttl=45 time=175 ms
    
    --- forums.opensuse.org ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 175.784/175.784/175.784/0.000 ms
    When one of these steps fails, testing next step(s) is useless. First that problem ust be solved.

    So please @dagring .........
    I have run those test, what does -c1 means?

    Dag R

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •