SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-14 04:01:55 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

[BUG] We need another DNS approach for [Synology] systems. #890

New Issue
Open
opened 2025-11-20 05:19:22 -05:00 by saavagebueno · 17 comments
saavagebueno commented 2025-11-20 05:19:22 -05:00
Owner
Copy Link

Originally created by @zzecool on GitHub (May 14, 2024).

In Synology the current DNS implementation fails like this if you have a DNS running localy :

The local DNS is listening in all available addresses for that we need a DNS that will listen in a different port but not with the current implementation as it is not supported.

sudo netstat -tuln | grep -w ':53'

tcp6       0      0 :::53                   :::*                    LISTEN     
udp6       0      0 :::53                   :::*   


2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 100.115.6.17:53 is not available, error: listen udp 100.115.6.17:53: bind: address already in use
2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 127.0.0.1:53 is not available, error: listen udp 127.0.0.1:53: bind: address already in use
2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 127.0.0.153:53 is not available, error: listen udp 127.0.0.153:53: bind: address already in use
2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:215: failed to load DNS forwarder eBPF program, error: field NbXdpProg: program nb_xdp_prog: map .rodata: map create: read- and write-only maps not supported (requires >= v5.2)
2024-05-13T23:20:38+03:00 WARN client/internal/dns/server.go:316: the DNS manager of this peer doesn't support custom port. Disabling primary DNS setup. Learn more at: https://docs.netbird.io/how-to/manage-dns-in-your-network#local-resolver
2024-05-13T23:20:38+03:00 ERRO client/internal/dns/server.go:322: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured

You guys are active, so we are very close to make Netbird fully supported in Synology.

Originally created by @zzecool on GitHub (May 14, 2024). In Synology the current DNS implementation fails like this if you have a DNS running localy : The local DNS is listening in all available addresses for that we need a DNS that will listen in a different port but not with the current implementation as it is not supported. ``` sudo netstat -tuln | grep -w ':53' tcp6 0 0 :::53 :::* LISTEN udp6 0 0 :::53 :::* ``` ``` 2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 100.115.6.17:53 is not available, error: listen udp 100.115.6.17:53: bind: address already in use 2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 127.0.0.1:53 is not available, error: listen udp 127.0.0.1:53: bind: address already in use 2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:185: binding dns on 127.0.0.153:53 is not available, error: listen udp 127.0.0.153:53: bind: address already in use 2024-05-13T23:20:38+03:00 WARN client/internal/dns/service_listener.go:215: failed to load DNS forwarder eBPF program, error: field NbXdpProg: program nb_xdp_prog: map .rodata: map create: read- and write-only maps not supported (requires >= v5.2) 2024-05-13T23:20:38+03:00 WARN client/internal/dns/server.go:316: the DNS manager of this peer doesn't support custom port. Disabling primary DNS setup. Learn more at: https://docs.netbird.io/how-to/manage-dns-in-your-network#local-resolver 2024-05-13T23:20:38+03:00 ERRO client/internal/dns/server.go:322: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured ``` You guys are active, so we are very close to make Netbird fully supported in Synology.
saavagebueno added the bugclienttriage-neededdnssynology labels 2025-11-20 05:19:23 -05:00
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 14, 2024):

@bcmmbaga Hop in now that you are on fire :P

@zzecool commented on GitHub (May 14, 2024): @bcmmbaga Hop in now that you are on fire :P
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

Hello @zzecool thanks for reporting this issue.

Can you test using user space mode?

If you are on DSM 7.0+ you can do that by using the following commands:

sudo mkdir -p /etc/sysconfig
echo 'NB_WG_KERNEL_DISABLED=true' | sudo tee -a /etc/sysconfig/netbird
sudo systemctl restart netbird
@mlsmaycon commented on GitHub (May 22, 2024): Hello @zzecool thanks for reporting this issue. Can you test using user space mode? If you are on DSM 7.0+ you can do that by using the following commands: ```shell sudo mkdir -p /etc/sysconfig echo 'NB_WG_KERNEL_DISABLED=true' | sudo tee -a /etc/sysconfig/netbird sudo systemctl restart netbird ```
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

