view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I believe that's the VLAN for the WAN, basically you only need to enable that if your ISP is using VLANs, but you want to enable VLANs on your LAN. I have the Telstra version of that modem (I recognise the Technicolor UI) and it doesn't allow you to use VLANs like you want to.
You could probably set up some routing stuff on a raspberry pi though, and use a switch.
Or if needed put your modem into bridge mode, and acquire a router that supports VLANs, I don't know of any cheap consumer ones, but I'm in the process of switching to OPNsense with an old computer. Unrelated, but in my experience technicolor has severe bufferbloat anyway.
Yeah that makes sense. I can't see why there would be a vlan enabled on your local network right now as it would make lots of things not work
I just read some more of your comments and thought I might properly explain VLANs:
VLANs let you create a whole virtual network within your physical network, there can be upto 4096 of them that can be tagged and 1 untagged per port, the VLAN ID defines which one to use.
A tagged VLAN is often used between routers and switches, so the connected device can pick which VLAN to use, but an untagged VLAN dedicates that port to that VLAN making it appear to the connected device as if it's the physical network.
Since it's a whole new network you need some sort of router to route between them.
As a rough example you could have something like: Router --2T--> Switch --2U--> TV, where the T is for tagged and U for untagged. Or replace Router with Pi if you use that, the Pi will access the internet with the (technically untagged) physical network, and route between tagged VLAN 2, meaning you can do everything on the Pi with 1 ethernet port.
Disclaimer: Most of this was learnt from experience so it might not be completely correct.