Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
  • in reply to: Update kernel 2.6.36 for b13 #51501

    I tried to get this working first with Dansguardian, and then with just HAVP. Unfortunately, I keep getting these errors:

    01:04:39 ClamAV: Using database directory: /var/register/system/ClamAV/db
    01:04:39 ClamAV: Could not load database: Can’t verify database integrity

    and these: proxy log:

    01:05:43 — Initializing ClamAV Library Scanner
    01:05:43 ClamAV: Using database directory: /var/register/system/ClamAV/db
    01:05:43 ClamAV: Could not load database: Can’t verify database integrity
    01:05:43 Error initializing ClamAV Library Scanner!

    I would be interested in seeing if anyone has successfully fixed this. I’ve tried copying stuff over from my old working install, but it’s not working, and freshclam doesn’t seem to be configured with the ZS directory locations in mind. Think I’ll go back to beta12 for now (doh).

    Be very interested in when Zeroshell is working with dansguardian and a modern kernel. Oh well.

    in reply to: HTTP Proxy/DansGuardian performance is slow over time #48137

    One thing to consider is the EeePC’s lack of gigabit LAN. If I had to do it over again I’d probably get an EeeBox. Either the B202 or the newer one have GLAN, which I expect would work with Linux. Kind of strange that the EeePC with screen running all the time uses less power than the EeeBox, which I think is 13-15W.

    This is only an issue though if you use VLANs, which I do. Otherwise you have your ZS box between your only subnet and the internet, and if you are complaining about 100Mbit being slow on that, I envy you.

    in reply to: How To rebuild kernel into b14 document #51585

    Thank you very much for your hard work, rda. Now my EeePC is working at full 100 Mbit speeds running ZS.

    Cheers. Hopefully a newer kernel version can become official in the not too distant future, I always feel better about downloading software from the official sources. But in the meantime, I’m pleased to be able to use this.

    * Whoops. Looks like beta14 does not have a dansguardian patch yet. I’ll go back to my old ways of operating until that comes out. Doh. Or attempt to do this process for beta13. Anyway, nice work guys.

    in reply to: How to get Linksys USB200M and maybe other USB NICs to work #50993

    Had a bit more of a play… I realized that I am only getting 160-200KB/s when routed through the zeroshell Eee PC, using sshfs. I tried looking at top and there is next to no CPU being used, and very little memory. dmesg gives a pretty much constant stream of that earlier message “asix_rx_fixup()” etc. This happens whether I use a USB200M or a D-Link DUB-E100.

    Other than that, it’s working perfectly. URL filtering is great, no slowdown on dansguardian, it all “just works”. With a new kernel or maybe even kernel module this would be working phenomenally. And realistically, for just one subnet it works ok as is. The maximum speed I can download is 570KB/s, which is not the full bandwidth but better than 200KB/s.

    in reply to: HTTP Proxy/DansGuardian performance is slow over time #48136

    Since I’ve moved to using an Eee PC with 10x the amount of RAM as the WRAP, I haven’t had the slowdown problem with dansguardian. No such errors in dmesg as I was getting before (but some different USB NIC related ones). I’ve been running the same setup without a reboot for about a week now. It’s working well and very snappy. Starting and restarting the filter is fast by comparison, and the web interface flies. For 10 more Watts and a built in UPS, monitor and keyboard, I think the Eee PC solution is definitely worth it.

    The only issue with using an Eee PC is the bandwidth you can get over a USB NIC. So far I’m not seeing the bandwidth I would expect (over sshfs at least, I haven’t tried other methods). However, since 1MB/s is all I can get over the internet, it’s not a real problem at this stage.

    in reply to: How to get Linksys USB200M and maybe other USB NICs to work #50992

    For some reason, I seem to be getting only about 1MB/s on an SSHFS connection that is routed on the zeroshell box. When I change it so that it’s on the same subnet (e.g. just going through the switch), I get 22+MB/s. I’m not sure whether it’s
    a) the dmesg errors slowing the connection down, i.e. the driver situation isn’t 100%
    b) the Eee PC not being able to handle the workload (doubtful I think, even though USB shifts workload to the CPU)
    c) the USB NIC isn’t as fast as it is supposed to be

    However, if all you are after is a way to filter your connection to the internet, it works really well. And if you are using it to route between two subnets on your home network, provided they don’t need to transfer massive files between each other, it works well too.


    Note that using the Linksys USB200M you will get errors appearing in dmesg. It is also likely with the DUB-E100.* Here is the error I get:

    ETH00: asix_rx_fixup() Bad RX Length 1518

    Not sure how to fix. It doesn’t appear to affect the functioning of the network, but I would appreciate any help.

    * See

    See also

    in reply to: How to get Linksys USB200M and maybe other USB NICs to work #50990

    The above appears to work for 13 beta, or at least from memory that’s what I did. In 12 beta it doesn’t work (I get something like Preboot Failed – Error 126 or something like that). In order to get it to work I had to put those lines in via the web interface, i.e. by finding a laptop with compatible NIC, booting from that, changing things from the web interface, and sticking the USB stick with Zeroshell on it back into the original Eee PC. A bit of a pain, lucky I had the other laptop to do it from.

    in reply to: USB nic wierdness #49113

    It wasn’t clear that this was resolved, but I’ve written a howto for this here:

    in reply to: HTTP Proxy/DansGuardian performance is slow over time #48135

    Ok, so I did a bit of googling for what to do with high IO-wait, and it said that it’s often a symptom of low memory. Also, check your dmesg output. Sure enough:

    Out of memory: kill process 4838 (havp) score 32659 or a child
    Killed process 4841 (havp)
    daemonwatcher invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0

    Looks like the low memory of the WRAP is an issue for running ZS+DG.

    in reply to: HTTP Proxy/DansGuardian performance is slow over time #48134

    Ok, I just had another little play with this, hammering the WRAP with opening different webpages (only about 5-10 different requests or so), and I note that in top the free swap memory is down to 52k (and has been around 500k or so for a bit), and the free memory is 2-3MB. 90% of processes are in I/O wait.

    My guess is that the WRAP is just too light in memory for the required task. I’m about to try it with a netbook instead of a WRAP, hopefully 1GB will be enough RAM.

    in reply to: HTTP Proxy/DansGuardian performance is slow over time #48133

    I just wanted to bump this.
    @foobysmacker wrote:

    I’m running ZS 1.0b11b on a Alix device (AMD 500MHz / 256MB / 1GB CF). The ZS box is used as a wired router (no wireless) and services 5 clients that browse the web + 1 that is used frequently for bittorrent downloads.

    Hi, I am getting similar symptoms to you. Except that usually it starts slowing down in a week or less. I am running a WRAP (which is half the MHz and RAM of your ALIX).

    When it works, it works well. When it works poorly, it will either:
    a) take a long time to connect to the web (5 minutes or more at times), i.e. unusable. Sometimes if you come back to it a while later it will inexplicably work. When I reset the machine, it usually restores the performance.
    b) not work at all.

    Meanwhile, everything else keeps chugging away, bittorrent, ssh to the ZS box. I run top and nothing is over 6% for memory or CPU usage. I have 3-4 MB free RAM and 57MB free swap or so. That doesn’t seem to be much RAM left, considering I’m running the embedded version – there isn’t any swap, correct? If so, maybe memory is the problem – 3MB RAM is not much to play with.

    The fact that my system has half the memory of yours makes me suspect a memory leak, even if that is not the case.

    Other symptoms – when I attempt to go to a website through firefox, the “connecting to…” bit at the bottom left hand side of the browser very quickly changes to “waiting to reply from…” and stays there the whole time it is stalled there. So I wonder what is the problem.

    Any suggestions for diagnosing this thing would be really helpful.

    Edit: Another thing I forgot to mention, I am running an Atheros wifi card in the WRAP. The connection quality is good but not great. I note the following url has something that points to two possibilities – RAM (suggests that DG needs lots of RAM) and that the Server Network Connections have low error rates. Either of these could be a problem.

Viewing 12 posts - 1 through 12 (of 12 total)