sudo mkdir -p /etc/sysconfig
echo 'NB_WG_KERNEL_DISABLED=true' | sudo tee -a /etc/sysconfig/netbird
sudo systemctl restart netbird

@mlsmaycon Yes here you are :

2024-05-22T18:52:59+03:00 INFO client/internal/connect.go:115: starting NetBird client version 0.27.7 on linux/amd64
2024-05-22T18:52:59+03:00 WARN client/system/info_linux.go:115: geucwReleaseInfo: exit status 1
2024-05-22T18:53:00+03:00 WARN client/internal/wgproxy/factory_linux.go:17: failed to initialize ebpf proxy, fallback to user space proxy: field NbXdpProg: program nb_xdp_prog: map .rodata: map create: read- and write-only maps not supported (requires >= v5.2)
2024-05-22T18:53:00+03:00 INFO iface/tun_usp_linux.go:33: using userspace bind mode
2024-05-22T18:53:00+03:00 INFO client/internal/routemanager/manager.go:93: Routing setup complete
2024-05-22T18:53:00+03:00 INFO iface/tun_usp_linux.go:45: create tun interface
2024-05-22T18:53:00+03:00 ERRO client/firewall/iptables/router_linux.go:51: failed to cleanup routing rules: failed to list rules in FORWARD chain: running [/sbin/iptables -t filter -S FORWARD --wait]: exit status 1: iptables: No chain/target/match by that name.

2024-05-22T18:53:00+03:00 ERRO client/firewall/create_linux.go:48: failed to create iptables manager: failed to list rules in FORWARD chain: running [/sbin/iptables -t filter -S FORWARD --wait]: exit status 1: iptables: No chain/target/match by that name.

