Results 1 to 13 of 13

Thread: Tinyproxy compiled for WL-500g

  1. #1
    Join Date
    Apr 2004
    Location
    Adelaide, Australia
    Posts
    88

    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
    Attached Files Attached Files

  2. #2
    Join Date
    May 2007
    Location
    Slovakia
    Posts
    5

    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.
    Attached Files Attached Files

  3. #3
    Join Date
    Sep 2006
    Location
    Slovakia
    Posts
    34
    could you please write some kind of tutorial how to install it?

    thx

  4. #4
    Join Date
    May 2007
    Location
    Slovakia
    Posts
    5

    mini how-to

    This was just a proposal to include tinyproxy into Oleg's firmware and the attached tar shows the proposed location within firmware.

    However, the compiled binnary can be put to any folder (e.g. /usr/local/sbin) and other files too (default config file is set to /etc/tinyproxy.conf, but you can use any other by setting -c switch when starting tinyproxy, e.g. /us/local/etc/tinyproxy.conf). Just don't forget to configure other setting in the config file to your locations (DefaultErrorFile, StatFile, PidFile, Filter)

    So, you can even untar the archive and copy whole content of tinyproxy subdir into /usr/local.
    Last edited by petom; 22-05-2007 at 13:18.

  5. #5

    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

  6. #6

    Tinyproxy help

    Dear wl-500gP users,

    I need to activate my proxy server on my wl-500gP (Oleg's FW 1.9.2.7-10), because I can't access some web sites from work.

    I installed Tinyproxy and tried to launch with the command:
    Code:
    /opt/sbin/tinyproxy start
    I sat the port to 3306.

    But no success. Could anyone post his own tinyproxy.conf? Or, give me a hand?

    ThanX,
    T.

  7. #7
    Join Date
    Aug 2008
    Location
    Poland, Bia³a Podlaska
    Posts
    276
    Yeah, i have the same problem...

  8. #8
    The Patch its apear to be cutted :


    if test x"$tinyproxy_use_our_regex" = x"yes" ; then

    ...?

    And its valid for wl600 ??

  9. #9
    Quote Originally Posted by petom View Post
    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.
    and for WL600?? plzzzz

  10. #10
    Join Date
    May 2007
    Location
    Slovakia
    Posts
    5
    I don't have possibility to try it on WL-600, but as long as you are able to run Oleg's firmware on it, then there is no difference. Go ahead and use it.

    If you don't want to embed it into firmware as such, you can simply put it into /usr/local
    folders.

  11. #11
    I would like but the binarys of WL-500g are not compatible with 600
    The procesor arquitecture its some diference, because that i quest for a wl600 compiled version, i have some problems with the cross-compile.

  12. #12
    Join Date
    May 2007
    Location
    Slovakia
    Posts
    5
    Then I am sorry. I don't have WL-600g. I've been using WL-500gP for 4 years already
    and it's still good enough for me

    May be you could try to look on OpenWRT pages and find a compiled version of firmware for Wl-600g and extract tinyproxy from there.
    http://wl500g.info/showthread.php?t=15275

    Sorry, can't help more

  13. #13
    dont worry and thanks for anwers

Similar Threads

  1. Vnstat compiled
    By Rob ter Veer in forum WL-500g Q&A
    Replies: 14
    Last Post: 17-12-2007, 17:45
  2. no /dev/discs on own compiled 1.9.2.7-4
    By Jean-Fabrice in forum WL-HDD Custom Development
    Replies: 13
    Last Post: 22-10-2006, 17:49
  3. compiled 1950
    By alien433 in forum WL-500g Q&A
    Replies: 0
    Last Post: 23-09-2005, 23:00
  4. Compiled some tools for x-mas!
    By Rob ter Veer in forum WL-500g Custom Development
    Replies: 29
    Last Post: 22-05-2005, 11:24
  5. Anyone have perl compiled for wh-hdd ?
    By ezhikov in forum WL-HDD Q&A
    Replies: 0
    Last Post: 08-02-2005, 11:22

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •