Is it possible to eliminate the LONG automatic message "** Connected with NAT traversal - might be unstable **" from the initial VPN Client login message window? Or, at least, allow the administrator-defined message to appear BEFORE the aforementioned long automatic message?
Thanks for any help.
Maurício
How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
-
- Posts: 8
- Joined: Mon Nov 22, 2021 5:28 pm
-
- Posts: 286
- Joined: Wed Nov 25, 2020 9:10 am
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
Open the port so that Nat traversal is no longer needed.
-
- Posts: 8
- Joined: Mon Nov 22, 2021 5:28 pm
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
Can you ellaborate on the safest way to implement this? Should I set the internal VPN Server listening only to port 5555 and forward this port on the firewall to it? Today the VPN Server is listening to ports 443, 992, 1194 and 5555.
Thaks again for any help.
Mauricio
Thaks again for any help.
Mauricio
-
- Posts: 286
- Joined: Wed Nov 25, 2020 9:10 am
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
What have you tried so far?
-
- Posts: 8
- Joined: Mon Nov 22, 2021 5:28 pm
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
So far I did not tamper with the firewall, as the VPN Server is working fine without any instability, even for very long connections. I just would like to get my message for the VPN users FIRST on the message window...
-
- Posts: 8
- Joined: Mon Nov 22, 2021 5:28 pm
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
Hello
Did the test on the firewall using TCP port 5555 pointed to the VPN Server and also configuring the client to use port 5555 (originally the client was using port 443). VPN works OK and no "NAT traversal" message. I'll now restrict the server to listen only to port 5555 and test again.
Mauricio
Did the test on the firewall using TCP port 5555 pointed to the VPN Server and also configuring the client to use port 5555 (originally the client was using port 443). VPN works OK and no "NAT traversal" message. I'll now restrict the server to listen only to port 5555 and test again.
Mauricio
-
- Posts: 8
- Joined: Mon Nov 22, 2021 5:28 pm
Re: How to eliminate "** Connected with NAT traversal - might be unstable **" text from initial message
Internal VPN Server (running on RPi 64-bit) works OK listening only to port 5555 redirected from the Mikrotik firewall. No other port is needed.
Thanks for all your help.
Mauricio
Thanks for all your help.
Mauricio