Port forwarding for VPN connection
I'm using a public wifi hotspot. Usually when I connect to these, I immediately connect to my college VPN. On this hotspot, only browsing works (no program other than a browser seems to be able to access the internet, this includes ping commands from the terminal). I'm guessing this is because of the firewall in use by the hotspot provider.
I'm given to understand that it should be possible to tunnel all of my traffic through an SSH tunnel, pointing to the correct port. I can set up a server on my home network to tunnel to, but it does not have a static IP. Is there a way around this, or possibly an easier way than SSH tunneling?
--Update--
I've since set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
ssh ssh-tunneling port-forwarding wifi-hotspot
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm using a public wifi hotspot. Usually when I connect to these, I immediately connect to my college VPN. On this hotspot, only browsing works (no program other than a browser seems to be able to access the internet, this includes ping commands from the terminal). I'm guessing this is because of the firewall in use by the hotspot provider.
I'm given to understand that it should be possible to tunnel all of my traffic through an SSH tunnel, pointing to the correct port. I can set up a server on my home network to tunnel to, but it does not have a static IP. Is there a way around this, or possibly an easier way than SSH tunneling?
--Update--
I've since set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
ssh ssh-tunneling port-forwarding wifi-hotspot
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
3
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37
add a comment |
I'm using a public wifi hotspot. Usually when I connect to these, I immediately connect to my college VPN. On this hotspot, only browsing works (no program other than a browser seems to be able to access the internet, this includes ping commands from the terminal). I'm guessing this is because of the firewall in use by the hotspot provider.
I'm given to understand that it should be possible to tunnel all of my traffic through an SSH tunnel, pointing to the correct port. I can set up a server on my home network to tunnel to, but it does not have a static IP. Is there a way around this, or possibly an easier way than SSH tunneling?
--Update--
I've since set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
ssh ssh-tunneling port-forwarding wifi-hotspot
I'm using a public wifi hotspot. Usually when I connect to these, I immediately connect to my college VPN. On this hotspot, only browsing works (no program other than a browser seems to be able to access the internet, this includes ping commands from the terminal). I'm guessing this is because of the firewall in use by the hotspot provider.
I'm given to understand that it should be possible to tunnel all of my traffic through an SSH tunnel, pointing to the correct port. I can set up a server on my home network to tunnel to, but it does not have a static IP. Is there a way around this, or possibly an easier way than SSH tunneling?
--Update--
I've since set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
ssh ssh-tunneling port-forwarding wifi-hotspot
ssh ssh-tunneling port-forwarding wifi-hotspot
edited Feb 26 '15 at 1:42
Alex
asked Feb 23 '15 at 22:27
AlexAlex
1187
1187
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
3
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37
add a comment |
1
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
3
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37
1
1
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
3
3
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37
add a comment |
1 Answer
1
active
oldest
votes
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP:
ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`.
It won't be very efficient however.
If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a VPN over SSH.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186460%2fport-forwarding-for-vpn-connection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP:
ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`.
It won't be very efficient however.
If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a VPN over SSH.
add a comment |
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP:
ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`.
It won't be very efficient however.
If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a VPN over SSH.
add a comment |
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP:
ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`.
It won't be very efficient however.
If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a VPN over SSH.
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP:
ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`.
It won't be very efficient however.
If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a VPN over SSH.
answered Mar 5 '15 at 8:36
ysdxysdx
1,192812
1,192812
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186460%2fport-forwarding-for-vpn-connection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
If you have a fix ip anywhere on the world, maybe you could configure an ssh daemon on its port 443. Without highly sophisticated tricks, there is now way to differentiate a https connection from an ssh, except by its port. Both are ssl connections, and the proxy/router can't see, what is in it.
– peterh
Feb 23 '15 at 22:33
3
@peterh Actually SSH is not based on SSL, it's derived from similar principles but was designed separately and SSH traffic can be distinguished from SSL by the very simple trick of checking the first two bytes sent by the client (IIRC). Many filters don't bother and only filter by port.
– Gilles
Feb 24 '15 at 21:35
@peterh I've set up a raspberry pi with a static ip on my home network. Can I either tunnel all of my traffic over ssh, via the RPi, or even just tunnel the VPN connection (that I would normally use, were the ports it uses not blocked over ssh (I'm not too worried about latency).
– Alex
Mar 2 '15 at 14:37