1 Attachment(s)
Tinyproxy compiled for WL-500g
Anyone want tinyproxy?
Executable is 106k. Each child takes 3.3% of the router's memory.
The patch for tinyproxy 1.6.2 is attached.
The configure options are:
./configure --host=mipsel-linux --with-config=/etc/tinyproxy.conf --enable-transparent-proxy
-- Rod
1 Attachment(s)
tinyproxy running on WL-500g
Hello,
as I need a small proxy (non-caching proxy) running on my Asus
(because I am lazy to switch my proxy off when I am at home and not at work)
I have managed tinyproxy working on Oleg's 1.9.2.7-7g firmware.
Probably it will work also on older releases, but I just started with this one.
If there is an interest to include it into firmware release (next one?),
I can share my experiences.
I have attached proposed tree within install dir (before target) of firmware.
making a functioning package -- tinyproxy
I'm trying to make tinyproxy package for wl-500gp.
First I've tried to build it with built in uclibc, then I managed to make a toolchain for newer uclibc (the one from www.nslu2-linux.org/wiki/FAQ/Optware-uClibcBuild) and to build binary with the tinyproxy.mk I've modified. I needed quite a lot of time to figure out how.
What I don't undestand is at the moment:
1) how I can make the resulting binary be named not in the form mipsel-linux-tinyproxy but only tinyproxy.
2) Which number for SXX in the init.d should I choose to be sure that it doesn'T collide with some other package?
(And it's still not fully working, I probably have to debug it, at the moment I also still haven't figured out 3) how to see sources in gdb, I know only of --enable-debug option in configure but I obviously miss something more.)
Thanks for all advices