Every time I look at m0n0wall I realize it's a great networking
appliance platform. It seems ready to handle all sorts of appliance
types of tasks. The hardware support and read-only CompactFlash boot
system is great.
To me the most obvious extension of m0n0wall is to augment its existing
strength as a firewall and make it a router. When it comes time to set
up an Internet router I shudder to pay for something like a Juniper or a
Cisco when I know I have hardware in stock that can perform just as well.
I'm not referring to full feed BGP/multi-OCx gear. I'm referring to
simple T1/E1, serial or Ethernet routing. I'm sure it could do the full
feed and OCx work but it's not likely to be the biggest use.
The solid packet filtering and access controls are already in m0n0wall.
Adding support for serial interfaces and T1/E1 cards seems like a
logical extension of the "WAN" port. This comes to mind:
Not all routers need firewalling. Most need some basic filtering.
Captive portals can be helpful on some networks. Most routers need to
understand multiple WAN ports and things like MLPPP.
Does it need a really routing daemon like quagga? That seems like a
small addition to the existing platform.
I build Ethernet-driven FreeBSD routers for my Internet connections now.
I keep multiple units around and rotate them in to service every six
months or so as FreeBSD releases updates. I would really rather use
something like m0n0wall which really makes things quick and simple.
Does anyone else see this potential development path for M0n0wall?