Write your configuration in the file called config.json
where you run Route ArcEnCiel. Your configuration will contain two tables :
{
"vlan": {
"<vlan_number>": "<vlan_subnet>",
...
},
"vpn": {
"<table name>": "<vpn_subnet>",
...
},
"iface_prefix": "<iface prefix>"
}
where :
<vlan_number>
is a number, like101
or150
, used to determine the name of a network interface.<vlan_subnet>
is a subnet in the likes of172.16.18.0
. All of the machines with an ip address on the VLAN should have an ip in that range.<table_name>
is the name of an ip rule table. Commonly, they correspond to the names of the hosts they are associated with. These tables should be set in another script.<vpn_subnet>
is the subnet of the VPN, like10.8.34.0
.<iface prefix>
is the prefix for all network interfaces, minus the '.' (eg. "eth0" for "eth0.1", "eth0.2", "eth0.3", etc).
It is important that all subnets be written with only one digit after the last period, otherwise some string slicing boondongery in Route ArcEnCiel will not work.
Simply pipe the output to your favourite capable shell. Even error messages are written as echo
commands, so don't worry.
./route_aec | sh