Digital Ocean VPC

[jonathan-wondereur]

I am able to set up my server on Digital Ocean and it works fine to connect to the internet, however I can not access servers on the same VPC as my Algo/Wireguard server.

I have set up BetweenClients_DROP: false but it still does not work, is there anything else that needs to be changed?

[davidemyers]

This might not be relevant, but are you using:

alternative_ingress_ip: true

[jonathan-wondereur]

After looking a bit more, it does not really work. Well it does, but it makes my traffic not come from the alternate ingress IP address.

[davidemyers]

Right, the change I suggested is the rule that would be used if you deployed a new server with:

alternative_ingress_ip: false

The alternate address feature is apparently incompatible with DigitalOcean VPCs.

[jonathan-wondereur]

That is unfortunate ... I guess I can just try deploying a few times with this turned off to see if I can get a DO IP address (not static) that is not blocked by Google Scholar etc ... I find addresses starting with 159.203seem to be blocked ...

[fvanderelst]

Hi - I have the same issue with EC2. With altenative_ingress_ip: false, BetweenClients_DROP: false, I can't seem to ping, nor SSH, another VM in the same security group, in the same subnet.

This is true from the Algo VPN VM itself, or from my laptop (mac) with the Wireguard vpn activated. Access to the public internet works, just not in-VPC.

Happy to contribute my config.cfg and iptables rules.v4.

iptables -vL doesn't show any DROPped packets.

Thank you for you great work !

[Update] : enough rebooting and this works. Thank you... Freddie

[jonathan-wondereur]

BTW @fvanderelst I have switched to Tailscale I find it is much easier to set up more flexible and powerful.