How about Squid Cache

[alpheratz]

I recon that would would be GREAT!

I was looking at Snapgear's SG565 a while ago and that has the ability to use an external USB disk as filestore for a squid cache:

www.securecomputing.com/index.cfm?skey=1558

I recon this would be a hit!

Cheers,

Alph

[johner]

yes please!

[alpheratz]

I just noticed that there IS a squid module for the 2100:

thecususergroup.proboards106.com/index.cgi?board=modifications&action=display&thread=604&page=2

I am wondering...is this compatible with the N5200(pro)?
The Module Development page (http://www.onbeat.dk/thecus/index.php/N5200_Module_Development) says "Starting with firmware version 1.00.06.5 Thecus have implemented a module framework for the N5200 which is basically the same as that of the N2100."

I have had look around the untarred Squid.mod file and things look OK to me...anyone out there tried to use a 2100 module on a 5200 series?

Cheers,

Alph

[omega]

The module framework for the N2100 is not 100% compatible to the one used for N5200, although this wouldn't be a big problem...

But the binaries are totally different. You need to compile squid for the N5200...

Andreas

[alpheratz]

Ah yes, I see..the 2100 is an ARM processor.

I have the source...do I need to compile a statically-linked binary or can I just use a dynamically-linked one?

On Centos, to get a statically linked binary, I have done:

./configure LDFLAGS=-Bstatic CFLAGS=-static

Centos then says:

[root@localhost src]# file squid
squid: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, statically linked, for GNU/Linux 2.6.9, not stripped

This seems to be very minimally OK...at least, when I run it up on the N5200pro I get:

root@127.0.0.1:~# ./squid -h
Usage: squid [-hvzCDFINRYX] [-d level] [-s | -l facility] [-f config-file] [-u port] [-k signal]
       -d level  Write debugging to stderr also.
       -f file   Use given config-file instead of
                 /usr/local/squid/etc/squid.conf
       -h        Print help message.
       -k reconfigure|rotate|shutdown|interrupt|kill|debug|check|parse
                 Parse configuration file, then send signal to 
                 running copy (except -k parse) and exit.
       -s | -l facility
                 Enable logging to syslog.
       -u port   Specify ICP port number (default: 3130), disable with 0.
       -v        Print version.
       -z        Create swap directories
       -C        Do not catch fatal signals.
       -D        Disable initial DNS tests.
       -F        Don't serve any requests until store is rebuilt.
       -I        Override HTTP port with the bound socket passed in on stdin.
       -N        No daemon mode.
       -R        Do not set REUSEADDR on port.
       -S        Double-check swap during rebuild.
       -X        Force full debugging.
       -Y        Only return UDP_HIT or UDP_MISS_NOFETCH during fast reload.

at least it's a start...

Advice/comments gratefully accepted...

I guess that if this is OK...converting it into a module based on the n2100's one should be fairly painless.

Cheers,

Alph