-
-
Notifications
You must be signed in to change notification settings - Fork 285
Multi IP troubles #3883
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
Comments
The IP on the VPS part should be correctly configured first. You can check with a |
I was trying to ping. It turns out that the computer goes online from the first IP and knocks on the second IP. |
Not sure to really understand what you mean by knocks. VPS IPs answer to ping at least from external ? |
By "knocks" I mean sending packets. I want to understand if the VDS needs to be configured somehow in order for multiple IP to work. I saw that |
I'm not sure to understand, if multi IPs are available and working on first VPS script install, shadowsocks-libev is configured on VPS and when server key is set on router it's also configured on router. |
Yes, I realized after a while. I first installed MPTCP on a VDS with a single IP. Later, I added another IP to the server. And the reconfiguration did not happen. I have now reinstalled the operating system on VDS and run the installation script. Today I'm going to the garage and try to set it up directly on the router. I'll write it off based on the results. It might be worth making a system reconfiguration tool. |
Expected Behavior
I am trying to set up multiple white IP addresses as mentioned in the article https://github.com/Ysurac/openmptcprouter/wiki/VPS-Multi-IPs. I have several computers on my network. I want all devices on the network to connect to the network from the first IP by default, and one of the computers to connect to the network from the second IP.
Current Behavior
Here are my current settings.
I've read previous reports about similar issues. Here are also the VDS network settings.
Also, here is the output result of the command

netstat -laputen | grep ss-server
For some reason that I don't really understand, the computer I need still accesses the Internet from the first IP, and not from the one I expect. I suspect that the problem is with configuring the network interface on the VDS side. I tried to set it up correctly, but it didn't work out.
Specifications
The text was updated successfully, but these errors were encountered: