Can't set up wired connection on new install

English Network/Internet
1

Hi all,

Relative Linux noob here, complete noob to opensuse. Have a new leap install and there’s no wired connection even though eth0 is recognised, drivers are there etc. YaST sees the ethernet controller but I’m not sure how to set up the connection (might be a problem with DHCP, which expressly didn’t work during the install. Works fine on Windows on the same machine though. Not sure if that’s relevant).

I’m using wicked but no dice on NetworkManager either. I tried disabling DHCP and copying network settings from Windows, which is dual booted on the same machine, but still got nothing (eventually it claimed it had connected, but I still had no internet access). When NetworkManager fails to connect, it says ‘IP configuration was unavailable’.

Any help appreciated.

2

Welcome to openSUSE Forums dap5. You may need to configure wicked for your network environment first.

YaST > System > Network Settings > Overview, select your network device and click ‘Edit’ to configure, follow the prompts given.

https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.basicnet.html#sec.basicnet.yast

BTW, the configured settings can be found in the /etc/sysconfig/network/ directory eg ifcfg-eth0

3

Thanks for the reply. I’m at the point in configuration where YaST is supposed to set up the connection for me via DHCP, but it’s not happening.

/etc/ifcfg-eth0 contents look like this:

BOOTPROTO='dhcp'
STARTMODE='auto'
DHCLIENT_SET_HOSTNAME='yes'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
PREFIXLEN='30'

I’ve tried to follow the instructions for wicked but think I must be missing something with DHCP setup?

4

/etc/ifcfg-eth0 is not used at all.
It should be /etc/sysconfig/network/ifcfg-eth0, as deano_ferrari wrote.

Also, you may have two (or more) conflicting configs for the same card, so please post a directory listing of /etc/sysconfig/network/ as well…

ls /etc/sysconfig/network/

OTOH, you may just have a DNS issue.
Can you reach hosts via the IP address?
E.g.:

ping 8.8.8.8

Oh, and the output of “/sbin/ifconfig” should show whether your interface has a valid IP address or not.

5

Sorry, that’s what I meant. /etc/sysconfig/network/ifcfg-eth0 is what I posted.

Directory listing of /etc/sysconfig/network/:

config
dhcp
ifcfg-eth0
ifcfg-lo
ifcfg.template
if-down.d
ifroute-eth0
if-up.d
providers
routes
scripts

Ping results in ‘Network is unreachable’.

/sbin/ifconfig output:

eth0      Link encap:Ethernet  HWaddr 74:D4:35:5E:B0:ED  
          inet6 addr: fe80::76d4:35ff:fe5e:b0ed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 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:154 (154.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:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:1200 (1.1 Kb)  TX bytes:1200 (1.1 Kb)
6

Alright, I somehow expected that but wasn’t sure… :wink:

Directory listing of /etc/sysconfig/network/:

Looks fine.

Ping results in ‘Network is unreachable’.

/sbin/ifconfig output:

Right, you don’t have an IP(v4) address.

Unless you have an IPv6 only network (which I’d find unlikely), this seems to indicate that DHCP is indeed not working as you wrote.
And as it works in Windows, it’s unlikely to be a network problem I suppose.

So, IMHO this may be a driver issue.
What network card do you have exactly?

/sbin/lspci -nnk

And please check that the package kernel-firmware is installed, this is necessary (for some drivers at least).
E.g. via:

rpm -q kernel-firmware
7

Yes, a bit new to this as I said :slight_smile:

Tail of /sbin/lspci:

05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
    Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:e000]
    Kernel driver in use: r8169
    Kernel modules: r8169

And I think the kernel firmware is installed:

kernel-firmware-20160516git-3.1.noarch
8

If I were to guess,
Because you are dual-booting your machine, you’re not getting your DHCP address because your DHCP lease issued to your Windows OS hasn’t expired.
When you installed your openSUSE, DHCP looked at your DHCP request and said “An address for that MAC address has already been issued” so ignored the request.

Solution 1
At least temporarily and to prove this is the problem, you can log into your home Gateway router where the DHCP server is running, find the DHCP lease and delete/cancel it. After that, you can restart network services (see Solution 3 below) to obtain your lease.

Solution 2
Configure a masked/alternate MAC address The procedure will depend on whether you’re configuring your network settings using Wicked or Network Manager.

Solution 3
Request a new DHCP lease.
Typically you can do this with openSUSE by restarting the network service if you weren’t dual-booting, I don’t know if it will work in your case. Run the following command

systemctl restart network

And, when you’re in Windows

ipconfig /renew

