.... However, I have some packages that are missing from these alternatives, like:
-deluge
-mkvtoolnix
-X11 applications
-etc...
and some are newer versions.
....
Excellent work! I've tried to install the Pound package but it looks like no startup script is installed in /opt/etc/init.d. Any idea why? I had to copy over one from Optware but it is not working properly.
Any chance to get a service script working, like in Optware?
Joined: 03 Aug 2014 Posts: 41 Location: Kyiv, Ukraine
Posted: Fri Apr 17, 2015 17:27 Post subject:
luiswu wrote:
Excellent work!
Thanks
luiswu wrote:
I've tried to install the Pound package but it looks like no startup script is installed in /opt/etc/init.d. Any idea why? I had to copy over one from Optware but it is not working properly.
Any chance to get a service script working, like in Optware?
Thanks
Compared to original Optware, I only upgraded pound 2.5 -> 2.7. Optware didn't ship its own init scripts, so probably it was shipped with the sourcecode itself. I'll just take the init script from Debian (and make necessary adjustments to make it work with Optware) a bit later (maybe, tomorrow, if I don't have the time to do it today).
Joined: 03 Aug 2014 Posts: 41 Location: Kyiv, Ukraine
Posted: Sat Apr 18, 2015 9:40 Post subject:
luiswu wrote:
Excellent work! I've tried to install the Pound package but it looks like no startup script is installed in /opt/etc/init.d. Any idea why? I had to copy over one from Optware but it is not working properly.
Any chance to get a service script working, like in Optware?
Joined: 03 Aug 2014 Posts: 41 Location: Kyiv, Ukraine
Posted: Sun Apr 19, 2015 18:22 Post subject:
My Optware fork project now has MIPSEL feed as well! Compared to the original outdated oleg Optware feed, it has:
-softfloat ABI, which is a must to work with dd-wrt
-newer package versions
-up-to-date toolchain
-considerably more packages available
It hasn't been run tested, so please test and report back:
Code:
ipkg-static update
ipkg-static upgrade
and in case pound isn't installed already,
Code:
ipkg-static install pound
Then edit /opt/etc/pound.cfg and start pound:
Code:
/opt/etc/init.d/pound start
Thanks for the quick fix! It is mostly working, I only had the following issues:
I had to manually create the /var/run/pound directory
The script doesn't stop Pound, you get the following error: killall: /opt/sbin/pound: no process killed
You may want to take a look at that for other users, it does't seem too hard to fix. Other than that it seems to be working, though I haven't had much time to fully test it. I'll report again when I finalise my tests.
Joined: 03 Aug 2014 Posts: 41 Location: Kyiv, Ukraine
Posted: Tue Apr 21, 2015 14:35 Post subject:
luiswu wrote:
Thanks for the quick fix! It is mostly working, I only had the following issues:
I had to manually create the /var/run/pound directory
The script doesn't stop Pound, you get the following error: killall: /opt/sbin/pound: no process killed
You may want to take a look at that for other users, it does't seem too hard to fix. Other than that it seems to be working, though I haven't had much time to fully test it. I'll report again when I finalise my tests.
Thanks for the feedback, I'll look into it a little bit later when I have the time.
Hosting has been kindly provided by zyxmon. Many thanks to him!
Run these commands to update feeds location (both arm and mipsel):
Code:
sed -i -e 's|alllexx.no-ip.biz/optware|optware-ng.zyxmon.org|' /opt/etc/ipkg.conf
ipkg-static update
I've discovered one more thing: this version of pound works fine with an http host but when I try to use an https listener (with the corresponding certificate) I get an error message from the browser saying that it can't establish the https connection.
I managed to run another version of pound in the router and with that version the https listener works correctly allowing https traffic (as long as I provide a valid certificate in the configuration file). I have ruled out therefore any ssl problem in my build and I presume that the problem lies in the compilation of this package, just to let you know.
In spite of these issues, thanks for the effort in bringing an operative version of optware, it is much appreciated!
Joined: 03 Aug 2014 Posts: 41 Location: Kyiv, Ukraine
Posted: Fri Apr 24, 2015 14:25 Post subject:
luiswu wrote:
I've discovered one more thing: this version of pound works fine with an http host but when I try to use an https listener (with the corresponding certificate) I get an error message from the browser saying that it can't establish the https connection.
I managed to run another version of pound in the router and with that version the https listener works correctly allowing https traffic (as long as I provide a valid certificate in the configuration file). I have ruled out therefore any ssl problem in my build and I presume that the problem lies in the compilation of this package, just to let you know.
In spite of these issues, thanks for the effort in bringing an operative version of optware, it is much appreciated!
As for https, openssl is functional, since I have tested it to work fine with lighttpd to establish an https socket. Therefore, there're two possibilities that come to my mind:
1) pound build issue
2) certificate issue
As for the former, I need more info to try to fix it, and probably the best way would be to try to replicate the error myself, but I'm a little busy right now with adding an i686 feed.
As for the latter, it might be possible that certificate you use is incompatible with this pound/openssl version(s). Just a wild guess, but who knows? Are you using the one provided by the package, your own self-signed one, or perhaps an authority-signed one, by the way? You may try to generate a self-signed certificate on the router and see if it works first.
It turns out that the build that I am using (Kong 25100M) comes with a pound executable and I haven't realized that until recently.
I was able to process https requests with that executable and a self-signed certificate, therefore I tend to believe that the problem with the optware pound must be a compilation issue, but I could't dig any further into that.
Still, it would be great if this issue can be fixed in the optware pound that you are managing, not all the builds come with this package and I suspect that sooner or later I will have to upgrade and will loose the "built-in" pound.
I'll upgrade the pound package and test if the other issues are fixed.
