openslx-ng/tm-scripts.git - Scripts for preparation and extraction of components on the reference machine. Part of Taskmanager.

	Commit message (Collapse)	Author	Age	Files	Lines
*	woopsie, the return ;)	Jonathan Bauer	2014-03-25	2	-14/+0
\|
*	[modules] new module naming convention	Jonathan Bauer	2014-03-25	2	-0/+14
\| \| \| \|	rename $MODULE.{conf,build} to module.{conf,build}
*	[iptables-helper] Use -w everywhere to prevent race conditions	Simon Rettberg	2014-03-10	1	-21/+30
\|
*	[iptables-helper] Put everything in a dedicated chain so we don't interfere ↵	Simon Rettberg	2014-02-17	1	-3/+27
\| \| \| \|	with other tools writing rules directly
*	[iptables-helper] Simple helper scripts/service for handling iptables rules	Simon Rettberg	2014-01-17	7	-0/+106
	This adds no fancy features or new syntax or anything, but merely helps to manage a .d directory for iptables scripts. You simply write simple shell scripts where you issue your iptables calls and place them in /opt/openslx/iptables/rules.d On bootup, and whenever the contents of the directory change, all tables will be reset and the scripts from rules.d are run. They're run in alphabetical order, so it's wise to adhere to the XX- naming scheme. Also you can place any kind of script there doing really complicated things, it's advised you keep them as simple as possible and use proper names, that tell what the script does. The default behaviour is set to ACCEPT on all tables/chains, but nothing stops you from doing 'iptables -P' in one of the scripts.