Skip to content

Question about network setup #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gyokiss opened this issue Apr 8, 2025 · 4 comments
Open

Question about network setup #30

gyokiss opened this issue Apr 8, 2025 · 4 comments

Comments

@gyokiss
Copy link

gyokiss commented Apr 8, 2025

Dear All,

As beginner, a probably very basic question. I would like to build up a lab, to see, what is possible, what can I do with this environment. I have in cloud built up the pangolin server, it looks good. The newt installation itself looks good, and pangolin reports online. But - on newt server do I see constant pinging attempts, I think the connection is not so good as should be. Also cannot add proxy for my internal stuff. Reports back gateway timeout.

My lab is behind a firewalled environment. I think should be there some incoming traffic enabled to newt server?

Thanks

György

@oschwartz10612
Copy link
Member

Hi is this related to fosrl/pangolin#495)?

If so lets continue over there. If the pings are failing that is why you would be seeing the gateway timeout.

@gyokiss
Copy link
Author

gyokiss commented Apr 10, 2025

Cool,

Now I have made a very new test - on another environment, another mikrotik ( but as fa I see, very similar config at least in nat) and newt runs on macos. That runs fine.
2nd test from third env - mikrotik as well, but now a rhel9 - also success.

So I have checked back the original environment with a different newt host, - landed in same issue.

That means newt is unable to connect. Interesting, the basic wirguard has no issue with connection. It would be great to have a test/requirement what should be a basic network config to use newt, or a short sample what is the requirement to create gateway with basic wireguard.

@gyokiss
Copy link
Author

gyokiss commented Apr 10, 2025

update 2.
I have managed to remove the firewall filter in my environment - it look s like all UDP ports have to enabled to reacht the mikrotik in this case. ( My mikrotiks in test and prd environment are CHR vm's).
Question: do you have a limit/range what udp ports will be used by newt? or is there any way to limit that?

@oschwartz10612
Copy link
Member

Sorry for the long delay. Did you get it to work?

You can edit the start_port in the config.yml to set the port for Wireguard for newt.

gerbil:
    start_port: 51820

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants