-
-
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
Support for *BSD #35
Comments
Note about FreeBSD: We need to recompile the kernel with options:
|
$500 bounty! Submit a pull request and email [email protected] to claim it. Partial solutions may be rewarded. |
So just to get this right. If i get this server running on OpenBSD I can make 500 bugs? Just want to know, so I will give it a try. |
@PolymathMonkey Just getting Algo to deploy properly on OpenBSD would probably be considered a partial solution but may still be awarded. I would think that it would be considered a full solution when you are able to deploy *BSD to at least one cloud provider just as you currently can with Ubuntu 16.04. This means, ensuring available images on at least one provider with appropriate kernel options for deployment, etc. I'd be willing to throw some of the bounty rewards associated with my contributions towards a fully working solution on AWS if @dguido has no objections to that. |
Yep! At minimum, it needs to be a port of the essential features: the common and VPN roles. You need to make a PR that integrates these features into the codebase. Either @gunph1ld or @defunctio need to review the PR to accept it. I'll consider rewarding partial solutions with partial credit. Does DigitalOcean have hosted OpenBSD images? I know they have FreeBSD. |
Don't know if they have OpenBSD. I know at least AWS has obsd images (5.9) , but still have to take a look to get a overview of the scope of the Project. But in general if there are no short time frames to complete the bounty. I would give it a try, I love bsd and the idea of the challenge of implementing a cloud image plus get the algo code running.. |
@PolymathMonkey I don't believe there is a time-frame for completion. As far as I know, these are just like any other bounties to incentivize advancing an OSS project but I don't work for ToB so don't hold me to that ;) +1 for HardenedBSD |
No timeframe! I think @gunph1ld had his eye on this one too though :-P |
I would only try to do the obsd stuff ^^. But I am always in for cooperating on projects depends on @gunph1ld . If he wants to to this on his own I would step to the aside, but I would enjoy working on |
Yeah try it! Jack had his hands full with a dozen other issues. Give it a shot. |
I'll give it a go on FreeNAS (FreeBSD) |
I'm a bit busy with a few things at the moment, but I could set up a little test cluster on HardenedBSD. I've got 2-3 servers sitting around that I could deploy this on to. I'll keep you updated as to my progress. Might take a couple weeks, though. |
@lattera Much appreciated! |
:\ sorry guys have to cancel my participation in this project (@openbsd implementation). Because some other topic is consuming all my time right now |
Update: I haven't forgotten about this. I should be able to start work on testing in early 2017. Got really sick twice in a row, preventing me from working on this. |
FreeBSD:
|
ifconfig fix Pre-tasks fixes fix hardcoded IP some refactoring disable system-based tags disable freebsd tags FreeBSD vpn role #35 add defaults ssh role freebsd default fix dns_adblocking freebsd ubuntu dict fix
HardenedBSD:
|
ifconfig fix Pre-tasks fixes fix hardcoded IP some refactoring disable system-based tags disable freebsd tags FreeBSD vpn role #35 add defaults ssh role freebsd default fix dns_adblocking freebsd ubuntu dict fix
ifconfig fix Pre-tasks fixes fix hardcoded IP some refactoring disable system-based tags disable freebsd tags FreeBSD vpn role #35 add defaults ssh role freebsd default fix dns_adblocking freebsd ubuntu dict fix
ifconfig fix Pre-tasks fixes fix hardcoded IP some refactoring disable system-based tags disable freebsd tags FreeBSD vpn role #35 add defaults ssh role freebsd default fix dns_adblocking freebsd ubuntu dict fix
in addition:
|
I tried installing under FreeBSD 11.1-RELEASE-p1 however were unable to complete the installation, it seems to fail rebuilding the kernel. When researching the problem I found a reference from strongSwan saying that recompilation for NAT_T isn't needed anymore in 11.1. However IPSEC_NAT_T is not preset in the kern conftxt
I also tried recompiling the 11.0 kernel manually with source from https://svn.freebsd.org/base/releng/11.0 using the following KERNCONF
But neither this granted me any acces as it fails when compling nvme
I have no previous experience with writing ansible scripts so I'm not sure how to modify the script to continue the installation without IPSEC_NAT_T, I suppose this could still work according to strongswan documentation. I've attached the install log from ansible when trying to install below. This is a fresh install and I've only installed some basic tools such as tmux before trying the ansible deploy of algo.
|
@dguido FreeBSD 10.4 is released now, maybe someone should consider updating the scripts to work with newer kernels. I've never written ansible scripts previously so I don't think I could provide code of good quality but can atleast add that I managed to hack the current scripts to ignore the NAT-T kernel extension which is now built in since 11.1 but I don't think so is the case for 10.4 so someone with a little more experience should probably write a conditional based on output of Pseudo code
|
Please note that as of revision 315514, IPSec support has been substancially changed, so the setup for FreeBSD might have to be changed a bit. |
I have gotten this to work with some workarounds. I am deploying directly on a Digital Ocean a FreeBSD11.1 droplet.
|
@jackivanov Why was this closed? Is it working in new FreeBSD-releases now? Or are you dropping support for FreeBSD? Or is it replaced by another issue? |
Oh sorry, it was accidentally. An update is coming in this PR which closes the issue |
Ah great to hear, I was afraid that you were silently dropping support for *BSD. |
Particularly interested in FreeBSD, HardenedBSD, and OpenBSD.
The text was updated successfully, but these errors were encountered: