Feature Requests

I'd like to see some minimalistic http or tftp server embedded in M0nowall, to be able to store xml config for VoIP box on a always-on router instead of using some external server.

There is a lot of VoIP devices (especially former Vonage adapters and routers) that must be configured using xml... Example - my D-Link VWR. Vonage give admin password away after closing of subscription, but VoIP admin pages in password-protected section of web config is simply useless - unit does not save config changes to a non-volatile memory.

Only way to config this beastie is xml file that must be stored on some http or tftp server. And looks like great idea to have this stuff in-house, accessible only from LAN/OPT side, because this xml contains VoIP account login and password in open text form.

Some minimalistic file management allowing to upload new xml to flash card (to be seen from outside as /<some folder>/<voip_dev_MAC_addr.xml>) or remove not-longer-necessary one is also necessary to get this running.

You could try to put the phones behind a captive portal interface and upload your config to that, give them pass-through access for the portal since they wont be able to authenticate.

You could try to put the phones behind a captive portal interface and upload your config to that, give them pass-through access for the portal since they wont be able to authenticate.

Hm... It was fun to find this reply after 4 years... Just to understand that it will not help.

Idea to integrate TFTP server (now definitely talking about TFTP) is still actual. There is a lot of available VoIP hardware that trying to read provisioning and dial plan XML file after every restart.
One of such devices is near me right now (Cisco CP7970G IP Phone with SIP firmware installed, used with one of BYOD SIP providers).

Sounds like something an inexpensive Raspberry Pi could handle well.

http://www.ronnutter.com/raspberry-pi-tftp-server/

As proposed in the last post, I do use a small dedicated machine in order to provide some services that are not packed into m0n0wall (ie. ntp, tftp, printing...).
As stated in the manuals/documentation, the current embedded services package won't grow any further. Thus using a second small/underpowered/old/recycled box (raspberry pi, beaggle bone, ...) seems to me to be the best (the only one) way to handle extra services.
Just my two cents.