2024-05-22T18:53:00+03:00 INFO client/internal/dns/host_linux.go:68: System DNS manager discovered: file
2024-05-22T18:53:00+03:00 INFO client/internal/engine.go:359: Network monitor is disabled, not starting
2024-05-22T18:53:00+03:00 INFO client/internal/connect.go:261: Netbird engine started, the IP is: 100.150.200.200/16
2024-05-22T18:53:00+03:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-05-22T18:53:00+03:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-05-22T18:53:00+03:00 WARN client/internal/engine.go:551: running SSH server is not permitted
2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted]
2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf
2024-05-22T18:53:00+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 549.946µs, total rules count: 22
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.1.1.1:53: read udp 10.0.0.50:36965->1.1.1.1:53: i/o timeout
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.0.0.1:53: read udp 10.0.0.50:46327->1.0.0.1:53: i/o timeout
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:265: Upstream resolving i2024-05-22T18:53:00+03:00 INFO client/internal/dns/host_linux.go:68: System DNS manager discovered: file
2024-05-22T18:53:00+03:00 INFO client/internal/engine.go:359: Network monitor is disabled, not starting
2024-05-22T18:53:00+03:00 INFO client/internal/connect.go:261: Netbird engine started, the IP is: 100.150.200.200/16
2024-05-22T18:53:00+03:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-05-22T18:53:00+03:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-05-22T18:53:00+03:00 WARN client/internal/engine.go:551: running SSH server is not permitted
2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted]
2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf
2024-05-22T18:53:00+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 549.946µs, total rules count: 22
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.1.1.1:53: read udp 10.0.0.50:36965->1.1.1.1:53: i/o timeout
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.0.0.1:53: read udp 10.0.0.50:46327->1.0.0.1:53: i/o timeout
2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s
2024-05-22T18:53:02+03:00 INFO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout
2024-05-22T18:53:02+03:00 ERRO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:525: Failed to apply nameserver deactivation on the host: unable to configure DNS for this peer using file manager without a nameserver group with all domains configureds Disabled for 30s
2024-05-22T18:53:02+03:00 INFO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout
2024-05-22T18:53:02+03:00 ERRO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:525: Failed to apply nameserver deactivation on the host: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured
@zzecool commented on GitHub (May 22, 2024): > ```shell > sudo mkdir -p /etc/sysconfig > echo 'NB_WG_KERNEL_DISABLED=true' | sudo tee -a /etc/sysconfig/netbird > sudo systemctl restart netbird > ``` @mlsmaycon Yes here you are : 2024-05-22T18:52:59+03:00 INFO client/internal/connect.go:115: starting NetBird client version 0.27.7 on linux/amd64 2024-05-22T18:52:59+03:00 WARN client/system/info_linux.go:115: geucwReleaseInfo: exit status 1 2024-05-22T18:53:00+03:00 WARN client/internal/wgproxy/factory_linux.go:17: failed to initialize ebpf proxy, fallback to user space proxy: field NbXdpProg: program nb_xdp_prog: map .rodata: map create: read- and write-only maps not supported (requires >= v5.2) 2024-05-22T18:53:00+03:00 INFO iface/tun_usp_linux.go:33: using userspace bind mode 2024-05-22T18:53:00+03:00 INFO client/internal/routemanager/manager.go:93: Routing setup complete 2024-05-22T18:53:00+03:00 INFO iface/tun_usp_linux.go:45: create tun interface 2024-05-22T18:53:00+03:00 ERRO client/firewall/iptables/router_linux.go:51: failed to cleanup routing rules: failed to list rules in FORWARD chain: running [/sbin/iptables -t filter -S FORWARD --wait]: exit status 1: iptables: No chain/target/match by that name. 2024-05-22T18:53:00+03:00 ERRO client/firewall/create_linux.go:48: failed to create iptables manager: failed to list rules in FORWARD chain: running [/sbin/iptables -t filter -S FORWARD --wait]: exit status 1: iptables: No chain/target/match by that name. ``` 2024-05-22T18:53:00+03:00 INFO client/internal/dns/host_linux.go:68: System DNS manager discovered: file 2024-05-22T18:53:00+03:00 INFO client/internal/engine.go:359: Network monitor is disabled, not starting 2024-05-22T18:53:00+03:00 INFO client/internal/connect.go:261: Netbird engine started, the IP is: 100.150.200.200/16 2024-05-22T18:53:00+03:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream 2024-05-22T18:53:00+03:00 INFO management/client/grpc.go:147: connected to the Management Service stream 2024-05-22T18:53:00+03:00 WARN client/internal/engine.go:551: running SSH server is not permitted 2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted] 2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf 2024-05-22T18:53:00+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 549.946µs, total rules count: 22 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.1.1.1:53: read udp 10.0.0.50:36965->1.1.1.1:53: i/o timeout 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.0.0.1:53: read udp 10.0.0.50:46327->1.0.0.1:53: i/o timeout 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:265: Upstream resolving i2024-05-22T18:53:00+03:00 INFO client/internal/dns/host_linux.go:68: System DNS manager discovered: file 2024-05-22T18:53:00+03:00 INFO client/internal/engine.go:359: Network monitor is disabled, not starting 2024-05-22T18:53:00+03:00 INFO client/internal/connect.go:261: Netbird engine started, the IP is: 100.150.200.200/16 2024-05-22T18:53:00+03:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream 2024-05-22T18:53:00+03:00 INFO management/client/grpc.go:147: connected to the Management Service stream 2024-05-22T18:53:00+03:00 WARN client/internal/engine.go:551: running SSH server is not permitted 2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted] 2024-05-22T18:53:00+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf 2024-05-22T18:53:00+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 549.946µs, total rules count: 22 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.1.1.1:53: read udp 10.0.0.50:36965->1.1.1.1:53: i/o timeout 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 1.0.0.1:53: read udp 10.0.0.50:46327->1.0.0.1:53: i/o timeout 2024-05-22T18:53:02+03:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s 2024-05-22T18:53:02+03:00 INFO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout 2024-05-22T18:53:02+03:00 ERRO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:525: Failed to apply nameserver deactivation on the host: unable to configure DNS for this peer using file manager without a nameserver group with all domains configureds Disabled for 30s 2024-05-22T18:53:02+03:00 INFO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout 2024-05-22T18:53:02+03:00 ERRO [nameservers: [{1.1.1.1 udp 53} {1.0.0.1 udp 53}]] client/internal/dns/server.go:525: Failed to apply nameserver deactivation on the host: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured ```
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

