Posted: Thu Jul 14, 2011 17:37 Post subject: 17201 - Howto fix the milkfish-dd?
tp-link 1042nd
The milkfish-dd did not start and respond as status
SER Uptime:
Error opening openser's FIFO /tmp/openser_fifo
Make sure you have line fifo=/tmp/openser_fifo in your config
No i entered the milkfish-dd wiki for help and found this
A: The OpenSER control tools could not connect to the FIFO interface. Check if your configuration loads the mi_fifo module and configures a fifo name. Example for the configuration syntax:
loadmodule “mi_fifo.so” modparam(“mi_fifo”, “fifo_name”, ”/tmp/openser_fifo”)
There is no /tmp/openser_fifo after dd-wrt startup.
root@charydbis:/# ls /tmp
ath0_hostap.conf hosts resolv.conf var
cron.d igmpproxy.conf resolv.dnsmasq www
crontab loginprompt root
dnsmasq.conf nvram udhcpc
etc oet udhcpc.expires
Q: ERROR: Error opening OpenSER's FIFO /tmp/openser_fifo when using openserctl
ERROR: Error opening OpenSER's FIFO /tmp/openser_fifo
ERROR: Make sure you have the line 'modparam(“mi_fifo”, “fifo_name”, ”/tmp/openser_fifo”)' in your config
ERROR: and also have loaded the mi_fifo module.
A: The OpenSER control tools could not connect to the FIFO interface. Check if your configuration loads the mi_fifo module and configures a fifo name. Example for the configuration syntax:
loadmodule “mi_fifo.so” modparam(“mi_fifo”, “fifo_name”, ”/tmp/openser_fifo”)
I have yet to try an earlier version of the firmware, but I will have to change routers as there are some issues with the WiFi in the E3000 with earlier builds
This is the case on DD-WRT v24-sp2 (12/24/10) big - build 15962 on my Netgear WNR3500L
maybe something in the compile. I have checked the milkfish.org forums and have noticed that there are some issues late last year with the build. But Milkfish had a meltdown and the forums are frozen so no posting there
I have been poking through the source code and noticed that there have not been any changes to the Milkfish or OpenSER for years.
I would say that this bug is not dependent on the missing module mi_fifo.so module.
Once i get this source thing checked out I'll have a more detailed look into it.
I'll also try to get the first "broken" release version too. Give me a few days as I have just had my $$$ work expanded by a solid month. Not so much spare time
Posted: Sat Oct 29, 2011 21:38 Post subject: openser_fifo
hi all.
17598M - sameshii
I've been thinking that I broke it my self messing with the cfg.. that was a quite a waste of time tryng to fix it.
thank you people
I'll try to reinstall openser using optware. will post results.
well, it works as a seprite service, but I don't know yet how to point milkfish webfece to it. I have a new paths to openser and it's modules - like /opt/sbin/ and /opt/etc/openser/ insted of /sbin and /var/..
There is enother motivating thing.. milkfish_openser doesn't include tls support in it's build. And opt-pak openser - does.
so if someone can share some idies how to make it right with out compilling a custom dd-wrt that would be nice.
Found enother thing: openser is included in OpenWRT packages as a new project called Kamailio and it has administration webface integrated in LuCi. And as far as i know that webface is a product of the same team that worked on openser, so everything is more solid there.
Thats why we didn't get any updates with milkfish so long! It has no future any more.
You can do most of what you would do on the Milkfish interface, which is regsitering local devices and creating aliases by pointing the OpenSER database to wherever it is stored on DD-WRT (/var/openser/dbtext) from memory
Re Kamailio:
Quick history:
SER = Sip Express Router. Set up by IPTel
OpenSER came from a fork where some developers who wanted more innovation, while SER wanted stability.
OpenSIPS came from a fork of OpenSER for various reasons
Milkfish forked from OpenSER especially for ruinning on embedded hardware.
Last year (or maybe the year before) OpenSER and SER decided to combine their code and work on a standard platform which would work with both OpenSER and SER modules and "styles of doing things". They called it Kamailio.
OpenSIPS was invited but decided to stay separate.
Now, there is a cool addition in Kamailio 3.1, current version is 3.2, there is now a module that supports registration of the SIP proxy to a third party SIP provider, like Asterisk / FreeSwitch does.
Up until now, xSER would only route and transform. Any outbound regsitrations would have to be acomplished by the client.
I am certainly keen on seeing a current, albeit stripped down, version of Kamailio on DD-WRT and am more than happy to contribute what little spare time I have between family and two CrazyGoNuts contracts I have at the moment.
Without having to completely recompile everything, I have had some success with the Firmware Modification Kit http://www.bitsum.com/firmware_mod_kit.htm which allowed me to install a version of dnsmasq which I compiled with a TFTP service and logging enabled.
The results are varied, but, I haven't bricked a unit.....yet
BTW I am compiling a 2.6 kernel on Netgear WNR3500Ls. I am also looking at running the same on a Linksys E3000.
Back to Milkfish: So far I have been able to get some basic SIP / RTP proxy services running. I haven't flogged it much yet, but I am about to for a client. Just to see if I can get a direct media stream between the two sites for a hosted PBX and handsets behind NAT.
Specifically, I am trying to customise a DD-WRT version that has:
TFTP for:
* Provisioning phones and managing the handset firmware via a USB key
SIP router and RTP proxy to:
* Allow a direct media path between the WAN address and the ITSP where the PBX is hosted externally
* Allow direct media between handsets on the same LAN
* Provide a basic backup system for when systems or links go down. A bit like Cisco's SRST
* Basic SIP border controller for "normalising" SIP for various IP PBXs behind a firewall.
* Running multiple Aastra handsets behind NAT.(that has always been an issue for me)
I also need:
* VLAN support, both port based and tagged
* Basic QoS and packet queuing
* OpenVPN
* PPTP for easy access to the LAN for remote support
I would love IPSec support. So far it hasn't been forthcomming.
Most of this stuff, other than the IPSec is available pretty much out of the box, with a bit of hacking and repackaging.
BTW, what is your interest in OpenSER / Kamailio ?
/C
ps. I am sorry if I am a little long winded in explaining things, I figured if we get a result in the end, then some further information and background might help someone else who stumbles across this thread.
yea, I've found a way to use "textdb" with a new openser and old paths to db that are used by webface.
But still, Milkfifh has a nice status button on a webface and an autoconfig on enabling service. And I might be wrong but openser uses some kind of "nat-helper" wich is allso configured automaticly.
So I guess we just need a dd-wrt with the right openser version.
I'm looking for a standalone solution with min complexity and max security for incorporate/private sip without using any third-party services.
I think that there is no need for Asterisk while openSER does the most functionality and clientside's zrtp makes it enough secure.
ps: Plane tls has a mitm-vuln. I'm still reserching srtp, but as far as I've figured it out: to avoide mitm I need to use a trusted CA to authorise clients certs - that is too far form ease.