**Feature Request within** another option would be let the DCE be the DHCP server and hack the DHCP config file to have it give out the router as the Gateway instead of itself (and obviously have them with the same IP scheme). it would be nice as a built in feature of the DHCP web configuration to manually define the gateway with out hacking the file as a way to dumb things down for the average user.
I think MCE is a great product, but we have to get some of this stuff more friendly to the average n00b or id10t user other wise they will stay in Bill Gates cult. I think a small network config script that they can ask if this will be the DHCP server AND the GateWay also might make that easier.
I'm personally onboard with the people that want a separate router for security reasons. I'd rather a separate router be out front to be hacked instead of a system that controls my whole house. I use IPCOP and can port forward what I need to make the features work if I know all the ports. I would accept using LMCE as my router also if the DHCP and firewall were more configurable (need my VPN specially). maybe someone can fork IPCOP and plug it in as LMCEs firewall.
There are going to be two net topos for LMCE deployments: an entry level setup with no IP PNP net devices, often on a reused existing PC HW to try it out with just the existing single NIC, and an existing DHCP and router. With no IP PNP devices to support (excluding storage shares, which don't need LMCE DHCP), LMCE does not need to be the DHCP server. LMCE never really needs to be the router (even the 2-NIC default can sit behind a separate router on the outside LAN segment), though of course firewall features do require 2 NICs. When people want to support IP PNP devices, they can upgrade to a 2-NIC PC or install a second NIC, though some people will start with that full version.
So yes, the LMCE Network Settings page should expose the dhcpd.conf "routers" (and maybe even the "next-server" for hosting the bootfile outside the Core) option that's already in the file. The Wizard should offer a high-level switching option between the two scenarios, which the initial installer should also accept.
LMCE is supposed to serve a home audience, not (necessarily) a hacker audience. Even when pro installers are deploying at a customer's site, the time saved and mistakes avoided with such automation will lower costs. And of course nontech consumers will find that significant barrier to entry dropped. Which is the main benefit of using competitor products like Windows MCE: it's really simple, in usage terms that the mass market can easily understand.
You should request a UI feature in Mantis
(Category: Webadmin / Severity: feature).