@zzecool can you try adding a default nameserver in the NetBird's dashboard? As the detected DNS mode was file, it won't resolve DNS queries without one.

@mlsmaycon commented on GitHub (May 22, 2024): @zzecool can you try adding a default nameserver in the NetBird's dashboard? As the detected DNS mode was file, it won't resolve DNS queries without one.
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

@mlsmaycon

I have a dns for this node in the Web management interface.

The dns is up and running fine.

It is on the same machine that netbird is running on port 53.

@zzecool commented on GitHub (May 22, 2024): @mlsmaycon I have a dns for this node in the Web management interface. The dns is up and running fine. It is on the same machine that netbird is running on port 53.
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

in that case, you can add one of the node's local IPs as a nameserver and distribute it to a group that only contains the Synology node.

@mlsmaycon commented on GitHub (May 22, 2024): in that case, you can add one of the node's local IPs as a nameserver and distribute it to a group that only contains the Synology node.
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

in that case, you can add one of the node's local IPs as a nameserver and distribute it to a group that only contains the Synology node.

@mlsmaycon

This is exactly what i have.

On the web interface for this node group the DNS is the 10.0.0.50

and this is inside the node :

Its ip address just to be clear

$ ifconfig | grep -A 1 ovs
ovs_bond0 Link encap:Ethernet  HWaddr 00:15:30:9F:71:02  
          inet addr:10.0.0.50  Bcast:10.0.0.255  Mask:255.255.255.0

The resolv test :

$ nslookup google.com     
Server:         10.0.0.50
Address:        10.0.0.50#53

Non-authoritative answer:
Name:   Google.com
Address: 172.217.17.110
Name:   google.com
Address: 2a00:1450:4017:810::200e
@zzecool commented on GitHub (May 22, 2024): in that case, you can add one of the node's local IPs as a nameserver and distribute it to a group that only contains the Synology node. @mlsmaycon This is exactly what i have. On the web interface for this node group the DNS is the 10.0.0.50 and this is inside the node : Its ip address just to be clear ``` $ ifconfig | grep -A 1 ovs ovs_bond0 Link encap:Ethernet HWaddr 00:15:30:9F:71:02 inet addr:10.0.0.50 Bcast:10.0.0.255 Mask:255.255.255.0 ``` The resolv test : ``` $ nslookup google.com Server: 10.0.0.50 Address: 10.0.0.50#53 Non-authoritative answer: Name: Google.com Address: 172.217.17.110 Name: google.com Address: 2a00:1450:4017:810::200e ```
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

@mlsmaycon

image

Maybe this is the problem that after this rule i have cloudflare for ALL ?

Does the first rule matched have higher priority and used or not ?

Thanks

@zzecool commented on GitHub (May 22, 2024): @mlsmaycon ![image](https://github.com/netbirdio/netbird/assets/2816897/24dab0d2-9377-4367-b5d0-ef9a79708861) Maybe this is the problem that after this rule i have cloudflare for ALL ? Does the first rule matched have higher priority and used or not ? Thanks
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

Could be. The peers in the personal group might be using the cloudflare addresses.

Just to confirm, your Synology is part of the personal group? if not it should be, or you should add one of its group to the distribution groups.

@mlsmaycon commented on GitHub (May 22, 2024): Could be. The peers in the personal group might be using the cloudflare addresses. Just to confirm, your Synology is part of the `personal` group? if not it should be, or you should add one of its group to the distribution groups.
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

Could be. The peers in the personal group might be using the cloudflare addresses.

Just to confirm, your Synology is part of the personal group? if not it should be, or you should add one of its group to the distribution groups.

Yes its part of the personal group.

@zzecool commented on GitHub (May 22, 2024): > Could be. The peers in the personal group might be using the cloudflare addresses. > > Just to confirm, your Synology is part of the `personal` group? if not it should be, or you should add one of its group to the distribution groups. Yes its part of the personal group.
saavagebueno commented 2025-11-20 05:19:24 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

ok, to validate the setup try limiting the cloudflare configuration to another group.

@mlsmaycon commented on GitHub (May 22, 2024): ok, to validate the setup try limiting the cloudflare configuration to another group.
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

ok, to validate the setup try limiting the cloudflare configuration to another group.

Yeap that did the trick. So the first matched rule is getting ignore and replaced, you have to consider if this is what you want, as most ppl we are used to the iptables way priority of rules.

2024-05-22T19:48:25+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted]
2024-05-22T19:48:25+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf
2024-05-22T19:48:25+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 508.582µs, total rules count: 22

