Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working on Scaleway servers #138

Closed
angristan opened this issue Mar 13, 2016 · 12 comments
Closed

Not working on Scaleway servers #138

angristan opened this issue Mar 13, 2016 · 12 comments

Comments

@angristan
Copy link

Installation is successful but the traffic is not routed trough the server.

More info here : https://community.scaleway.com/t/i-dont-have-a-working-vpn/1790

@Nyr
Copy link
Owner

Nyr commented Mar 13, 2016

The thread doesn't actually have any information at all, more like disinformation.

You can also see that it's working for others, so you could probably consider that this issue could be in your end and not a problem with the script or Scaleway.

Still, I have just created one Scaleway instance to check for you, and it works. I wanted to check on the ARM servers too, but they are likely out of capacity and wouldn't let me get one so I just tested with the Avotons.

@Nyr Nyr closed this as completed Mar 13, 2016
@Nyr
Copy link
Owner

Nyr commented Mar 13, 2016

It could be that you just didn't set up the NAT correctly.

You need to specify the internal IP address on the first installation step (which is there by default) and then specify the public one when asked later.

@angristan
Copy link
Author

You need to specify the internal IP address on the first installation step (which is there by default) and then specify the public one when asked later.

Later ? It only asks one time for the IP adress.

So I have to keep it this way ?

First I need to know the IPv4 address of the network interface you want OpenVPN
listening to.
IP address: 10.2.0.215

@Nyr
Copy link
Owner

Nyr commented Mar 13, 2016

Try to actually READ what the script is asking you for:

First I need to know the IPv4 address of the network interface you want OpenVPN
listening to
.

Do a ifconfig and check what's the freaking IP address assigned to the network interface (eth0).

If you specify the right IP you are asked for, the script will later detect the NAT and ask you for the public IP and will work perfectly.

I now see you haven't even bothered to read the script at all and look at how it works. I would consider this reasonable except for the fact you are actually maintaining a fork of this script which you apparently don't even understand.

So please, refrain from opening any issue in the future.

@angristan
Copy link
Author

I am not familiar with NAT, sorry.

So when I see :

First I need to know the IPv4 address of the network interface you want OpenVPN
listening to.

Why would I put a private IP ??

Now I understand, it explains a lot ^^

The noob apologizes

@Nyr
Copy link
Owner

Nyr commented Mar 13, 2016

Why would I put a private IP ??

Because it is the actual IP address assigned to the interface, which is what the script is asking about.

@angristan
Copy link
Author

Yep that's right, no public IP on ifconfig ^^

@angristan
Copy link
Author

(I'd just like to point out that I wasn't the only one confused with Scaleway) #112

@Nyr
Copy link
Owner

Nyr commented Mar 14, 2016

The right IP address is detected by default and user needs to manually break the configuration for it to fail.

Not my problem if people doesn't read what they are asked about.

@BrainBlasted
Copy link

The right IP address is detected by default and user needs to manually break the configuration for it to fail.

I have run the script more than once, changing absolutely nothing, using an Ubuntu 17.04 droplet. Now, the IP detected by the script matches the inet section in eth0. Is that the correct configuration?

@BrainBlasted
Copy link

Running the iptables commands in #92 results in an empty output.

@Nyr
Copy link
Owner

Nyr commented Feb 22, 2018

@BrainBlasted you are using an EOL distribution and as such, is not supported. But yes, the instructions in this thread still stand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants