@robnitro
Just re-read your post, the supplied diffs are against the specific git revision my tree is at the time of creation. If you use git/svn to fetch the latest, the patches might not apply. Either fix the differences or apply patches to same revision. As I already mentioned you can download the latest-src.tar.xz and just build, as explained on the first page.
As for the blocklist, I feel a static file that gets compress in the image is a better approach than a script that will use more storage. Also, 30-40MB RAM is a huge amount for routers that have 64/128MB of RAM.
Thanks for the heads up. I was just really confused... I was not touching stuff, just adding my scripts to etc and also building a version for buffalo ag300h.
The tar.xz works perfect! No more issues, I even did a git pull and it still worked fine. Sometimes linux stupifies me, too many options.
As for the block lists, yeah, it's insane. But for those who do torrents, the 128 MB ram routers really can handle it. You can also run peerblock on the PC with the torrent client, but I have others in the house who use p2p and don't want bad ips/ranges from connecting.
For example, I run 14 small allow lists(for gaming-etc), 11 smaller lists, and 2 HUGE lists (level 1 bluetack, and a slightly bigger one- primary threats- which some are dupes of L1).
Just to make your point, yes huge memory hog LOL
lol here are the bzip2 compressed sizes of the lists:
Allow list- 3K
11 small lists- 420K
L1+Primary threats- 1.75MB!
L1 alone- 800K.
Memory wise:
Allow- 23.4Kb
11 lists- 1.4MB
L1+primary threats- 8.8MB
L1 alone- 7MB