Solution 4
Don’t use DHCP, configure fixed network settings.
If you don’t know how to do this, then you need to post your Windows network settings and then we can post proposed settings for your openSUSE.
To display your network settings in Windows, run the following two commands in a CMD prompt

ipconfig /all

route print

HTH,
TSU

9

I really thought you had it then. But still no luck. I allowed the lease to expire (there wasn’t an option to cancel it in the router configuration page, weirdly) and restarted the network using systemctl and still nothing. Does that mean configuring an alternate MAC address wouldn’t work?

Opensuse seems to have no interaction with the LAN at all, and the router doesn’t know opensuse is there either (there’s no mention of it in the configuration). It’s like the ethernet cable isn’t plugged in (except dmesg says ‘link up’, that’s the only indication).

I tried configuring fixed network settings in wicked and it didn’t work, but it’s more than possible that I did it wrong.

C:\Users\Dan>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Dan-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-8F-4C-82-59
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::453b:e47d:adae:835d%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.41.10.6(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Lease Obtained. . . . . . . . . . : 15 March 2017 12:17:57
   Lease Expires . . . . . . . . . . : 15 March 2018 12:17:57
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 10.41.10.5
   DHCPv6 IAID . . . . . . . . . . . : 302055311
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-99-07-34-10-FE-ED-24-3B-0C

   DNS Servers . . . . . . . . . . . : 209.222.18.222
                                       209.222.18.218
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 74-D4-35-5E-B0-ED
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e9d7:3431:ec28:2434%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 15 March 2017 12:17:29
   Lease Expires . . . . . . . . . . : 16 March 2017 12:17:29
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 477418549
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-99-07-34-10-FE-ED-24-3B-0C

   DNS Servers . . . . . . . . . . . : 194.168.4.100
                                       194.168.8.100
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{DF0B3EA5-72B9-4A64-A875-AEAEEA393D65}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


C:\Users\Dan>route print
===========================================================================
Interface List
 18...00 ff 8f 4c 82 59 ......TAP-Windows Adapter V9
 14...74 d4 35 5e b0 ed ......Realtek PCIe GBE Family Controller
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.11     20
          0.0.0.0        128.0.0.0       10.41.10.5       10.41.10.6     20
       10.41.10.1  255.255.255.255       10.41.10.5       10.41.10.6     20
       10.41.10.4  255.255.255.252         On-link        10.41.10.6    276
       10.41.10.6  255.255.255.255         On-link        10.41.10.6    276
       10.41.10.7  255.255.255.255         On-link        10.41.10.6    276
  104.238.169.117  255.255.255.255      192.168.0.1     192.168.0.11     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
        128.0.0.0        128.0.0.0       10.41.10.5       10.41.10.6     20
      169.254.0.0      255.255.0.0         On-link      192.168.0.11    296
  169.254.255.255  255.255.255.255         On-link      192.168.0.11    276
      192.168.0.0    255.255.255.0         On-link      192.168.0.11    276
     192.168.0.11  255.255.255.255         On-link      192.168.0.11    276
    192.168.0.255  255.255.255.255         On-link      192.168.0.11    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.0.11    276
        224.0.0.0        240.0.0.0         On-link        10.41.10.6    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.0.11    276
  255.255.255.255  255.255.255.255         On-link        10.41.10.6    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 14    276 fe80::/64                On-link
 18    276 fe80::/64                On-link
 18    276 fe80::453b:e47d:adae:835d/128
                                    On-link
 14    276 fe80::e9d7:3431:ec28:2434/128
                                    On-link
  1    306 ff00::/8                 On-link
 14    276 ff00::/8                 On-link
 18    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

Could you suggest some settings for me for a fixed network? At least if that doesn’t work then I’ll know the problem isn’t just DHCP after all.

10

I can’t remember off the top of my head what it means when the Windows network address is designated “preferred” - Whether it might mean that the alternate network configuration is also filled in, or something else like using a DHCP lease beyond expiration. According to your routing table, it does look like a Class C private network may be configured somewhere.

First, a comment about your IP address range, I find it odd that it’s so tiny.
Did you set up your own LAN or is this assigned to you by your ISP?
If by your ISP, it looks like it has subnetted incredibly tiny address ranges to its customers, only four addresses, and when you exclude the highest and lowest addresses (which are unusable) that leaves only two addresses…

In fact, because only two addresses are permitted… And the DHCP server/gateway is using one address and your Windows machine is using the other, you actually don’t have any valid addresses you can assign your openSUSE

If this Gateway device is something you can manage and configure, then stop right here and ignore what I describe below, because your first step should be to modify your private address range at your Gateway to allow a large/reasonable number of addresses… ie change your subnet mask to something like 255.255.0.0 which would be a nice, middle of the road setting that permits later further subnetting or supernetting.

All that follows assumes that you cannot re-configure your gateway device…

So,
Probably your next step should be to call up whomever set up your Internet connection and ask them “What’s up? Why are you subnetted to only be allocated 2 addresses with one used by the gateway device so leaving you with only one address for one machine?”

Considering that you’ve been allocated a piece of a Class A private network, it’s incredibly over-restrictive (I can think of worse descriptions) to not grant you a fairly large range of addresses unless they just don’t want you to set up a single device/machine.

The alternative is to just configure your openSUSE with the same settings assigned to your Windows OS, but that will likely mean poor networking.

When configuring openSUSE with fixed settings using Wicked,

  • Edit your network adapter settings, specifying fixed addresses.
  • Be sure to configure your DNS, you may want to point to Google DNS instead (eg 8.8.8.8)
  • Not in your network adapter settings, configure the Routing tab specifying your Default Gateway as described in your “route print” (ie 10.41.10.5)

TSU

11

I’m a little lost now. How do I know whether I can configure the gateway settings? And do you mean a tiny range of addresses that can be assigned to different devices? Because I also have a Macbook and an Android phone connected to the same LAN, plus a couple of other devices at various times. Also, I’m not sure what it means by ‘preferred’ IP address.

What would it mean if a Class C private network were configured somewhere?

Does this look any different (I honestly have no idea what I’m looking for):

C:\Users\Dan>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Dan-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-8F-4C-82-59
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 74-D4-35-5E-B0-ED
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e9d7:3431:ec28:2434%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 15 March 2017 12:17:29
   Lease Expires . . . . . . . . . . : 16 March 2017 12:17:29
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 477418549
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-99-07-34-10-FE-ED-24-3B-0C

   DNS Servers . . . . . . . . . . . : 194.168.4.100
                                       194.168.8.100
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{DF0B3EA5-72B9-4A64-A875-AEAEEA393D65}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Dan>route print
===========================================================================
Interface List
 18...00 ff 8f 4c 82 59 ......TAP-Windows Adapter V9
 14...74 d4 35 5e b0 ed ......Realtek PCIe GBE Family Controller
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.11     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link      192.168.0.11    296
  169.254.255.255  255.255.255.255         On-link      192.168.0.11    276
      192.168.0.0    255.255.255.0         On-link      192.168.0.11    276
     192.168.0.11  255.255.255.255         On-link      192.168.0.11    276
    192.168.0.255  255.255.255.255         On-link      192.168.0.11    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.0.11    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.0.11    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 14    276 fe80::/64                On-link
 14    276 fe80::e9d7:3431:ec28:2434/128
                                    On-link
  1    306 ff00::/8                 On-link
 14    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
12

Based on your Windows network settings which were assigned by DHCP,

Someone configured your LAN with near impossible boundaries.
Ordinarily,
When someone designs a LAN, the size would be set to accommodate at least a reasonable number of devices with room to expand.

But,
Whoever set up your Gateway device configured a network which can accommodate at most 2 wired addresses. If you also have a wireless network, then that might be configured as a physically different network so is not relevant to your wired network troubles (Is that the “alternative” address that might be configured which would start with 192.168 ?). Since one of the addresses is used by the Gateway server, that leaves only one address that can be assigned to any/all devices in your wired LAN.

You can read up on how the subnet mask works, basically it splits any network address into 2 parts… the NetworkID and the Host Address. You can think of it as similar to a street address and a house number. Ordinarily City Planners are going to allow as many numbers as needed on the street, but let’s say in a binary world that you only allow two house addresses, and one is occupied by the Mayor. How then can you build more than one other house on the same street with a unique address without changing the address scheme? – You can’t. And, that’s how your Gateway Server is currently configured.

You can find the definition of a Class A Private Network many places on the Web… The only requirement is that the first of the four octet numbers has to be a “10,” ie 10.x.y.z. The “standard” subnet mask is 255.0.0.0 which allows for only the one NetworkID (the “10”) and a maximum number of addresses which can be assigned to devices, so it allows for a great many possibilities creating smaller subnets (changing the x or y or many z possible octets), but doesn’t allow for supernetting which is rarely done.

Without going into all that subnetting and supernetting, there are a great many possibilities between the two extremes of the Class A standard subnet I described above and what someone configured in your Gateway… I just arbitrarily picked one and suggested it to you (255.255.0.0) although if you do any VPNs, that should also affect your best decision.

In other words,
The most important takeaway is that when you’re designing a LAN, you should always choose a subnet mask that allows you a “middle of the road” balance between NetworkID and HostiD and never an extreme on one side or the other as now exists in your LAN (unless of course it was done on purpose).

Who set up your Gateway device, your ISP or yourself… Or someone you know?

TSU

13

Addendum to what I posted above,

What I’ve described should be fixed before anything else because only after you enlarge the number of total addresses which <can> be used in the network can you <then> re-configure the DHCP service to support a larger number of addresses which can be issued to Hosts in your LAN.

And then, only after all that has been done can you then re-visit what kind of issues your openSUSE might have getting a DHCP lease.

TSU

14

OK, thanks for the patience and the explanation. Clearly I’ve got a lot of reading to do.

I didn’t have a hand in configuring the network - obviously I would have been in over my head - so it must be the ISP’s settings I’m using, since I didn’t get anyone else to do it. Although you’re right, it doesn’t make sense that they’d only let me assign two IP addresses for wired connections. The router they give you has four ethernet sockets in the back apart from anything else! I don’t think it can have been deliberate.

I do use a VPN, and it was connected the first time I posted ipconfig /all and wasn’t connected the second time. Wasn’t sure if it would make a difference.

15

If you know who set up your Gateway router, that should be the person you talk to first about fixing your situation.
If your ISP did that, then they should fix it.
If you hired or asked someone specific to set up your router, then that person should be contacted.
If you set up the router yourself, then hopefully you have a start on what you should do, and find more information in the router’s documentation.

TSU

16

I haven’t managed to find a solution to this, but in the interest of testing, I did connect some other devices to the router. Using a wired connection, both a Macbook and a Raspberry Pi connected to the network using DHCP instantly, without any manual interfering, at the same time. To reiterate, I’m obviously not an expert, but doesn’t this mean the network is capable of assigning more IP addresses over ethernet? And doesn’t that mean the problem is more likely to be with the Windows/Linux machine?

17

Nope, this is what is happening…

The diff is that your Macbook and Raspberry Pi have MAC addresses different than your Windows/Linux machine, so when they connect the DHCP server will <know> that those devices haven’t been issued an address before (remember, when you multi-boot, by default both Windows and openSUSE are using the same hardware NIC so the DHCP server will not think they’re different machines). Because your Macbook and RPi are “obviously” different and the DHCP server <knows> that each device hadn’t been issued a lease before, the DHCP server is perfectly willing to terminate the Windows/openSUSE lease to be able to grant a new lease to the Macbook or RPi.

I didn’t mention before, but it’s essential you should know that for most devices the manufacturer of network cards burn a guaranteed unique permanent MAC address into every card. The RPi is an exception, it will generate a new MAC address with every connection. But, for every other device (laptop, workstation, server, router, phone, appliance, etc) that address is fixed by default, but can be masked (through software present a different MAC address). This is the problem when you multi-boot… Although practically each OS in a multi-boot should be considered a very different machine, because they are using the same MAC address they can <appear> to be the same machine on the network to anything that identifies based on that MAC address.

TSU

18

OK, I understand. But the point is I connected both the laptop and the Raspberry Pi at the same time, and watched the network assign IP addresses to both, at the same time (I disabled wifi on the laptop to make sure it was assigning it over ethernet). So if my network can support more IPs, I still don’t understand why it can’t assign one to SUSE, even when I spoof the MAC address, which I just tried. I know you said my ISP needs to fix the network, but I’m not optimistic about the help their tech support is going to give me, especially when I can’t really articulate the problem.

19

I would try to disable DHCP and configure the interface manually (in YaST->System->Network Services) with the values shown by Windows.
I.e. IPv4 address 192.168.0.11, Subnet Mask 255.255.255.0, Default Gateway 192.168.0.1, DNS Servers 194.168.4.100 and 194.168.8.100.

Should show at least whether the problem is really related to DHCP, as you suggested yourself in a previous post…

Or did you try that already meanwhile?

I do seem to remember that some people had problems with the r8169 kernel module in the past.
If the problem is actually at the driver level, it will affect DHCP too of course so may explain why you don’t get any IP address assigned.

20

So I just tried this, and it still fails, but it fails differently.

If I try to use DHCP, or configure the network statically using the Windows settings, with the IP 192.168.0.11, finding web pages instantly fails and if I ping 8.8.8.8, I instantly get ‘Network is unreachable’ and the prompt comes back.

If I configure a static IP that’s different, e.g. 192.168.0.31, finding web pages takes much longer to fail, and when I ping, it repeatedly tries like it’s supposed to, and I have to quit the process myself, except that it still says Destination Host Unreachable for each packet.

Maybe the distinction isn’t important but I thought I’d describe it in case it is.

tl;dr: neither DHCP nor static addresses work, unless I’m configuring the static address wrong. :frowning:

If there’s something wrong with the driver, is there anything I can do to check or fix it?