-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Ubiquiti EdgeMax configuration #307
Comments
I just started looking at this too and found these community discussions that may be helpful: |
Also very interested in this. On a side note, I wasn't even entirely sure this router would support Algo. The only thing I wasn't able to confirm after talking with Ubiquiti's support was support for ECDSA certificate keys. I did, however, find this in the release notes for version 1.8.0 of EdgeOS (it's currently on 1.9.1):
This tells me it can support it with the latest versions of EdgeOS, but once I get mine I'll test it out. |
I found this which I think is what we need, but I'm far from a networking guy so I'm not sure. |
This is as close as I got to getting it working. I tried starting Output of
My directory structure for certs/keys/etc on my EdgeRouter Lite:
Perhaps I'm missing some files/permissions? Any help would be greatly appreciated. |
Got super close last night. It tried installing a new virtual ip on my EdgeRouter, but then right after I lost all internet and LAN access. I configured all of this using My hardware setup:
Can someone else try this and let me know? Some resources, some of which I still have to try):
Output of
Here's the updated directory structure:
ipsec.conf:
|
Thinking it has to be some sort of issue with firewall or NAT rules. :( |
I added a bounty. Check the first post in this issue. You can add to the funds by clicking the badge there. |
Added $100 bounty. |
I was able to get strongSwan to load the certs and the ecdsa key with some adjustments. I copied ipsesc.conf and ipsec.secrets to /etc/, but in ipsec.conf I changed the In ipsec.secrets I made a similar adjustment. I also changed After pubkey: ECDSA 256 bits, has private key And I haven't been able to ping across the tunnel or otherwise do anything useful with it, but at least it seems to authenticate correctly.
|
Adding this iptables rule enables me to ping/ssh to a private ip address on my algo ec2 instance:
I'll try setting |
@chriseldredge @ebcodes Something like this:
|
@gunph1ld @chriseldredge
|
In my latest attempt, I tried setting this up using the EdgeOS (VyOS) CLI. I'm not touching it for tonight as it's not working (not tunneling traffic). If anyone needs more info I'm happy to provide it. I added the suggestion from @gunph1ld from above for the The routing structure was a bit different this time: I didn't want to piss my roommate off fucking around with this thing all night (already spent 6 hours on it...). While I like the idea of IPSEC and it's security, I'm about ready to move on from it if it's going to be this hard to set it up. Anyway... Structure:
Here are my current configs. This was attempted using 1.9.7alpha1 of the EdgeMax router firmware for ER-Lite.
Directory structure for certs/keys:
|
@gunph1ld the suggestion to set routing_table to 0 seems to have helped:
When I start the VPN connection my EdgeRouter will route traffic originating from the local server through the tunnel successfully. In effect this means that DNS is being routed through VPN. However, traffic from my LAN is being routed by default route through ISP and not getting passed through VPN tunnel. GRE/ipsec configuration may be necessary to complete the configuration. |
(Edit - fixing some subnets and iptables rules to tighten things up) I have it working end to end. Router /config/config.boot Algo Server ipsec.conf
Serverside iptables changes
Router home_ipsec.conf (referenced in config.boot)
|
@kiratp and I spent a long time tonight setting this up and I managed to get a tunnel working on my ERL! There's still plenty to do, however, to get this working fully:
kiratp and I will be playing around with this again next weekend, but for now, at least something works! Hats off to @kiratp for being so patient and helpful tonight. Thank you! |
@mister2d - More the merrier! Just jump on the Algo support Slack. The next issue I am working through as a P1 is Hardware Offload. Something about the tunnel is breaking offload (capped at 9 Mb/s vs 30Mb/s sw-only) |
#473 - PR to make this easy |
@kiratp Thanks for getting a fix in for this! I'm using your PR but not having much luck. The tunnel comes all the way up and I have DNS/routing from the EdgeRouter itself via my AlgoVPN endpoint. I also have access to local LAN resources on my 192.168.1.0/24 network. However, I cannot ping my EdgeRouter .1 from my LAN or route any traffic through the VPN from any device in 192.168.1.0/24 other than the EdgeRouter itself at .1. Below is most of my config. Any ideas? This seems rather strange. Almost as if the passthrough mode is working for everything but the .1 address. EDGE ROUTER
Edge Router XFRM Policy
EDGEROUTER ROUTES
ALGOVPN ENDPOINT IPSec Conf
ALGOVPN ROUTES
ALGOVPN XFRM Policy
|
Closing this issue as solution referenced in #473 is good enough. |
Anyone who tried out the PR from @kiratp have any objections to paying out the bounty? |
@dmwyatt: do we have a good idea of how to get HW acceleration working so an ERL can at least sustain 100 MBit/s? #473 also mentions routing breaking when multiple clients connect to the VPN. Until these issues are addressed I wouldn't use my ERL with Algo VPN. Your initial ask didn't mention any reliability or performance requirements so I think it is reasonable to pay out the boundy. How is it working out for you? Do you have it enabled and are you happy with it? |
@ndfred - there is a thread on the UBNt forums about the offload issues - https://community.ubnt.com/t5/EdgeMAX/IPSec-performance-issue/m-p/1946992#M162999 I've been helping folks with routing on Slack - happy to help there. The issues I've seen seem to seem to stem from manually configured routing rules (xfrm), overlapping subsets etc. I will refactor the PR once the new modular client support is released. Thanks for releasing the bounty folks! |
Anyone have any ideas or advice on how to configure an EdgeRouter Lite to send all internet traffic on LAN through the algo server?
Specifically, I'm looking for step-by-step instructions to enable my EdgeRouter Lite to route all internet traffic on my LAN through my algo VPN instead of the open internet.
Here's my thread on the ubiquiti forums linking to this issue.
The text was updated successfully, but these errors were encountered: