I’m having trouble picking dynamic IP address on my LAN network at the office. Below iis what I have, please let me know what else I can share. Also, how can I detect that I am picking an APIPA (169.254.x.x)
STARTMODE {manual*|auto|nfsroot|hotplug|off}
Choose when the interface should be set up.
manual
Interface will be set up if ifup is called manually
auto
Interface will be set up as soon as it is available (and service network was started). This either
happens at boot time when network is starting or via hotplug when a interface is added to the system
(by adding a device or loading a driver). To be backward compliant onboot, on and boot are aliases for
auto.
hotplug
Interface will be activated when it is available. Use instead of auto for devices which may be missed,
such as bonding slaves, usb or other plugable hardware.
nfsroot
Nearly like auto, but interfaces with this startmode will be not shut down by default. Use this mode
when you use a root filesystem via network or want to avoid interface shutdown. To force a nfsroot
interface down, use either wicked ifdown --force device-down <interface> or ifdown <inter-
face> -o force.
off
Will never be activated.
Note: Hotplugging is available only when wickedd-nanny is enabled.
See wicked-config(5) for instructions how to enable it.
Without nanny, an ifup call preforms a one-shot setup.
Hmmm…I was hoping that the ifdown/ifup sequence would get you a working connection (as described in the bug report). You could try switching to NetworkManager via YaST > System > Network Settings, change to NetworkManager. Once complete, you should be able to configure via the KDE (or Gnome) NM front-ends.
Unless you’ve been fiddling with ifplugd,
IMO you shouldn’t assume your problem is related to it.
Only things on your machine which should be relevant are
Your interface configuration specifies “BOOTPROTO=“dhcp”” which is the case in your first post.
Your interface is active.
You should run the following to inspect your working network configuration (or “ifconfig” but that is deprecated)
ip addr
That should tell you whether the interface is up, and whether you’re configured with a link-local address(aka self-assigned when not configured) or something else.
You should also consider that you’re connecting to a part of your network which might be blocking DHCP.
If you have another device which can attach using the same network connection (looks like a wired cable in your case), try that.
Maybe even replace your patch cable.
And, of course always look at your network connectivity LED lights on both ends of the patch cable.
I found out the problem is actually with the ports I was connected to. I tried 2 different ports and concluded the problem was with my laptop. Thanks for all your help!