|
Post by drewy on Dec 6, 2008 21:42:48 GMT 7
Just in case anyone didn't know, in later versions of azureus the use of the safepeer plugin has been terminated.
They now recommend you use azureus's built in IP Filters for the same purpose as safepeer. IP Filters is also meant to be less of a memory hog.
So to get IP Filters working with the azureus mod you need to do a little work....
You need ssl access to your 5200. Login as sys. Make sure the AZUR mod is not started. and then:
cd /raid/data/module/AZUR/system/bin/azureus
/raid/data/module/AZUR/system/bin/jre/bin/java -jar /raid/data/module/AZUR/system/bin/azureus/Azureus2.jar --ui=console
this starts the azureus client in console mode, but with a command prompt so that you can issue commands and set parameters etc.
type:
set "Ip Filter Autoload File" "http://www.bluetack.co.uk/config/level1.gz" string set "Ip Filter Enabled" true boolean set "Ip Filter Enable Banning" true boolean set "Ip Filter Banning Persistent" true boolean
and then:
quit
Then start up the AZUR mod. If you then: cd /raid0/data/module/AZUR/system/bin/azureus/.azureus ls -l
you should (soon) see the ipfilter.* files growing in size as azureus begins caching the ip filters.
That's it should then be working fine.
|
|
flynn
Junior Member
Posts: 88
|
Post by flynn on Jun 15, 2009 4:34:50 GMT 7
are these steps still necessary with the latest module? or after updating to Azureus 3.1.1.0?
I ask because the ipfilter.cache file was already > 0 before performing these steps, and when looking at the output of the azureus startup it looks like it was already set to autoload some files from bluetrack.
|
|
|
Post by jasonsmitters7384 on Jul 21, 2009 11:46:31 GMT 7
|
|