Hot answers tagged vpn
8
It's not the ssh client that decides through which interface TCP
packets should go, it's the kernel. In short, SSH asks the kernel to
open a connection to a certain IP address, and the kernel decides
which interface is to be used by consulting the routing tables.
(The following assumes you're on GNU/Linux; the general concept is the
same for all Unices, ...
4
Hamachi isn't meant for that. It's a VPN service/software, not an anonymous browsing helper.
You could use Hamachi to tunnel traffic to another machine that runs something like Tor, possibly with an http proxy too or whatever else anonymizing techniques you will.
Hamachi itself doesn't provide that. It lets you build a private network, but you have to deal ...
4
/etc/resolv.conf defines how the computer resolves host names (e.g. which, if any, default domain names are searched when you try to resolve a non-FQDN hostname....lookup for a bare www becomes www.yourdomain.example.com), and which name servers are used to do the lookup.
One of the reasons, and the most likely, that VPN clients might modify ...
3
Two of the possibilities are:
the host you're trying to ssh into only allows connections from certain IP addresses (e.g. addresses on one or more of the university's VLANs). They may not have configured it to recognise VPN addresses as "local".
the host is configured to allow password-based auth from certain addresses but requires an ssh key from all ...
3
Don't use CIPE. It was deprecated a long time ago, as it isn't actually cryptographically secure. IPSEC is current, but it's a giant pain to get running.
Use OpenVPN, especially if it's computer-to-computer (if some of the clients are, say, phones, then use IPSEC/PPTP, as OpenVPN clients aren't easily available on such devices). Here's the HOWTO:
...
3
I have no experience of PPTP Client and haven't looked at the instructions. But the command route add -net 0.0.0.0/0 ppp0 means “route all traffic through ppp0 except the traffic that has more precise routes”. This means that
the loopback interface, your local network if you have one, and the route to the VPN server (which is set up, right?) will use the ...
3
You need to do three things on your VPN server (the Linode) to make this work:
You must enable IP forwarding:
sysctl -w net.ipv4.ip_forward=1
Set up destination NAT (DNAT) to forward the port. You've probably already figured this out because it's standard port forwarding stuff, but for completeness:
iptables -t nat -A PREROUTING -d x.x.x.x -p tcp ...
2
So where points that address you typed in a gateway field? I've never configured OpenVPN using NetworkManager but i suppose that is the place where you should provide the address of your router.
And in your log file there is a line which says:
Mar 7 15:42:43 ASDF nm-openvpn[23554]: Cannot load certificate file /home/g/Desktop/client1/client1.crt: ...
2
I believe that simple X forwarding will be too slow for what you want to do, so you'll have to choose between other protocols like VNC (thereis plenty of implementations), RDP (rdesktop) or NX. I would recommend NX as it is based on X, is very fast and even provides sound and file transfer. FreeNX is easy to setup and as it is based on X (just compressed and ...
2
There is no practical way to select different routes on an application-by-application or process-by-process basis. (Linux had one for a time: iptables --cmd-owner, but that disappeared in kernel 2.6.14). See Linux : restricting outgoing on an application basis.
You can select different routes on a user-by-user basis with iptables --uid-owner, or select ...
2
Your kernel is too recent for the Cisco VPN client. You'll need to downgrade your kernel to a 2.6.30 version or below.
See the release notes.
2
Yeah... CrunchBang Linux uses .debs, not .rpms. Try the linux-headers-2.6-686 package or some variant thereof (e.g. linux-headers-2.6-amd64 on a 64-bit installation). And you don't actually need the source code, you just need the externally-visible headers.
And beware 10-year-old instructions.
2
http://serverfault.com/questions/128357/routing-application-traffic-through-specific-interface
use iptables -m owner. This lets you setup OUTPUT chain rules based on UID, GID, PID, SID and command name.
2
I think you can just get it from github either through git
$ git clone git://github.com/apenwarr/sshuttle.git
or simply download a recent package and unpack it
$ wget https://github.com/apenwarr/sshuttle/tarball/master
$ tar xvzf <filename>
And then simply enter the directory and run it. You can move it to /opt/ or anywhere else, where you need ...
2
I don't know of an "out-of-the-box" solution that does this completely automatically and seamlessly. It is possible. The best I can do is provide a "high-level" summary.
Basically, you are looking at a routing problem. You want traffic destined to specific subnets to travel over different gateway IP addresses. If you are willing to live without a ...
2
Well it actually depends on your desired goal.
Do you want to distribute load (and client requests) between both of your webservers (multiple active arch) or you just need to be "fully" redundant in case of webserver failure?
If you just need the redundancy aspect and are not worried about distributing load I would suggest using pacemaker to achieve this.
...
2
While this is something that is usually done on the server as mentioned in the comments, there might be cases where you only want to use the VPN's DNS for queries inside of the VPN. In that case you'd probably want to run a lightweight DNS daemon on your system and instruct it where to send what query. If you are in several VPNs at once this is basically a ...
2
You can use iptables to do this, probably. At least if "goes over the VPN" is something that iptables can see, for example, its a separate tunnel device. Assuming the vpn is device "vpn", something like:
iptables -P OUTPUT DROP
iptables -A OUTPUT -o vpn -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
# dhcp
iptables -A OUTPUT -p udp --sport 68 --dport 67 -j ...
2
You can't have your cake and eat it. Your ISP carries the network traffic from your computer to the server, so it has to know which host the traffic is going to. Note that if you use HTTPS, the ISP knows which host you're connecting to, it doesn't see the rest of the URL.
If you don't want your ISP to know which server you're connecting to, you need to ...
2
Try Tor's obfsproxy. It was specifically designed for this kind of usecases. It obfuscates the traffic between the client and a Tor bridge in a way, that - in theory - it becomes indistinguishable from gibberish. At least it shouldn't be triggered as Tor- or SSL-traffic.
https://www.torproject.org/projects/obfsproxy.html.en
2
eth0:1, eth0:2 are interface aliases. They do not function as individual interface. The actual interface is still eth0. Traffic going in and out of those aliases are still count as eth0's.
You will get a better idea if you use iftop to monitor those interfaces one by one.
iftop -BPn -i eth0
iftop -BPn -i eth0:1
iftop -BPn -i eth0:2
All 3 commands will ...
2
The EPEL repository has a vpnc package. Generally, EPEL should be the first place you should look for additional packages. The EPEL repository is semi-official, since it is from the Fedora project. Unlike rpmforge, it doesn't contain any packages that already exist in CentOS/RHEL, so you do not need to worry about conflicts.
Instructions on setting up the ...
2
How do I ensure that my torrent client actually uses this connection?
There is a site, CheckMyTorrentIP, that does exactly that. Basically, you download a torrent file generated specifically for you and once you open it in your client it will report the IP address being used. The IP should be displayed directly in your client but you can also revisit the ...
2
OpenVPN provides a link. If running in tun (recommended) mode, it provides a link for IP traffic. If running in tap mode, it provides a link for Ethernet traffic (which includes IP, but also all kinds of other things).
If you run in tap mode, you need to bridge your OpenVPN tap interface to your Ethernet interface. You can do that with brctl, but, ...
2
First of all: you won't be able to route traffic to 127.x.y.z anywhere other than the local machine (ok, it might even be possible, but you'd certainly break something else in the process...) so I'd recommend updating the apache config to also listen at the VPN IP (e.g. 10.8.0.1). If that's not an option, you could try one of the options at the end of my ...
2
Of course it's possible. The configuration you might want to try is tap rather than tun if you wonder about that, even though it might bit a bit harder to configure, it's easier to get hosts together in one network that way. You might need to enable client-to-client connections for that - there is a line for that commented out in example OpenVPN configs.
...
1
/etc/resolv.conf lists the name servers that your computer uses to look up DNS names. To send packets to a computer, you need to know its IP address, but IP addresses are (more or less) tied to a particular Internet service provider and location, and can change, so they aren't normally used to designate computers. Instead, DNS names are used.
Usually ...
1
Of course you can run both at the same time. IIRC t is also possible to connect to a cisco concentrator using vpnc, as long as it has ipsec support. What will happen when you do both we can't tell. That depends on the VPN configurations, which may be pushed to your computer from the remote end.
To get what you want you probably have to manually configure ...
1
If it were Linux, the command you'd use would be:
ip route add 192.168.0.0/16 via 10.8.0.7
This requires that ip_forwarding is enabled on PC A (assuming it's a Linux box, I'm sure there's a similar concept in other OSes). I'm not sure if the "ip" command is available on Mac.
1
I suggest pptp
It's easy to install on CentOS (binary for CentOS 6.2 right here)
Clients are universally available (all OSs, phones, etc.)
It's not too hard to setup. See a simple tutorial for CentOS 6 here
Only top voted, non community-wiki answers of a minimum length are eligible
