Hi there, I own a VPS and I have installed OpenVPN on my CentOS with no problems on my main dedicated/static IP. What I'd like to know is that if I have a second dedicated/static IP for the same VPS is it possible to switch between which IP I want to use with OpenVPN when I authenticate with a user + pass combination? If so how can I do this? Thanks in advance

Yes. Entirely possible, if not somewhat easy enough too. Farmiliar with IPTABLES? If so, its a combintaion of a 'client_connect' script, and a dynamic firewall rule, which is added when the client connects and removed when the client disconnects.

Hi thanks for the quick reply. This is my first time buying and using a VPS so you can say I will need spoon feeding :) I have followed this tutorial to setup my first connection: http://www.webhostingtalk.com/showthread.php?t=1024872 What needs to be done to the above steps in order to use the second IP as I have mentioned in my first post? Do I just add the new IP to "iptables" and create a new .conf file on the server and a matching .ovpn file on my computer for this to work? Thank

[quote="sens0r"]What needs to be done to the above steps in order to use the second IP as I have mentioned in my first post?[/quote] Basically follow that guide (or any Centos guides out there), until you get a basic but functional setup. Adding the custom IP should be donelast, when everything else is working fine. What stage are you at now? Can you surf net through the tunnel? (assuming thats a function you're after).

Yes as stated I have followed the above mentioned tutorial and already using my first IP without any problem. So how do I add the second IP :roll:

[quote="sens0r"]:roll:[/quote] Dude... Here we go: create client-connect.sh and client-disconnect.sh, chmod to 755 [code]cd /etc/openvpn touch ./client-connect.sh touch ./client-disconnect.sh chmod 755 ./client-connect.sh chmod 755 ./client-disconnect.sh[/code] edit server.conf, add: [code]script-security 2 client-connect /etc/openvpn/client-connect.sh client-disconnect /etc/openvpn/client-disconnect.sh[/code]

client-connect.sh [code]#!/bin/bash if [ $common_name != "common_name_here" ] then iptables -t nat -A POSTROUTING -s $ifconfig_pool_remote_ip -o venet0 -j SNAT --to-source 111.255.111.111 #VPS IP 1 fi if [ $common_name = "common_name_here" ] then iptables -t nat -A POSTROUTING -s $ifconfig_pool_remote_ip -o venet0 -j SNAT --to-source 222.255.222.222 #VPS IP 2 fi exit 0[/code] client-disconnect.sh [code]#!/bin/bash if [ $common_name != "common_name_here" ] then iptables -t nat -D POSTROUTING -s $ifconfig_pool_remote_ip -o venet0 -j SNAT --to-source 111.255.111.111 #VPS IP 1 fi if [ $common_name = "common_name_here" ] then iptables -t nat -D POSTROUTING -s $ifconfig_pool_remote_ip -o venet0 -j SNAT --to-source 222.255.222.222 #VPS IP 2 fi exit 0[/code] not finished yet.

I'll wait for you to provide all the instructions, I hope you can comment the instructions as well which would be very helpful and greatly appreciated.

And what are these two files supposed to contain and how will they help me in utilizing both the IPs of my VPS?

Wait a minute, I think you mis-understood me. I will be the only one using the OpenVPN on my VPS, I just want to be able to select between the two IPs which I have for my VPS when I connect through the OpenVPN. Can I not do this by simply adding the new IP into the "iptable" and generating new .conf and .ovpn files matching the second IP?

[quote="sens0r"]Wait a minute, I think you mis-understood me. I will be the only one using the OpenVPN on my VPS, I just want to be able to select between the two IPs which I have for my VPS when I connect through the OpenVPN. Can I not do this by simply adding the new IP into the "iptable" and generating new .conf and .ovpn files matching the second IP?[/quote] Fo sure there's an easier way, if its just you. I thought you wanted to grant access based on username. If its just for you personally, then the easiest way will be just to run 2 instances of openvpn on the server; 1 on port 1194, and 1 or port 1195 for example. When a conection comes in on port 1194, it can go out of IP 1. When a conection comes in on port 1195, it can go out of IP 2. And u can just have a 2nd client.conf file, and in the 2nd client.conf will be the directive to connect to port 1195 instead of 1195. Much simpler than the code I was about to give you. And less intrusive too. Wont have to change too much. Thank you for clarifying before it got any futher. I see you're tracking this thread eagerly, which is great.. just gotta let u know, I will be AFk for bout 30 mins.

One OpenVPN for Multiple IPs

Bebop

Done. Works. See 3 posts up.

Mimiko

sens0r
I didn't really understood thru all the conversation what you mean to do. With you want to connect only yourself to same server which have two different public IP, there are two things. If it's for fault tollerance, then in your client configuration just add two "remote" options with different public IP of the server. If you intentional whant to connect to different IPs on your behalf, then from clients configuration remove any "remote" option, and start OpenVPN client with command line parameter "--remote" where you place your desired public IP. You can make to shortcuts to OpenVPN client, one with one IP, other with secod IP.

Bebop

Mimiko wrote remove any "remote" option, and start OpenVPN client with command line parameter "--remote" where you place your desired public IP

That wont be enough in this case, because the exit IP is determined by IPTABLES post routing SNAT commands (regardless what IP you type for --remote).

This case is already solved. Just waiting for confirmation that sens0r has got it working.

Mimiko

That wont be enough in this case, because the exit IP is determined by IPTABLES post routing SNAT commands (regardless what IP you type for --remote).

Hm, why should use IPtables on client mannualy or how is that? A lot is in linux and I can't figure out how it is working.

Yes, you done the job. )) I prefer o keep as simple as possible, that's for my perspective, manually selecting IP to which to connect seemed simpler. ))

