[SOLVED] All network interfaces down and no internet after reboot

mon0

New Member
Dec 16, 2023
13
1
3
Howdy folks. I was doing some cable rerouting with my network and had to bring my server down, and took the opportunity to upgrade my HL15 to the Noctua kit since I've had it for a while. After rebooting I noticed that I wasn’t able to access my web GUI, so I plugged a keyboard and monitor in and saw that every network interface was down.

I found some others threads saying that the interface set for the bridge can get jacked up when adding PCI devices (the only thing I "added" since it was last working was a fan controller to FAN2 header on my board), so I had some back and forth with GPT, reconfigured my network interface to the interface that appears to be up, but I’m still getting nothing. I’m an absolute loss and really want to get my server back up, so if anyone has any tips or advice that I can follow, I’d appreciate it. My UniFi is reporting a connection, the physical link light indicators are lit on both ends, but still no internet.

Last photo may be unrelated, but I noticed these failures right before boot. I've tried booting into different kernel versions, etc but nothing. I'd be really surprised if just adding a fan controller would have caused this, but what do I know :D
 

Attachments

  • 1752292619724.jpeg
    1752292619724.jpeg
    492.5 KB · Views: 7
  • 1752292642708.jpeg
    1752292642708.jpeg
    357.7 KB · Views: 6
  • 1752292728772.jpeg
    1752292728772.jpeg
    389.6 KB · Views: 6
  • 1752292752204.jpeg
    1752292752204.jpeg
    353.5 KB · Views: 6
  • 1752292759958.jpeg
    1752292759958.jpeg
    308.3 KB · Views: 6
Last edited:
Interestingly all my VMs and LXCs are reporting to my Dream Machine, so it's clearly connected, yet I can't ping it at 192.168.20.12, can't access the web interface or any of these services, and all the .1s were previously on a .20 VLAN and now are not. Something is clearly goofy in my config, but I just can't figure out what1752293015449.png
 
Disregard, I'm stupid. It was the port not having the correct VLAN tag causing issues with ARP