LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26524 Commits
1 Branch
46 MiB
Tree: bb801a5a6f
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'bb801a5a6f'
${ noResults }
openwrt-packages-dist/net/jool/files/jool-siit.conf.json

47 lines
1.1 KiB
Raw Normal View History

jool: update to 4.1.6, add init files and default configuration This commit adds support for starting and running jool through init scripts, with default config files as examples. Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com>
3 years ago
​
​
​
​
​
​
​
​
jool: remove iptables support and update templates 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>
3 years ago
​
jool: update to 4.1.6, add init files and default configuration This commit adds support for starting and running jool through init scripts, with default config files as examples. Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com>
3 years ago
jool: remove iptables support and update templates 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>
3 years ago
​
​
​
​
jool: update to 4.1.6, add init files and default configuration This commit adds support for starting and running jool through init scripts, with default config files as examples. Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com>
3 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
jool: remove iptables support and update templates 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>
3 years ago
​
jool: update to 4.1.6, add init files and default configuration This commit adds support for starting and running jool through init scripts, with default config files as examples. Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com>
3 years ago
​
​
​
​
 
  1. {
  2. 	"comment": "Sample full SIIT configuration.",
  3. 

  4. 	"instance": "instance name",
  5. 	"framework": "netfilter",
  6. 

  7. 	"global": {
  8. 		"comment": "pool6 and the RFC6791v4 pool belong here, ever since Jool 4.",
  9. 		"pool6": "64:ff9b::/96",
  10. 		"manually-enabled": false,
  11. 		"zeroize-traffic-class": true,
  12. 		"override-tos": false,
  13. 		"tos": 254,
  14. 		"mtu-plateaus": [1, 2, 3, 4, 5, 6],
  15. 		"amend-udp-checksum-zero": true,
  16. 		"eam-hairpin-mode": "simple",
  17. 		"randomize-rfc6791-addresses": false,
  18. 		"rfc6791v6-prefix": null,
  19. 		"rfc6791v4-prefix": null
  20. 	},
  21. 

  22. 	"eamt": [
  23. 		{
  24. 			"comment": {
  25. 				"text": "Here's a compound comment.",
  26. 				"more": "Its type is not checked, after all.",
  27. 				"date": "2019-01-06",
  28. 				"whatever": 1234
  29. 			},
  30. 			"ipv6 prefix": "2001:db8:1::/128",
  31. 			"ipv4 prefix": "192.0.2.0"
  32. 		}, {
  33. 			"ipv6 prefix": "2001:db8:2::",
  34. 			"ipv4 prefix": "192.0.2.1/32"
  35. 		}, {
  36. 			"ipv6 prefix": "2001:db8:3::/124",
  37. 			"ipv4 prefix": "192.0.2.16/28"
  38. 		}
  39. 	],
  40. 

  41. 	"comment": "This comment is relevant to denylist4 maybe.",
  42. 	"denylist4": [
  43. 		"198.51.100.0",
  44. 		"198.51.100.2/32",
  45. 		"198.51.100.32/27"
  46. 	]
  47. }