-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
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. |
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. 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. |
update 2. |
Sorry for the long delay. Did you get it to work? You can edit the
|
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
The text was updated successfully, but these errors were encountered: