28ac3a6997
This commit removes iptables backend support and leaves only the netfilter backend support. This means that: - iptables and nftables firewall based systems (firewall3 and firewall 4) are supported trough the netfilter instance mode - the iptables/xtables mode support is disabled For more information on the modes and how to use the new netfilter instance checkout https://www.jool.mx/en/intro-jool.html This move is made out of the commit upstream that sets firewall4 as the default for new default buils and based on the conversation in #16818 and was decided that the netfilter interface is the priority since iptables support will be dropped in the foreseeable future. While at it update the templates provided. Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com> |
||
|---|---|---|
| .. | ||
| jool-nat64.conf.json | ||
| jool-siit.conf.json | ||
| jool.config | ||
| jool.init | ||
| readme.md | ||
Jool
Documentation
You might also want to see contact info.
Usage
Start script
This package includes a start script that will:
1. Read the configuration file /etc/config/jool
2. Determine what services are active
3. Run jool with procd
For now this means that:
* The services will be disabled by default in the uci config (/etc/config/jool)
* The only uci configuration support available for the package is to enable or disable each instance or the entire deamon
* There is no uci support and configuration will be saved at `/etc/jool/*
* Only one instance of jool(nat64) can run with the boot script
* Only one instance of jool(siit) can run with the boot script
* For now there is no way of overriding of the configuration file's paths
The configuration files the startup script useses for each jool instance are:
* jool(nat64): /etc/jool/jool-nat64.conf.json
* jool(siit): /etc/jool/jool-siit.conf.json