How do I add a port exception to an OpenVPN connection? [closed]
up vote
0
down vote
favorite
I want port 22 to remain untouched as I believe it to be secure enough for my purposes and I'd like to use it to sync files.
ssh openvpn
closed as unclear what you're asking by vidarlo, Thomas, mikewhatever, NickTux, George Udosen Nov 20 at 9:46
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I want port 22 to remain untouched as I believe it to be secure enough for my purposes and I'd like to use it to sync files.
ssh openvpn
closed as unclear what you're asking by vidarlo, Thomas, mikewhatever, NickTux, George Udosen Nov 20 at 9:46
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want port 22 to remain untouched as I believe it to be secure enough for my purposes and I'd like to use it to sync files.
ssh openvpn
I want port 22 to remain untouched as I believe it to be secure enough for my purposes and I'd like to use it to sync files.
ssh openvpn
ssh openvpn
asked Nov 17 at 15:32
NonYaBidnezz
226
226
closed as unclear what you're asking by vidarlo, Thomas, mikewhatever, NickTux, George Udosen Nov 20 at 9:46
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by vidarlo, Thomas, mikewhatever, NickTux, George Udosen Nov 20 at 9:46
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07
add a comment |
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
In short there's two ways to accomplish this.
Over VPN
In this case, your VPN provider has to allow incoming traffic to port 22 on your VPN link, or you have to set up SSH to use an port that allows incoming traffic. How to do this differs from provider to provider, but most do tend to use RFC1918-addressing with optional port forwarding. In case of port forwarding you typically don't get to pick the port.
Bypassing VPN
You can't create routes that involves port numbers, but that should not be necessary.
Simply make sure that you still have a valid route to reach the host you're trying to reach outside of the VPN route. This can be a /32, i.e. a route only to the host you're sshing from.
In addition, if you have set up a firewall, you must allow ssh on that interface.
Without any more detailed configuration from you, this is the answer that's possible to give. You'll have to fill in the details yourself.
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
In short there's two ways to accomplish this.
Over VPN
In this case, your VPN provider has to allow incoming traffic to port 22 on your VPN link, or you have to set up SSH to use an port that allows incoming traffic. How to do this differs from provider to provider, but most do tend to use RFC1918-addressing with optional port forwarding. In case of port forwarding you typically don't get to pick the port.
Bypassing VPN
You can't create routes that involves port numbers, but that should not be necessary.
Simply make sure that you still have a valid route to reach the host you're trying to reach outside of the VPN route. This can be a /32, i.e. a route only to the host you're sshing from.
In addition, if you have set up a firewall, you must allow ssh on that interface.
Without any more detailed configuration from you, this is the answer that's possible to give. You'll have to fill in the details yourself.
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
add a comment |
up vote
0
down vote
In short there's two ways to accomplish this.
Over VPN
In this case, your VPN provider has to allow incoming traffic to port 22 on your VPN link, or you have to set up SSH to use an port that allows incoming traffic. How to do this differs from provider to provider, but most do tend to use RFC1918-addressing with optional port forwarding. In case of port forwarding you typically don't get to pick the port.
Bypassing VPN
You can't create routes that involves port numbers, but that should not be necessary.
Simply make sure that you still have a valid route to reach the host you're trying to reach outside of the VPN route. This can be a /32, i.e. a route only to the host you're sshing from.
In addition, if you have set up a firewall, you must allow ssh on that interface.
Without any more detailed configuration from you, this is the answer that's possible to give. You'll have to fill in the details yourself.
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
add a comment |
up vote
0
down vote
up vote
0
down vote
In short there's two ways to accomplish this.
Over VPN
In this case, your VPN provider has to allow incoming traffic to port 22 on your VPN link, or you have to set up SSH to use an port that allows incoming traffic. How to do this differs from provider to provider, but most do tend to use RFC1918-addressing with optional port forwarding. In case of port forwarding you typically don't get to pick the port.
Bypassing VPN
You can't create routes that involves port numbers, but that should not be necessary.
Simply make sure that you still have a valid route to reach the host you're trying to reach outside of the VPN route. This can be a /32, i.e. a route only to the host you're sshing from.
In addition, if you have set up a firewall, you must allow ssh on that interface.
Without any more detailed configuration from you, this is the answer that's possible to give. You'll have to fill in the details yourself.
In short there's two ways to accomplish this.
Over VPN
In this case, your VPN provider has to allow incoming traffic to port 22 on your VPN link, or you have to set up SSH to use an port that allows incoming traffic. How to do this differs from provider to provider, but most do tend to use RFC1918-addressing with optional port forwarding. In case of port forwarding you typically don't get to pick the port.
Bypassing VPN
You can't create routes that involves port numbers, but that should not be necessary.
Simply make sure that you still have a valid route to reach the host you're trying to reach outside of the VPN route. This can be a /32, i.e. a route only to the host you're sshing from.
In addition, if you have set up a firewall, you must allow ssh on that interface.
Without any more detailed configuration from you, this is the answer that's possible to give. You'll have to fill in the details yourself.
answered Nov 18 at 10:14
vidarlo
8,03542341
8,03542341
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
add a comment |
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
In retrospect, I will need to bypass to prevent providing clues I don't want to provide through Dynamic DNS.
– NonYaBidnezz
Nov 18 at 23:11
add a comment |
What are you trying to achieve, and what is your configuration?
– vidarlo
Nov 17 at 15:47
I'm using protonvpn. How can I get the information that you require? Would the contents of an *.ovpn file do it?
– NonYaBidnezz
Nov 17 at 17:03
Redacted, of course.
– NonYaBidnezz
Nov 17 at 17:04
Objective is to get both my machines on OpenVpn while still being able to sync files over ssh. SSH can take place over VPN or not. VPN is actually preferred. I use dynamic DNS. I'm assuming I'll have to script an update to that on startup or something. I'll worry about that later.
– NonYaBidnezz
Nov 17 at 17:07