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!
view the rest of the comments
If you want to keep it wired then you'll need to put it on a separate VLAN from your other devices. A VLAN effectively allows you to create separate ethernet networks over the same physical network. We use them at work to keep factory hardware separate from office hardware and I use them at home to keep a vpn open for streaming geolocked content from another country. Traffic between the two VLANs has to be routed just like it would if they were separate physical networks.
I have an Edgerouter POE which has a small built in switch and supports VLANs so I can easily dedicate a port on the switch to a particular VLAN. In my case I route that traffic through wireguard, but in your case all you really need is setting up NAT for internet access and not route it with your other VLAN.
Any commercial grade routers support VLANs, i've seen it on unifi, aruba and fortigate and have never heard of it not being supported.
As others have pointed out, if you have a switch between your TV and Router then that'll need to be a managed switch that can trunk the vlan code back to the router, otherwise all the traffic will be comingled.
Other thoughts:
You might be able to arrange your IPs to sort of fake it. If your router is 192.168.1.1 and you make the TV be 192.168.1.2. Then you could give your TV a static IP configuration and tell it that it's subnet mask is 255.255.255.252. Then it'd only consider the IPs 192.168.1.1-192.168.1.2 as being in it's local network and if it tries to access something else on the LAN then it'll send it to the router for forwarding.
I'm not sure what your router would do in that situation, but it seems unlikely it'd manage to forward that packet. You'd have to avoid putting any device on 192.168.1.3 (as that'd be the routers broadcast address) but I think you could probably make that work. It's not really secure (as anyone that compromises the TV could change the subnet) and it'd still be possible for devices on your network to send UDP packets (but not get replies from) the TV. It's also not really extendable and you probably can't get a second TV to work like that (and definitely not three), but it wouldn't require switching to commercial routers.
Thank you so much. I think i'll have to buy a switch. I have a shitty iinet tgvac789 V2 router which I think is useless.
The switch on its own will do nothing for you. It's only useful with a router that supports VLANs
Unfortunately in your situation you'll need to replace your current router-modem combo with a dedicated modem, a commercial router (if you don't want to build your own linux one then EdgeRouters seems pretty good value for money) and a managed switch.
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.
Can you enable multiple vlans?
I only see one VLAN option but then I also found this