Replies: 2 comments 5 replies
-
You found https://freetz-ng.github.io/freetz-ng/wiki/60_Development/ ? Old but should still help. |
Beta Was this translation helpful? Give feedback.
-
So 1st your package should build in in source/ . And then the needed! files should be copied to packages/ |
Beta Was this translation helpful? Give feedback.
-
as stated in a previous discussion - I'm trying to integrate strongswan into freetz as it looks a lot better than default AVM IPSEC tunnel config (IKEv2, sha512, dh groups, ipv6, etc ...).
I think these options would be fine in the config script:
(off course, I could eventually expand it in further revisions, but let's stick to the basics right now).
Anyway, the setup creates a lot of libraries + config files + executables in src/(dir)/(file), which should be put somewhat like this:
so, a few questions:
a) what should I do with all those config files? most of them can be narrowed down to ipsec.conf, swanctl.conf and strongswan.conf. ipsec.secrets is something to configure via a yet-to-be-written web frontend, and subdirs could be merged with appropriate file in /etc (I guess)
b) what should I do with all those libs + binaries? strongswan has 2 options which could help placing them, but what's a good location?
also: when playing a bit with the options, and running make install, eg:
$(SUBMAKE1) -C $(STRONGSWAN_DIR)/src/charon install DESTDIR="$(STRONGSWAN_DEST_DIR)"
it replies with:
libtool: error: 'packages/target-mips_gcc-8.3.0_uClibc-1.0.36-nptl_kernel-4.9/strongswan-5.9.1/rootpackages/target-mips_gcc-8.3.0_uClibc-1.0.36-nptl_kernel-4.9/strongswan-5.9.1/root/usr/sbin' must be an absolute directory name
Beta Was this translation helpful? Give feedback.
All reactions