-
Notifications
You must be signed in to change notification settings - Fork 162
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
Comments
A page dedicated to only VLANs or and edit of a blueprint? |
Either or both would work. I have 4 NICs my Home Assistant server is using. One for each vlan it need to cover. |
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. |
I have 6 different networks which my HA is attached to. VLAN tagging support would be great, however I work around that with Proxmox. 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: |
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 |
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
The text was updated successfully, but these errors were encountered: