[GH-ISSUE #3491] Connecting smart TV to Netbird (with a router device?) #7347

Open
opened 2026-08-05 01:12:35 -04:00 by saavagebueno · 5 comments
Owner

Originally created by @iamarealperson1 on GitHub (Mar 12, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3491

Originally assigned to: @nazarewk on GitHub.

I would like to connect to a remote media server from my home network. The remote server is running Netbird and is configured already.

There is no Netbird app for my Smart TV. So I need to get the TV to access the remote media server via an intermediary device in my home network (the thin client).

I have installed Netbrid on the thin client but couldn't figure out how to route requests to my Netbird domain/network to it from other devices like my TV.

Can someone point me to the documentation/concepts I need to learn in order to do this?

Thanks

Originally created by @iamarealperson1 on GitHub (Mar 12, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3491 Originally assigned to: @nazarewk on GitHub. I would like to connect to a remote media server from my home network. The remote server is running Netbird and is configured already. There is no Netbird app for my Smart TV. So I need to get the TV to access the remote media server via an intermediary device in my home network (the thin client). I have installed Netbrid on the thin client but couldn't figure out how to route requests to my Netbird domain/network to it from other devices like my TV. Can someone point me to the documentation/concepts I need to learn in order to do this? Thanks
Author
Owner

@nazarewk commented on GitHub (Mar 13, 2025):

Ideally you would have your own (probably OpenWRT based) primary routing device for home network, install Netbird client on it and you should be all set as long as:

  1. the router's firewall allows forwarding to wt0 interface,
  2. the router sets up DNS server which could plug in to Netbird's DNS proxy to call it before other DNS servers,

You should be able to replicate this by configuring your "thin client" device and plugging in the TV directly into it over LAN to act as a router.

If you never configured a router here is a short list of mechanisms involved:

  • DHCP server running on internal interface:
    • to hand out addresses to clients
    • inform them about the default route (how to reach anything not configured explicitly), usually through itself,
    • inform them about the default nameservers (DNS) also usually through itself,
  • firewall configured to do NAT (translation between internal ip address space to a single external IP address),
  • ip forwarding (firewall + kernel feature) enabled to allow packets to travel between internal and external (internet or router facing) interfaces
  • local DNS server (usually dnsmasq) forwarding queries to either Netbird or upstream
<!-- gh-comment-id:2720515160 --> @nazarewk commented on GitHub (Mar 13, 2025): Ideally you would have your own (probably OpenWRT based) primary routing device for home network, install Netbird client on it and you should be all set as long as: 1. the router's firewall allows forwarding to `wt0` interface, 2. the router sets up DNS server which could plug in to Netbird's DNS proxy to call it before other DNS servers, You should be able to replicate this by configuring your "thin client" device and plugging in the TV directly into it over LAN to act as a router. If you never configured a router here is a short list of mechanisms involved: - DHCP server running on internal interface: - to hand out addresses to clients - inform them about the default route (how to reach anything not configured explicitly), usually through itself, - inform them about the default nameservers (DNS) also usually through itself, - firewall configured to do NAT (translation between internal ip address space to a single external IP address), - ip forwarding (firewall + kernel feature) enabled to allow packets to travel between internal and external (internet or router facing) interfaces - local DNS server (usually dnsmasq) forwarding queries to either Netbird or upstream
Author
Owner

@iamarealperson1 commented on GitHub (Mar 13, 2025):

Thank you @nazarewk. Unfortunately I am stuck with my ISP router for this but I am going to look into configuring IP tables on the thin client.

Based on my understanding, I plan to:

  1. Set up iptables on the thin client following a guide like this: https://syslogine.cloud/docs/os/debian/networking-and-security/nat-configuration/
  2. Set the default gateway on my TV to the IP address of the thin client

Is that all there is to it?

I have verified that the thin client connects successfully to my netbird network. DNS routing is done via the same thinclient that is running pihole. I don't anticpate any changes required to my DNS set up?

<!-- gh-comment-id:2722422319 --> @iamarealperson1 commented on GitHub (Mar 13, 2025): Thank you @nazarewk. Unfortunately I am stuck with my ISP router for this but I am going to look into configuring IP tables on the thin client. Based on my understanding, I plan to: 1. Set up iptables on the thin client following a guide like this: https://syslogine.cloud/docs/os/debian/networking-and-security/nat-configuration/ 2. Set the default gateway on my TV to the IP address of the thin client Is that all there is to it? I have verified that the thin client connects successfully to my netbird network. DNS routing is done via the same thinclient that is running pihole. I don't anticpate any changes required to my DNS set up?
Author
Owner

@nazarewk commented on GitHub (Mar 14, 2025):

I would generally advise to set up the thin client as a complete router, but configuring the TV statically should work too with some care:

  • The default gateway set to the thin client will make the IP address space accessible from the TV, but won't resolve any names just yet,
  • The DNS/Nameserver set to the thin client's IP will allow you to resolve names over Netbird, then either:
    • create a global Nameserver entry in Netbird and assign it to the thin client (this might not be ideal)
    • spin up a DNS resolver pointed both to upstream DNS (like google or cloudflare) and to Netbird's proxy

You can tell Netbird DNS proxy to listen on a specific (externally accessible or just to make it predictable) address with NB_DNS_RESOLVER_ADDRESS=<your-thin-client-ip>:53 on the Netbird daemon.

Some of the DNS resolver examples are: dnsmasq, PiHole, unbound, knot-resolver (aka kresd), Technitium, CoreDNS

<!-- gh-comment-id:2723888485 --> @nazarewk commented on GitHub (Mar 14, 2025): I would generally advise to set up the thin client as a complete router, but configuring the TV statically should work too with some care: - The default gateway set to the thin client will make the IP address space accessible from the TV, but won't resolve any names just yet, - The DNS/Nameserver set to the thin client's IP will allow you to resolve names over Netbird, then either: - create a global Nameserver entry in Netbird and assign it to the thin client (this might not be ideal) - spin up a DNS resolver pointed both to upstream DNS (like google or cloudflare) and to Netbird's proxy You can tell Netbird DNS proxy to listen on a specific (externally accessible or just to make it predictable) address with `NB_DNS_RESOLVER_ADDRESS=<your-thin-client-ip>:53` on the Netbird daemon. Some of the DNS resolver examples are: dnsmasq, PiHole, unbound, knot-resolver (aka kresd), Technitium, CoreDNS
Author
Owner

@ez1976 commented on GitHub (Mar 14, 2025):

i have the same issue exactly (watching a local TV from another country).
since i have my computer on with netbird agent connected all the time, i just published the remote network on my computer.

and on the TV i changed the default Gateway to my computer's IP.
so it is routing everything through it but also to the remote network.

<!-- gh-comment-id:2724410182 --> @ez1976 commented on GitHub (Mar 14, 2025): i have the same issue exactly (watching a local TV from another country). since i have my computer on with netbird agent connected all the time, i just published the remote network on my computer. and on the TV i changed the default Gateway to my computer's IP. so it is routing everything through it but also to the remote network.
Author
Owner

@iamarealperson1 commented on GitHub (Mar 14, 2025):

Thank you both, I will give these options a try soon.
@ez1976 this certainly seems easier. Do you have any docs / references on "publishing the remote network"? I am using Debian on the thin client.

<!-- gh-comment-id:2724423041 --> @iamarealperson1 commented on GitHub (Mar 14, 2025): Thank you both, I will give these options a try soon. @ez1976 this certainly seems easier. Do you have any docs / references on "publishing the remote network"? I am using Debian on the thin client.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7347