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

(Proxmox) Can't ping other hosts, even though they are visible. #209

New Issue
Closed
opened 2025-11-20 05:08:02 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:08:02 -05:00
Owner
Copy Link

Originally created by @hansauge on GitHub (Oct 18, 2022).

Trying to connect multiple RDPs from a Proxmox node, done with reusable keys, netbird status/client sees them, but that is about it. Pigning is not possible. It might due to double NAT, previously Tailscale did handle them without an issue.

Originally created by @hansauge on GitHub (Oct 18, 2022). Trying to connect multiple RDPs from a Proxmox node, done with reusable keys, netbird status/client sees them, but that is about it. Pigning is not possible. It might due to double NAT, previously Tailscale did handle them without an issue.
saavagebueno added the bugwaiting-feedbacktriage-needed labels 2025-11-20 05:08:02 -05:00
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 31, 2022):

Hello @hansauge, the double NAT shouldn't be an issue. We don't manage the windows firewall yet to allow connections to windows nodes. You should be able to ping from a Windows node to a Linux but not the other around without either enabling in the firewall or converting the tunnel interface into private.

@mlsmaycon commented on GitHub (Oct 31, 2022): Hello @hansauge, the double NAT shouldn't be an issue. We don't manage the windows firewall yet to allow connections to windows nodes. You should be able to ping from a Windows node to a Linux but not the other around without either enabling in the firewall or converting the tunnel interface into private.
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@hansauge commented on GitHub (Nov 8, 2022):

Hi @mlsmaycon, pings do not work including Windows to Windows nodes. Only thing working is a Mac with one Windows laptop, which are the only ones outside the proxmox network and the management interface which connects fine across all devices.

@hansauge commented on GitHub (Nov 8, 2022): Hi @mlsmaycon, pings do not work including Windows to Windows nodes. Only thing working is a Mac with one Windows laptop, which are the only ones outside the proxmox network and the management interface which connects fine across all devices.
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 16, 2023):

@hansauge, We've refactored the connectivity layer. Can you check if the issue happens on the latest version?

@mlsmaycon commented on GitHub (Jun 16, 2023): @hansauge, We've refactored the connectivity layer. Can you check if the issue happens on the latest version?
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@houpi commented on GitHub (Oct 3, 2023):

我在0.23.6上依然存在这个问题，pve为7.4-15，直到手动输入以下命令后才解决
iptables -F

在这之前，我查看了一下iptables的配置
root@pve:~# iptables -L -nv
Chain INPUT (policy ACCEPT 2450 packets, 411K bytes)
pkts bytes target prot opt in out source destination
3231 559K ts-input all -- * * 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
108 17260 DOCKER-USER all -- * * 0.0.0.0/0 0.0.0.0/0
108 17260 DOCKER-ISOLATION-STAGE-1 all -- * * 0.0.0.0/0 0.0.0.0/0
39 4342 ACCEPT all -- * docker0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
25 1452 DOCKER all -- * docker0 0.0.0.0/0 0.0.0.0/0
44 11466 ACCEPT all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- docker0 docker0 0.0.0.0/0 0.0.0.0/0
0 0 ts-forward all -- * * 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT 3676 packets, 1170K bytes)
pkts bytes target prot opt in out source destination

Chain DOCKER (1 references)
pkts bytes target prot opt in out source destination
9 612 ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 udp dpt:3478
16 840 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:443

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
pkts bytes target prot opt in out source destination
44 11466 DOCKER-ISOLATION-STAGE-2 all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0
108 17260 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
pkts bytes target prot opt in out source destination
0 0 DROP all -- * docker0 0.0.0.0/0 0.0.0.0/0
44 11466 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain DOCKER-USER (1 references)
pkts bytes target prot opt in out source destination
108 17260 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain ts-forward (1 references)
pkts bytes target prot opt in out source destination
0 0 MARK all -- tailscale0 * 0.0.0.0/0 0.0.0.0/0 MARK xset 0x40000/0xff0000
0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 mark match 0x40000/0xff0000
0 0 DROP all -- * tailscale0 100.64.0.0/10 0.0.0.0/0
0 0 ACCEPT all -- * tailscale0 0.0.0.0/0 0.0.0.0/0

Chain ts-input (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- lo * 100.101.53.37 0.0.0.0/0
0 0 RETURN all -- !tailscale0 * 100.115.92.0/23 0.0.0.0/0
7 420 DROP all -- !tailscale0 * 100.64.0.0/10 0.0.0.0/0

我怀疑过是否因为tailscale的iptables规则影响了netbird，但我在其它机器上也安装了tailscale和netbird，均正常。

@houpi commented on GitHub (Oct 3, 2023): 我在0.23.6上依然存在这个问题，pve为7.4-15，直到手动输入以下命令后才解决 iptables -F 在这之前，我查看了一下iptables的配置 root@pve:~# iptables -L -nv Chain INPUT (policy ACCEPT 2450 packets, 411K bytes) pkts bytes target prot opt in out source destination 3231 559K ts-input all -- * * 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 108 17260 DOCKER-USER all -- * * 0.0.0.0/0 0.0.0.0/0 108 17260 DOCKER-ISOLATION-STAGE-1 all -- * * 0.0.0.0/0 0.0.0.0/0 39 4342 ACCEPT all -- * docker0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 25 1452 DOCKER all -- * docker0 0.0.0.0/0 0.0.0.0/0 44 11466 ACCEPT all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- docker0 docker0 0.0.0.0/0 0.0.0.0/0 0 0 ts-forward all -- * * 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 3676 packets, 1170K bytes) pkts bytes target prot opt in out source destination Chain DOCKER (1 references) pkts bytes target prot opt in out source destination 9 612 ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 udp dpt:3478 16 840 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:443 Chain DOCKER-ISOLATION-STAGE-1 (1 references) pkts bytes target prot opt in out source destination 44 11466 DOCKER-ISOLATION-STAGE-2 all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 108 17260 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (1 references) pkts bytes target prot opt in out source destination 0 0 DROP all -- * docker0 0.0.0.0/0 0.0.0.0/0 44 11466 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) pkts bytes target prot opt in out source destination 108 17260 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain ts-forward (1 references) pkts bytes target prot opt in out source destination 0 0 MARK all -- tailscale0 * 0.0.0.0/0 0.0.0.0/0 MARK xset 0x40000/0xff0000 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 mark match 0x40000/0xff0000 0 0 DROP all -- * tailscale0 100.64.0.0/10 0.0.0.0/0 0 0 ACCEPT all -- * tailscale0 0.0.0.0/0 0.0.0.0/0 Chain ts-input (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 100.101.53.37 0.0.0.0/0 0 0 RETURN all -- !tailscale0 * 100.115.92.0/23 0.0.0.0/0 7 420 DROP all -- !tailscale0 * 100.64.0.0/10 0.0.0.0/0 我怀疑过是否因为tailscale的iptables规则影响了netbird，但我在其它机器上也安装了tailscale和netbird，均正常。
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

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

closing for lack of activity

@nazarewk commented on GitHub (Apr 17, 2025): closing for lack of activity
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 triage-needed waiting-feedback
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#209
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?