r/HomeNetworking • • 7h ago

PC Only Available on Network through Unmanaged Switch

Odd issue...but I am guessing this has a simple solution.

I setup a Home Assistant PC and got it working on my desk connected to an unmanaged switch I keep on my desk. I can connect to it from a wired connection sharing the same switch as well as the overall WAN. I gave it a static IP, and blocked internet access.

I plan on installing the PC in my attic, where I have a direct connection to a port on my managed router (ASUS EBG19P). The port is setup same as all of the other wired ports...and it often shows up on my routers admin page...but I cannot ping it or access the home assistant home page.

Any help would be appreciated! Thanks

2 Upvotes

19 comments sorted by

7

u/AnxiousReward1715 7h ago

how exactly did you "block internet access"?

2

u/ImtheDude27 7h ago

My thoughts exactly. Going to need a LOT more detail to have even half a clue on what's preventing access.

Blocking internet access is also going to cause other problems, like updates and certain integrations depending on what hardware/switches/devices are connected to the HA instance.

1

u/Infiltrait0rN7_ 6h ago

Will try to describe things best i can... I'm an engineer...but networking is seriously painful to my brain. πŸ˜„

You're right about updates...and I may unblock it as I get comfortable with the software. Just proceeding with caution after a ransomware attack on my NAS a few years ago.

1

u/PropertyCorrect99 7h ago

your static ip probably has gateway set to the switch or something that dont exist when you move it to attic. try set gateway to router ip or leave it blank if you not need internet at all

also check if the attic port is in same vlan as your desk, managed routers sometimes have ports in different vlans out of box

1

u/Infiltrait0rN7_ 6h ago

Gateway is set to the router IP, oddly the DNS Server is also set itself to the same IP.

The switch was unmanaged, so it shouldn't have had a IP Address, correct?

The Attic port is in the same VLAN as my desk. I only have 1 wired VLAN and that is isolated to a different port on the router.

1

u/Infiltrait0rN7_ 7h ago

It’s a toggle in the routers settings.

1

u/AnxiousReward1715 6h ago

Oh dear lord, found the manual... thats a very unique way that Asus is handling things... did you set the static IP from the router too? guessing you did....

1

u/Infiltrait0rN7_ 6h ago edited 6h ago

Yes, I did.

Although in at least two cases unrelated to this fun issue - I think i set it only on one device, and it didn't seem to freak out.

1

u/AnxiousReward1715 6h ago

Ya.... Don't do that, use a dhcp reservation and static it on the I'm assuming Windows 11 box?

1

u/Infiltrait0rN7_ 6h ago

Yep, understood - The router has a static IP tied to the Mac Address...and the Home Assistant PC is also configured to use the same IP Address.

Its running Home Assistant OS - old Windows 10 mini PC.

1

u/AnxiousReward1715 6h ago

So its a VM sitting on a windows 10 install or generic x86/64 install? and I understand, the static IP thing. don't do that. Do a dhcp reservation if you feel like it, its cleaner.... but either are wildly unnecessary for a home environment....

1

u/Infiltrait0rN7_ 6h ago

Its a generic x86/64 install. Went through with ubuntu to boot...then then HAOS.

Thanks for the tip on the static IP thing

1

u/AnxiousReward1715 6h ago

Not sure how you expect it to work without DNS..... but like you do you boo. Local only is a thing I suppose...

1

u/Infiltrait0rN7_ 6h ago

Wait - little confused where your 'without DNS' comment came from.

HAOS looks like it defaulted the DNS to the router IP address.

→ More replies (0)

1

u/Infiltrait0rN7_ 6h ago

I moved the HA PC to another unmanaged switch on my network which connects to another port on the router (same VLAN). Works just fine, same as on my desk.

1

u/International_Sky526 54m ago

small correction, an unmanaged switch has no ip address of its own, so the static ip belongs to the pc. it showing up on the router admin page means layer 2 is working, wich points at the ip config (subnet mask or gateway) rather than the cable or port.