Hi Rutri,
I, like
poundjd (Jeff) am exploring eBox and may be able to offer some (limited) help.
Jeff's suggestions are good advice as they are widely implemented by eBox users. My requirements were quite close to those described in your opening post. By design, eBox is quite capable of accommodating different set-ups and provided a suitable answer to my needs. In essence this was to use the router/switch as a gateway to the LAN and leave functions such as the firewall etc there also.
The alternative approach is shown here:
http://forum.ebox-platform.com/index.php?topic=1233.0It is quite a long thread and deals with the following main ideas:
- Moving DHCP from a multi-function router/switch to an eBox (relevant posts #1-#4)
- Segmenting/reserving the address space in DHCP (irrelevant posts #4-#38)
- Accessing the WAN/web from the eBox (relevant posts #39 onwards)
Also of interest might be the LAN topolgy diagram (post #48)
A broad outline is:
Module Status SectionEnable the eBox modules you require
Network Section-->InterfacesAssign a static IP Address to the eBox NIC
Network Section-->GatewaysCreate a gateway to the LAN IP Address of the router
Set as default
DHCP SectionDefault Gateway=Configured Ones
Primary Nameserver=IP Address of router
Define a DHCP range to be allocated if you decide to use eBox as your DHCP server.
As far as VPN is concerned I cannot offer any suggestions as I have not explored eBox for this. Other users on the forum may be able to assist with this, however they may be expecting eBox to be set up in the manner suggested by
Jeff.