Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-VLAN Page #76

Open
LordNex opened this issue May 15, 2022 · 2 comments
Open

Multi-VLAN Page #76

LordNex opened this issue May 15, 2022 · 2 comments

Comments

@LordNex
Copy link

LordNex commented May 15, 2022

Any chance of creating a page with multiple NIC selections? Many of us use segmented networks where HA has a connection to each and thus has several IP addresses depending on what VLAN that nic is connected too

@Holewijn
Copy link
Contributor

A page dedicated to only VLANs or and edit of a blueprint?

@LordNex
Copy link
Author

LordNex commented Jul 1, 2022

Either or both would work. I have 4 NICs my Home Assistant server is using. One for each vlan it need to cover.

@LordNex
Copy link
Author

LordNex commented Nov 26, 2023

It would be nice to have a dashboard that can enumerate and monitor each VLAN and show what data isntransdered via which adapter. Although there is an issue with the default subnet which I have a ticket out for.

@OutOfThisPlanet
Copy link

OutOfThisPlanet commented Dec 8, 2023

I have 6 different networks which my HA is attached to.
Each on a different VLAN.

VLAN tagging support would be great, however I work around that with Proxmox.
Proxmox is VLAN aware (both at the bridge and interface level), however if I were to host HA on a PI, VLAN Tagging would not be an option.

Being able to set the default interface is the most important thing I want!!

This workaround is good, but I shouldn't have to do this:

image

@LordNex
Copy link
Author

LordNex commented Dec 9, 2023

I have 6 different networks which my HA is attached to.

Each on a different VLAN.

VLAN tagging support would be great, however I work around that with Proxmox.

Proxmox is VLAN aware (both at the bridge and interface level), however if I were to host HA on a PI, VLAN Tagging would not be an option.

Being able to set the default interface is the most important thing I want!!

This workaround is good, but I shouldn't have to do this:

image

Luckily VMWare ESXi is also VLAN aware. You build a vSwitch and tie it to the LACP tagged group coming off your server if it's multi homed. I'm running off a Dell PowerEdge R620 with 4 Intel gigabit adapters LACP/LAG'd together. But I'm still having issues trying to keep the adapter I want as the primary interface. Although the trusted networks addition has seemed to help at least keeping my phones and tablets running internal instead of dropping out to Nabu.casa. I just wish Starlink would provide a public IPv4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants