Open hwiorn opened 1 month ago
I figure out the issue was caused by exit-node. After exit-node routing was disabled on server side, this issue has gone. On the other hands, disabling it only on client side doesn't work.
But, the exit-node feature is I wanted to use. I don't know what settings cause this issue.
I found another issue is, network transmission is really slow when exit-node routing is active, even both vpn and device in the same network.
try to add inside netbird catch-all DNS service via google/cloudflare. I have same problem and this strange solution works. And it works for fix strange internal dns servers resolving problems
Do you mean "Nameservers" in netbird dashboard? If it is what your talking about, I already did use google DNS in this netbird network. I think I could test to toggle DNS settings once a more.
@hwiorn Can you confirm if the server with the public IP is the routing client (part of distribution group for the exit node) or the routing server (the exit node itself)?
According to your netbird status
it seems to be the former. In that case all responses (e.g. to your ingress ssh attempt) are routed via the exit node and become inaccessible from elsewhere unless there is another more specific route installed.
@lixmal I thought exit node peers can be by installing netbird client. I didn't realize it has ingress issue. I installed the netbird client to make an exit node within my VPN server which was already netbird self-hosted. I understand this behavior that you said if exit node is active. But, I don't get it how I can make the routing to accept external access from public IP using netbird. Do I have to set some internal routing between wg IPs in netbird? Or just settings up "the routing server" is enough? And, I can't figure out what's the routing server in your comment.
Describe the problem
I'm netbird newbie. I installed self-hosted version. this is my infra setup.
Before netbird up(or after netbird down).
After netbird up.
How can I enable public IP accessing? To Reproduce
Steps to reproduce the behavior:
curl -fsSL https://pkgs.netbird.io/install.sh | sh
netbird up --management-url https://vpn.mysite.com:33073 --setup-key XXXXX
server-a.netbird.selfhosted
and check it's okay.Expected behavior
Can access public IP and domain of server A.
Are you using NetBird Cloud?
No. I use self-host netbird.
NetBird version
NetBird status -dA output:
Do you face any (non-mobile) client issues?
Please provide the file created by
netbird debug for 1m -AS
. netbird.debug.375981251.zipScreenshots
If applicable, add screenshots to help explain your problem.
Additional context
SSH always got
operation timed out
error, when netbird is connected.