proxmox-mirrors/pve-firewall
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-firewall synced 2025-08-06 18:39:57 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
master
pve-firewall/test
History
Thomas Lamprecht 29e5ce1536 test/simulator: add very basic ICMP type functionallity 
For now without integer to full-name, and vice versa, mapping of
ICMP types.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2020-05-04 14:10:55 +02:00
..
test-basic1 test/simulator: add very basic ICMP type functionallity 2020-05-04 14:10:55 +02:00
test-default-rules1 Update and add tests for corosync firewall changes 2019-07-02 09:05:44 +02:00
test-errors1 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-errors2 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-errors3 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-errors4 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-group1 adopt regresion tests for lxc containers 2015-08-12 11:59:18 +02:00
test-ipset1 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-ipset2 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-unconfigured return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-vm-aliases1 return empty ruleset if firewall disabled in cluster.fw 2014-06-04 07:24:34 +02:00
test-vm-ipfilter1 add regression tests for ipfilter 2014-06-12 08:32:11 +02:00
test-vm-ipfilter2 test: add test for implicitly allowed container IP 2016-03-03 09:42:46 +01:00
corosync.conf Only include multicast rules if transport is udp 2019-07-02 09:05:44 +02:00
fwtester.pl fwtester: reduce extra empty lines a bit 2020-05-04 14:09:53 +02:00
Makefile add Makefile targets for regression tests 2014-05-13 14:18:08 +02:00
README test/README: whitespace fixes and slight rewording 2020-05-04 13:52:44 +02:00

README 

= A simple simulator to test our iptables rule generation =

== Invocation ==

 # ./fwtester.pl

This scans for subdirectory named test-* an invokes fwtester.pl for each
subdirectory with:

 # ./fwtester.pl test-<name>/tests

== Test directory contents ==

Each test directory can contain the following files:

 * cluster.fw  Cluster wide firewall config
 * host.fw     Host firewall config
 * <VMID>.fw   Firewall config for VMs
 * tests       Test descriptions

== Test description ==

The test description file can contain one or more tests using the following
syntax:

 { from => '<zone>' , to => '<zone>', action => '<DROP|RECECT|ACCEPT>', [ source => '<ip>',] [ dest => '<ip>',] [ proto => '<tcp|udp>',] [ dport => <port>,], [ sport => <port>,] }

The following <zone> definition exist currently:

 * host:              The host itself
 * outside:           The outside world (alias for 'vmbr0/eth0')
 * vm<ID>:            A qemu virtual machine
 * ct<ID>:            An openvz container
 * nfvm:              Non firewalled VM (alias for 'vmbr0/tapXYZ')
 * vmbr<\d+>/<bport>: Unmanaged bridge port


== Test examples ==

 { from => 'outside', to => 'ct200', dport => 22, action => 'ACCEPT' }
 { from => 'vm101', to => 'vm100', dport => 443, action => 'ACCEPT', id => 'vm2vm'}

You can assign an 'id' to each test, so that you can run them separately:

 ./fwtester.pl -d test-basic1/tests vm2vm