NethServer 6

Please, note that the custom templates add a dhcp option to interfaces.

We should probably open services running on the firewall from blue.
And review all inter-zone traffic policies.

Meanwhile, to open dns from blue:

cat <<EOF >/etc/e-smith/templates-custom/etc/shorewall/rules/99dnsmasq_blue

?COMMENT dnsmasq blue
ACCEPT blue $FW tcp 53
ACCEPT blue $FW udp 53
EOF

We should probably open services running on the firewall from blue.
And review all inter-zone traffic policies.

Special property AllowHosts was developed with this scenario in mind.

For example, given a configuration GREEN+BLUE, where blue network is 10.0.1.0/24.
We want to open DNS access from blue network:

config setprop dnsmasq AllowHosts 10.0.1.0/24
signal-event firewall-adjust

• new database dhcp
• each record of type range has following properties:
  • key: associated interface name
  • status: can be enabled or disabled
  • DhcpRangeStart: first IP address of DHCP range
  • DhcpRangeEnd: last IP address of DHCP range
  • DhcpLeaseTime: seconds of lease time. Default is 8640
  • DhcpGatewayIp: (optional) set a custom gateway ip. If not set, the gateway is the ip address of associated interface (record key)

In the future, the range record can be extend with extra options, like custom DNS/WINS server, etc.

We also need to do a big refactor on web interface, maybe a solution is to split DNS and DHCP configuration into separate pages.

• add a "DHCP server" inside the "network configuration"
• the new section should be specified for each interface with a role

• the new section should be specified for each interface with a role

Do you really need a dhcp server on every role? I think that green and blue are the only zones that need dhcp.

And dhcp should work out of the box, i.e. the AllowHosts should be automatic.

DNSMasq it's probably the only special case where ports should be automatically open on blue zone if the DHCP is enabled.

For all other services, use AllowHosts property.