21 minutes ago, cheesysenator said:

hat does the wireguard tunnel on my PC have to do with unraid being unable to reach the DHCP server?

you do not have a LAN at all. All your connection is handled over the tunnel.

Your IP address is 162.81.*  which belongs to the "Knoxville Utility Board" (whatever this is). But your DHCP Server is 10.10.10.1 which is a private address and cannot be reached from the 162.81.* net. (normally)

So there must be some tricks nobody can guess how to manage this.

You should call the support of your provider and ask how to setup a linux machine.

 

if the data is still correct, contact

OrgTechHandle: ROLLI132-ARIN
OrgTechName:   Rollings, Allen
OrgTechPhone:  +1-865-558-2026
OrgTechEmail:  [email protected]

 

 

It looks to me as if you do not have a DHCP Server, but use a "DHCP Relay" or something...

very strange, never saw a setup like this in the real world before...

Edited December 29, 20241 yr by MAM59

The Idea Veeah had (and deleted again, why?) also came into my mind.

What you have is not a classic router, but a kind of tunneling modem. You have no NAT there, very uncommon today.

And it MAY happen, that your provider only allows a certain amount (usually ONE) of devices behind the modem.

So it MAY be that you need to buy your own NAT router and hook it up the line. This will serve as the internet gateway for many LAN devices.

 

So better check your contract and see, what you have ordered.

 

On 12/29/2024 at 6:50 AM, MAM59 said:

The Idea Veeah had (and deleted again, why?) also came into my mind.

What you have is not a classic router, but a kind of tunneling modem. You have no NAT there, very uncommon today.

And it MAY happen, that your provider only allows a certain amount (usually ONE) of devices behind the modem.

So it MAY be that you need to buy your own NAT router and hook it up the line. This will serve as the internet gateway for many LAN devices.

 

So better check your contract and see, what you have ordered.

 

After some total reconfiguration of my home network, adding an additional router and routing ethernet wires through it, the problem is fixed. The fiber modem seems to only want to have one device immediately attached to it, and got confused when a switch was attached to it. Seems like the fiber install guy should have known something about that, considering he plugged a switch into the fiber modem, but, whatever. Now the DHCP server is accessible.