Every couple of boots or so, I am unable to get any DNS Requests via IPv4 to work, and networking stalls until it tries ipv6. If trying to use my routers DNS server, it will just respond with “REFUSED”, and if trying any other DNS Server, it will time out. This only happens on this machine, and not under Windows or on other machines. Any ideas what could be going on here?
Have you contacted your ISP about this?
Wheree are you located? I cannot make up from the scrsh.
Is this before you enter EndeavourOS and does it boot normally?
Are you using a native VPN app? which one?
(native= in linux code)
Edit 1: f this is your router’s…I’m not doubting you capabilities man but…sometimes it’s not all wish granting with open source.
So… I’m using my Router’s DNS server only because I Have a ubiquity router and i have configured DNS over TLS via Unifi and I also have local dns entries I have setup through the Unifi dashboard. This issue does not occur on any other system in my house (wired or wifi, windows or mac or ios or android, etc)
also I’m not using a vpn…
As I also stated and shown in the screenshot, this issue causes any IPv4 dns lookup even when changing my dns servers in network management to be anything else.
And Im already booted into endeavour… im on my kde desktop for the screenshot…
It’s also very intermittent, only happening every few boots or so
wired or wifi, windows or mac or ios or android, etc
yes, but these are all bitches.
also I’m not using a vpn…
As I also stated and shown in the screenshot, this issue causes any IPv4 dns lookup even when changing my dns servers in network management to be anything else.
And Im already booted into endeavour… im on my kde desktop for the screenshot…
Yes yes, idd kde and Qt imo are going like really beyond in CXX…they know shit. and you think this was obvious from your screenshot…yeah no not for me, sorry friend.
“t’s also very intermittent, only happening every few boots or so.”
Nice…so people smarter than me still got yout sht online in ipv6. awrsome.
Edit: I get you’re kinda bitchy for your superboss network skills not taking ground but is this all?
Edit 2: I really mean boss and also I really mean I’m just an ahole not affiliated with the true guys at endeavour but I think what you’rte asking really is difficult dude. like 9.9 at google…what ya playin at?
If rebooting is getting this to work…aces man, aces.
What do you have in /etc/resolv.conf when DNS is down?
Can you ping your router when it is down?
1 Like
as DNS is currently working, I don’t know whats in resolv.conf when it is down, but when it is down, I can ping my router fine
How is the device connected to the network (wired or wireless)? Post inxi -nz in to the thread, maybe we will spot a clue.
Is the Windows installation on the same machine? (https://www.minitool.com/news/fast-startup-windows-10-018.html)
What’s in there when it’s up?
Are you using NetworkManager, or systemd-resolved? Check what is running if you are not sure:
systemctl status NetworkManager
systemctl status systemd-resolved
Here is inxi -nz (Ignore Device-2, im assuming thats my WiGig adapter for my Vive that I can’t use on linux anyways)
[roberth@EVA-01 ~]$ inxi -nz
Network:
Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi
IF: wlan0 state: down mac: <filter>
Device-2: Intel driver: N/A
Device-3: Intel Ethernet I225-V driver: igc
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
[roberth@EVA-01 ~]$
and the Windows install is on the same machine, dual booting
here is resolv.conf right now (in working state) (this is the correct dns servers that are supposed to be served via dhcp for my network, I have windows ad setup for my windows systems)
# Generated by NetworkManager
search ad.azuresucks.net
nameserver 10.0.0.1
nameserver 10.0.0.225
nameserver 2600:6c40:7a00:10ad::1
When checking the networking applet in kde when the dns wasn’t working, the dns servers in there were correct as well, and even after manually adding dns servers in networkmanager (the 9.9.9.9) It was still not working…
and NetworkManager is active, systemd-resolved is disabled
Can you ping an external site by IP when the DNS is down, for example ping 9.9.9.9?
Don’t forget to check this:
Windows can interfere with the network card when it is supposedly “off” unless you disable this “feature”.
And i can ping outside fine iirc (i think i tried pining 8.8.8.8)
Ill check the fast startup thing in windows real quick… it wouldn’t surprise me if that is it… (iirc it happened right after rebooting from winblows…)
Hibernation is not even available for my machine in windows, but still went and disabled it in registry, booted back into Linux and I have the dns issue again… but it seems like it’s the whole ipv4 stack outside of the network is failing only on this system
Try restarting NetworkManager and see what happens.
sudo systemctl restart NetworkManager
See if there are any clues in the log.
sudo journalctl -b -u NetworkManager
Double-check your external IP address isn’t in any logs you post if you would prefer to keep that confidential.
Here is my journalctl for NetworkManager
Even after restarting NetworkManager, IPv4 Connectivity is still fried, including trying to use Wi-Fi instead
Also unable to connect to my router admin page while in this state, but can access my other local pages fine…
Apr 17 21:12:28 EVA-01 NetworkManager[1658]: <info> [1713406348.8433] manager: NetworkManager state is now CONNECTED_SITE
Apr 17 21:12:28 EVA-01 NetworkManager[1658]: <info> [1713406348.8433] device (enp7s0): Activation: successful, device activated.
Apr 17 21:12:29 EVA-01 NetworkManager[1658]: <info> [1713406349.3634] policy: set 'eth0' (enp7s0) as default for IPv6 routing and DNS
Apr 17 21:12:30 EVA-01 NetworkManager[1658]: <info> [1713406350.4215] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 17 21:14:41 EVA-01 NetworkManager[1658]: <info> [1713406481.0242] audit: op="statistics" interface="enp7s0" ifindex=2 args="2000" pid=2073 uid=1000 result="success"
Apr 17 21:18:49 EVA-01 NetworkManager[1658]: <info> [1713406729.1544] device (wlan0): set-hw-addr: set MAC address to 2E:96:79:85:9F:3A (scanning)
Apr 17 21:18:49 EVA-01 NetworkManager[1658]: <info> [1713406729.1581] device (wlan0): supplicant interface state: disconnected -> inactive
Apr 17 21:18:49 EVA-01 NetworkManager[1658]: <info> [1713406729.1582] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Apr 17 21:23:18 EVA-01 systemd[1]: Stopping Network Manager...
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9551] caught SIGTERM, shutting down normally.
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9554] dhcp4 (enp7s0): canceled DHCP transaction
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9554] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9554] dhcp4 (enp7s0): state changed no lease
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9554] manager: NetworkManager state is now CONNECTED_SITE
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9555] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9739] device (wlan0): set-hw-addr: reset MAC address to 8C:B8:7E:92:43:2F (unmanage)
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9779] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Apr 17 21:23:18 EVA-01 NetworkManager[1658]: <info> [1713406998.9802] exiting (success)
Apr 17 21:23:18 EVA-01 systemd[1]: NetworkManager.service: Deactivated successfully.
Apr 17 21:23:18 EVA-01 systemd[1]: Stopped Network Manager.
Apr 17 21:23:18 EVA-01 systemd[1]: Starting Network Manager...
Apr 17 21:23:18 EVA-01 NetworkManager[4572]: <info> [1713406998.9890] NetworkManager (version 1.46.0-2) is starting... (after a restart, boot:717f16ba-1e18-492e-9d06-9ea209b0adc5)
Apr 17 21:23:18 EVA-01 NetworkManager[4572]: <info> [1713406998.9890] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0171] manager[0x61c38b5cfb90]: monitoring kernel firmware directory '/lib/firmware'.
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0492] hostname: hostname: using hostnamed
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0492] hostname: static hostname changed from (none) to "EVA-01"
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0493] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0496] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill1) (driver iwlwifi)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0497] manager[0x61c38b5cfb90]: rfkill: Wi-Fi hardware radio set enabled
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0497] manager[0x61c38b5cfb90]: rfkill: WWAN hardware radio set enabled
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0502] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-adsl.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0507] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0508] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-ovs.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0539] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-team.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0540] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wifi.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0540] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wwan.so)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0541] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0541] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0541] manager: Networking is enabled by state file
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0542] settings: Loaded settings plugin: keyfile (internal)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0549] dhcp: init: Using DHCP client 'internal'
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0549] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0550] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0551] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0553] device (lo): Activation: starting connection 'lo' (89d59c7e-33fc-4656-9531-11b356951377)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0556] device (enp7s0): carrier: link connected
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0557] manager: (enp7s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0558] manager: (enp7s0): assume: will attempt to assume matching connection 'eth0' (ab1370c8-038c-48c7-ae03-ce5f534406f9) (indicated)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0558] device (enp7s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0560] device (enp7s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0563] device (enp7s0): Activation: starting connection 'eth0' (ab1370c8-038c-48c7-ae03-ce5f534406f9)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0565] manager: (virbr1): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0567] device (virbr1): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0568] device (virbr1): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0570] device (virbr1): Activation: starting connection 'virbr1' (16db0747-51f7-47eb-bd30-ef3e1c41d067)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0571] device (wlan0): driver supports Access Point (AP) mode
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0572] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0573] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.0875] device (wlan0): set-hw-addr: set MAC address to 76:64:45:44:BD:E7 (scanning)
Apr 17 21:23:19 EVA-01 systemd[1]: Started Network Manager.
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3443] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3449] ovsdb: disconnected from ovsdb
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3449] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3451] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3452] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3452] device (enp7s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3454] device (enp7s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3455] device (virbr1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3456] device (virbr1): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3457] device (virbr1): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3459] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3460] device (virbr1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3463] device (enp7s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3464] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3466] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3466] device (virbr1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3467] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3468] device (lo): Activation: successful, device activated.
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3469] device (virbr1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3470] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3470] device (virbr1): Activation: successful, device activated.
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3540] dhcp4 (enp7s0): state changed new lease, address=10.0.0.69, acd pending
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3543] dhcp4 (enp7s0): state changed new lease, address=10.0.0.69
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3544] policy: set 'eth0' (enp7s0) as default for IPv4 routing and DNS
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3575] device (enp7s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3580] device (enp7s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3581] device (enp7s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3582] manager: NetworkManager state is now CONNECTED_SITE
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3583] device (enp7s0): Activation: successful, device activated.
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3711] device (wlan0): supplicant interface state: internal-starting -> disconnected
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3711] Wi-Fi P2P device controlled by interface wlan0 created
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3712] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3713] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3714] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.3715] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.4140] agent-manager: agent[906253625e504340,:1.41/org.kde.plasma.networkmanagement/1000]: agent registered
Apr 17 21:23:19 EVA-01 NetworkManager[4572]: <info> [1713406999.5400] policy: set 'eth0' (enp7s0) as default for IPv6 routing and DNS
Apr 17 21:23:22 EVA-01 NetworkManager[4572]: <info> [1713407002.3420] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 17 21:23:22 EVA-01 NetworkManager[4572]: <info> [1713407002.6691] manager: startup complete
lines 154-202/202 (END)
It looks like you are not getting a DHCP lease, and the connection is restarting over and over.
Try disabling mac address randomization and see if it makes any difference. https://wiki.archlinux.org/title/NetworkManager#Configuring_MAC_address_randomization
Another thing you can try is switching to the LTS kernel to test if the issue happens there. If the LTS kernel works fine, you are probably up against a kernel bug.
sudo pacman -S linux-lts linux-lts-headers
You should be able to choose the new kernel at boot time in the menu for whatever bootloader you are using.
Ill try shoving this into a Networkmanager/conf.d file and see if this works…
[device]
wifi.scan-rand-mac-address=no
[connection-mac-randomization]
# dont Randomize MAC for every ethernet connection
ethernet.cloned-mac-address=stable
Very few ISP’s around the world support DNS over TLS. There is a greater possibility of blocking 853 port.
Hence choose quad. Net like Swiss based dns.
9.9.9.9 (us&switzerland)or 9.9.9.11(only in Switzerland)
VPN connection will not work when 853 port for dns is in use, because many VPN providers are not supporting dns over TLS
Also check your arch Linux configuration. Enable systemd relevant controls
Dns works fine on every other device on the network with same settings. Also, I’m not using a vpn…
I have noticed that my router thinks this pc has an ip of 10.0.0.100 instead of the 10.0.0.69 it is stating I have on the pc itself… maybe the MAC address randomization isn’t turned off properly or something else is happening
That certainly explains the issue you are having. Though it seems kind of odd that NetworkManager is not just accepting whatever IP address is offered to it by the DHCP server. You haven’t configured a static IP on the device or anything, have you?
What IP address do you get in Windows? 10.0.0.100, or something else?
I reserved a DHCP Lease of 10.0.0.69 on my dhcp server for this system, so the fact that I get that ip address on my system, then it disconnects and then the router thinks its a different system means that mac randomization isnt actually disabled. I just set it static on my systems end and made the “cloned mac address” the physical mac address.
works no issue now, but would prefer to use dhcp again…
Honestly, I wish i could just completely disable mac address randomization for the whole kernel, but dont want to deal with the patches for that…
could also be getting screwed up cause i mount an nfs drive over the network using fstab, and the mac gets changed after login or something causing a conflict?
(Windows gives me the 10.0.0.69 address like its supposed to from reserved dhcp pool)