Bebop

Mimiko wroteHm, why should use IPtables on client mannualy or how is that? A lot is in linux and I can't figure out how it is working

If you need some help with Linux, it might be better that you start a new thread.

sens0r

Hi Bebop thanks for your efforts.

I'm a little confused though, from what I've seen in your post, I think your method would only allow multiple users to use ONE static IP right? Because I don't see anywhere that you have mentioned anything about a second VPS static IP.

Maybe you really didn't understand what I was trying to do. I simply wanted myself to be able to choose which of the two available VPS static IPs to use when connected through the OpenVPN.

Bebop

sens0r wroteHi Bebop thanks for your efforts.

I'm a little confused though, from what I've seen in your post, I think your method would only allow multiple users to use ONE static IP right? Because I don't see anywhere that you have mentioned anything about a second VPS static IP.

Maybe you really didn't understand what I was trying to do. I simply wanted myself to be able to choose which of the two available VPS static IPs to use when connected through the OpenVPN.

My understanding of your problem is this:

You have 1 (one) VPS
Your VPS has 2 (two) WAN Ips
According to the guide you followed, this VPN is used as a tunnel
You want to choose which IP you exit the tunnel with
eg: if you visit http://www.whatismyip.com you can see the VPS IP 1 or VPS IP 2 depending which one you want to tunnel with.

If this is not what you described then I apologize for not understanding. please do claify. You use the phrase

which of the two available VPS static IPs to use

That is a very ambiguous phrase because you can 'use' IP's to enter OR exit the tunnel. What do you want to do?

Mimiko

Oh, Bebop, girls are always right. :lol:

sens0r:

I simply wanted myself to be able to choose which of the two available VPS static IPs to use when connected through the OpenVPN.

Which I stated to create two shortcuts with different "--remote" command line options. sens0r see my post before.

Bebop:

You want to choose which IP you exit the tunnel with

Interesting aproach, Now I understood what was that all about. Like load ballacing clients to different IPs to get internet access.

sens0r

I'm not sure why you guys are confused about this, maybe because I am a newbie and not so good at explaining technical things.

Both of you are correct at some points and wrong at some. So I will try to explain this one more time 😃

I bought a VPS and installed CentOS on it, then I installed OpenVPN on it with the aforementioned guide.

Now my VPS comes with 2 different static IPs

1) 123.123.123.120

2) 123.123.123.121

When I first configured OpenVPN I used "123.123.123.120" to connect to the internet but now I want to utilize the second IP "123.123.123.121" as well.

Since there is only going to be one user (Me) who is going to connect to my VPS and use the OpenVPN connection, I don't have to worry about multi users or multi load on the system.

Now when I start my OpenVPN Gui and press connect, I want to be able to choose which IP to connect to the internet with, let's suppose I connect with "123.123.123.120", I want the whole of my internet including emails to use this IP. Then if required I would disconnect from this IP and connect with the second IP "123.123.123.121" and vice versa.

You see I will only be using one user/pass combination but I want to be able to choose which IP to use to access the internet through OpenVPN.

Can this be done? If so what's the most efficient way to do it 🙂

Thanks!

Bebop

sens0r wrote I want the whole of my internet including emails to use this IP

Thank you for clarifying. This is what I understood you meant, so this is the solution I delivered to you twice. One option will give you an external IP based off your username. The other will base it off your .ovpn file. There is no easier method than those described.

sens0r

I am not to sure as this all looks a bit confusing to me :?
I will give it a try and post back when possible 🙂

Thanks!

Bebop

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

sens0r

I have been successful in utilizing both the IPs, I used a combination of the original guide which I linked to and your implementation method and got it to work.

Although there are a few things which I did different than your instructions and I will let you know about them soon enough :lol:

Thanks again, will be back later :mrgreen:

Bebop

sens0r wroteI have been successful in utilizing both the IPs, I used a combination of the original guide which I linked to and your implementation method and got it to work.

Although there are a few things which I did different than your instructions and I will let you know about them soon enough :lol:

Thanks again, will be back later :mrgreen:

Well done. Lets see what you came up with. Glad that saga is finally over :twisted:

ecrist

You can have openvpn listen on multiple IPs with multiple --local arguments in your config or on the command line.

sens0r

I'd like to bring this thread back from the dead.

I'd like to know how can I add the config files to the startup of my server. Meaning when the server reboots, I want the config files to start with the boot.

For instance I want it to automatically execute this command on each VPS reboot:

openvpn /etc/openvpn/1199.conf

I have about 9 of these conf files and I want to make them run in the background as well.

Thanks in advance!

« Previous Page