Currently I am using PC Engines Alix + m0n0wall in production environments. So far no problems. It is working really good.
In the Past I have bad experience with VOIP+pfsense. I never try the most recent version 1.2.3. But ....I would say a VOIP friendly router should have the Following features 1. WAN Port - PPOE - DHCP - STATIC - PPOE + MLPP 2. LAN Port's - DHCP - VLAN - DHCP Option 66 3. VPN Support 4. Should pass the TFTP traffic from WAN to LAN 5. WAN Failover 6. Monitoring tools But I could not find any open source firmware support all of the above. Thank you. A.T.Lloyd On Wed, Sep 2, 2009 at 4:00 PM, Dave Donovan <[email protected]>wrote: > On Wed, Sep 2, 2009 at 1:51 PM, Dave Donovan<[email protected]> > wrote: > > I like the suggestion of using the Snoms for remotes. I never would > > have guessed that a phone had OpenVPN built in. Maybe the Alix is a > > good solution for your aggregation point. > > I'm going to reply to my own post here and add some disclosure, lest > anyone get false hope or be misled. > > In my environment I'm running pfSense at my remote sites on refurb > Dell P4s. I've bough the Alix systems and I'm testing them pending > deployment. So far things look good. > > At my head office, I'm not running pfSense. I'm running Untangle > because it has a web filtering, antivirus, antispam, etc and a cool > interface for generating and distributing the OpenVPN install packages > with the keys and everything all rolled up. It's gone wonky on me a > few times and I've sworn to rip it out but then reconsidered the > calmness of the following day. The Untangle system is not meant for > the hacker set. It's the Trixbox of routers. > > Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