Removing the /etc/sysconfig/netbird breaks everything again.

So now that your install.sh script detects Synology just fine, please add the creation of /etc/sysconfig/netbird file :D

  • kind to explain what the userspace is doing exactly with the NB_WG_KERNEL_DISABLED=true config ?

We are making progress :D

@zzecool commented on GitHub (May 22, 2024): > ok, to validate the setup try limiting the cloudflare configuration to another group. Yeap that did the trick. So the first matched rule is getting ignore and replaced, you have to consider if this is what you want, as most ppl we are used to the iptables way priority of rules. ``` 2024-05-22T19:48:25+03:00 INFO client/internal/dns/file_linux.go:107: created a NetBird managed /etc/resolv.conf file with the DNS settings. Added 1 search domains. Search list: [netbird.selfhosted] 2024-05-22T19:48:25+03:00 INFO client/internal/dns/file_repair_linux.go:48: start to watch resolv.conf: /etc/resolv.conf 2024-05-22T19:48:25+03:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 508.582µs, total rules count: 22 ``` Removing the /etc/sysconfig/netbird breaks everything again. So now that your install.sh script detects Synology just fine, please add the creation of /etc/sysconfig/netbird file :D * kind to explain what the userspace is doing exactly with the NB_WG_KERNEL_DISABLED=true config ? We are making progress :D
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

@zzecool can you confirm that this local resolver, 10.0.0.50#53, comes with every Synology by default?

@mlsmaycon commented on GitHub (May 22, 2024): @zzecool can you confirm that this local resolver, 10.0.0.50#53, comes with every Synology by default?
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 22, 2024):

@zzecool can you confirm that this local resolver, 10.0.0.50#53, comes with every Synology by default?

Nope this is a DNS that im personaly running on this machine.

@zzecool commented on GitHub (May 22, 2024): > @zzecool can you confirm that this local resolver, 10.0.0.50#53, comes with every Synology by default? Nope this is a DNS that im personaly running on this machine.
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 22, 2024):

Okay, in that case, it is better not to default to userspace mode just yet, as it may affect other users.

We will look into the masquerade issue and then make a decision.

Thanks for validating this.

@mlsmaycon commented on GitHub (May 22, 2024): Okay, in that case, it is better not to default to userspace mode just yet, as it may affect other users. We will look into the masquerade issue and then make a decision. Thanks for validating this.
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@zzecool commented on GitHub (May 23, 2024):

Okay, in that case, it is better not to default to userspace mode just yet, as it may affect other users.

We will look into the masquerade issue and then make a decision.

Thanks for validating this.

Can you think any other way to make this work in kernel space while having another DNS running in the same machine ?

@zzecool commented on GitHub (May 23, 2024): > Okay, in that case, it is better not to default to userspace mode just yet, as it may affect other users. > > We will look into the masquerade issue and then make a decision. > > Thanks for validating this. Can you think any other way to make this work in kernel space while having another DNS running in the same machine ?
saavagebueno commented 2025-11-20 05:19:25 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

@zzecool is this still an issue for you with latest NetBird versions?

possibly related to https://github.com/netbirdio/netbird/issues/3698

@nazarewk commented on GitHub (Apr 23, 2025): @zzecool is this still an issue for you with latest NetBird versions? possibly related to https://github.com/netbirdio/netbird/issues/3698
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label bug client dns synology triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#890
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?