nzbget - binary newsgrabber

Quote:

---

Originally Posted by methanoid

Did you check speed by comparing file size to time or take the figure nzbget gave you?

What options did you enable in the CONF? PAR2? UnRAR?

---

Par repair in nzbget.conf, other postprocessing (unrar etc.) has to be done by a script.

The speed indication on the latest revision is more accurate. I didn't actually benchmark it, I just took it as read. It's definitely quick...

EDIT:

Benchmarks

LinkStation Pro (400MHz ARM)
128MB RAM
750GB SATA drive
XFS
My max actual throughput ~16.1mbps

Test file: 399.3MB NZB = 361.5MB actual download
20 connections
Web interface refresh rate: 1 second

Download: 3 minutes, 6 seconds = 15.56mbit/sec
Par check (repair not needed): 1 minute, 55 seconds
Unrar: 1 minute, 3 seconds

I'm happy with 15.5mbps+ of my 16.1mbps. :D

Note also, I'm getting 50% of my max throughput using just ONE connection to the usenet server. This is a VERY efficient usenet downloader.

Dont need to ipkg install php as php-fcgi includes it?

nzbgetweb/settings.php

Settings here are well documented in the file. - but I think for a guide we need to be a tad more explicit.. last line for example of the conf file?

Could expand this:
Find a postprocessing script you like, put it wherever.
Edit nzbget.conf to tell it where you put it.
chmod a+x /path/scriptname.sh

Anyway I got the webserver up but not working. Whenever I try to upload a file I get
"Error: Check the path and the permissions for the upload directory (option nzbdir)"

I notice nzbget doesnt create directories when run so I had to create them manually in Windows so they show as nobody|nogroup for owner but I CHMOD -R 777 for them but still no joy...

So currently I cannot use nzbget yet...

And even when I can.. well it needs some extra tool as SABnzbd has a cool Firefox addin NZBstatus which would be nice to have with nzbget.

I'm certainly willing to change... one plus for nzbget is it wont interfere with running a website like SAB can with port usage....

Quote:

---

Originally Posted by methanoid

I notice nzbget doesnt create directories when run so I had to create them manually in Windows so they show as nobody|nogroup for owner but I CHMOD -R 777 for them but still no joy...

---

It must create all directories. Probably a permission-problem. Are there any errors in log-file?
Try to start the program from root-account.

Quote:

---

Originally Posted by methanoid

Anyway I got the webserver up but not working. Whenever I try to upload a file I get
"Error: Check the path and the permissions for the upload directory (option nzbdir)"

---

First check if nzbget works by uploading nzb-files via samba or ftp. Later we could try to fix the problem with web-interface.

Quote:

---

Originally Posted by hugbug

It must create all directories. Probably a permission-problem. Are there any errors in log-file?
Try to start the program from root-account.

First check if nzbget works by uploading nzb-files via samba or ftp. Later we could try to fix the problem with web-interface.

---

hi, OK it was a warmware problem :D

I editted the sample conf file and missed a ~ so my NZBget dir was ~/mnt/disk1/share/nzbget rather than /mnt/disk1 etc.... Ooooops

nzbget now creates the dirs but wont let me copy files into them so I had to chmod -R 777 nzbget directory and now I can copy an NZB file in but NZBget isnt doing anything with it... I run NZBget with "nzbget -D"

Nothing in log file bar NZBget running in Daemon mode.

if nzbget is as good on a Linkstation as Neilt0 says I'll be keeping this Linkstation and saving buying a low power usage PC for downloads...

My fingers are crossed!! :o

Quote:

---

Originally Posted by methanoid

nzbget now creates the dirs but wont let me copy files into them so I had to chmod -R 777 nzbget directory

---

There was a permission bug. Install the latest version from nzbget's home page with

Code:

---

ipkg install http://surfnet.dl.sourceforge.net/sourceforge/nzbget/nzbget-0.4.1-testing-r178-bin-cs05q3armel-arm.ipk

---

Set the option "umask=000" in the configuration file.

The created directories now should be accessible from all user-accounts, including samba.

Quote:

---

now I can copy an NZB file in but NZBget isnt doing anything with it...

---

Check options "NzbDirInterval" and "NzbDirFileAge". Value "5" for the last option should be enough. Check if date/time is set properly on you linkstation and if nzb-file has a proper date/time (files downloaded from some indexing servers have errorneous timestamp in the feature).

Yeah I had the correct nzbget and umask - I did read the "guide" post...

It was the time though.. well spotted... as soon as I changed my NTP server it worked.. The default LS time server was dead.. put a proper one in and its downloading away.. I'll test web interface next!

Thanks Hugbug, great spot!

Well it downloads beautififully and easily maxes my connection which SAB didnt do... but I need to add post processing script to unrar (IMHO this should be in NZBget as standard!!), just integrate ydrol's script.

Some questions if I may

1) to add ydrol's script which is Perl I assume I have to add Perl - which? Full Perl or would MicroPerl do? Details at http://ipkg.nslu2-linux.org/feeds/op...table/Packages

2) likewise I assume I have to install unRar (done) ?

3) Reason web i/f wont work and allow UL of NZB MIGHT be the lack of any option in $rpc_api='' - which do I use? I have installed PHP-FCGI and used XML_RPC before when I used to use Hellanzb so is that what I choose?


If I am totally honest I am VERY impressed with NZBget's speed but it's not as easy to configure as SABnzbd and as friendly. SAB has many more features but I guess they cost in one way or another? I like the way that SAB integrates with Newzbin website (can auto download bookmarked NZBs) and can process NZBs into categories (different file locations for say TV shows from Music downloads). I like auto PAR and auto RAR. I also have a great Firefox addin called NZBstatus which monitors SAB's progress.

But speed matters... really.. and I think NZBget could be developed further (and seems to be)...

Is there a road map for the future of this great package Hugbug? Please share it with us if you will

I do not use any postprocessing scripts myself. Sorry I can't help on configuring them. I hope neilt0 could share his experience on that part.

The reason to not using postprocessing and unrars for me is, that asus wl500gp has very slow speed accessing usb-attached hard drive (about 2-3 MBytes/sec). Because of that I can not use it as a shared drive, but need to copy downloaded files to desktop. And here we come to the point - the speed of copying files from wl500gp to desktop pc is the same as unraring the files from wl500gp to desktop pc. So unraring on wl500gp would be just unnecessary work for the router.

Quote:

---

3) Reason web i/f wont work and allow UL of NZB MIGHT be the lack of any option in $rpc_api='' - which do I use? I have installed PHP-FCGI and used XML_RPC before when I used to use Hellanzb so is that what I choose?

---

The option affects communication between web-interface-app and nzbget-server. If you see download queue and log in web-interface, that means the communication works.
You may leave the option empty. On optware-platform json-extension (built into php) will be used automatically; this is the best option for speed.

The option does not affect uploading of the files. The uploading does not need any communication with nzbget-server. Web-app just put uploaded files into nzbget's incoming directory. If it does not work check permissions for that directory. Also try some other nzb-file. I have had problems with some files (with special characters in their names). For test rename any nzb-file to something very simple (test.nzb) and put it into "C:\", then try to upload it.

BTW, from a local network it is easier to upload files using network-dir. I created a shortcut for nzbget's nzb-dir to sendto-menu of windows explorer. So any file can now be easily sent to nzbget via explorer's context menu.

Quote:

---

Is there a road map for the future of this great package Hugbug?

---

I'm sorry to disappoint you, but I'm not planning any new features.

Perl is easy: ipkg install perl

Web interface:

vi /opt/share/www/nzbgetweb/settings.php

I use:

$serverip = '192.168.0.16';

Make sure that's set to your LSPro IP.

Other than that, dunno why it's not working for you. Hugabug may. All I can recommend is carefully check all settings in the configs.

The major feature I miss from SAB is nzbdstatus, but nzbget is so fast at uploading NZBd via the web interface, it's not a huge loss.

There are major advantages to nzbget: speed, RAM usage, libpar2 instead of par2 for single pass par2, scripts can be more sophisticated.
SAB's fine for a fast PC -- I've used it for years, but for a device like the LSPro, I don't think there's any choice. It has to be nzbget.

Another warmware error.. I mistyped the NZB file directory in the Settings.php

Will need to remove PHP from the list of install requirements as PHP-FCGI installs PHP anyway and put in Perl if post processing script used and optional unRAR into install list.

Files upload to NZB dir fine but won't start downloading - still looking into.

Have to confess I am disappointed that no new features are planned at all. That's one thing I have liked about SAB, the devs have added stuff I have requested. Not big stuff but still they keep tweaking and improving.

Fingers crossed the postprocessing script works now... my net connection gets throttled from 4pm so its chugging a bit...

Are all my files supposed to be called

(null)
(null)_duplicate1
(null)_duplicate2
(null)_duplicate3 etc?? Seems I have another issue!

Quote:

---

Originally Posted by methanoid

Are all my files supposed to be called
(null)
(null)_duplicate1
(null)_duplicate2
(null)_duplicate3 etc??

---

No, they don't :)
I suppose these names were created by nzbget, not by a postprocess-script? Try a different nzb-file from a different source and report if it works.

Quote:

---

Originally Posted by hugbug

No, they don't :)
I suppose these names were created by nzbget, not by a postprocess-script? Try a different nzb-file from a different source and report if it works.

---

Seems to work on others.. musta been a rogue!

I really don't like the way it keeps NZB files when they have been completed and you have to delete them manually.. oh well... I guess I better hope the developers of the post processing scripts do all the things I still want to do.

I'll have to ask them how to fix such things like
WARNING PostProc:Unable to rename "/mnt/disk1/share/nzbget/nzb/Big Brother (UK) - 2008-06-20 - Big Ears Show 5.nzb" to .processed ;)

It downloads fine now from web uploaded NZBs and ones copied via SMB to the NZB directory. I think I may miss the auto download of Newzbin bookmarks!

Quote:

---

Originally Posted by methanoid

Seems to work on others.. musta been a rogue!

---

Please send me a problem nzb-file for testing.

Quote:

---

I really don't like the way it keeps NZB files when they have been completed and you have to delete them manually

---

Why bother? Delete them once a month :).
I believe both perl-scripts delete them also.

Quote:

---

Originally Posted by hugbug

Why bother? Delete them once a month :).
I believe both perl-scripts delete them also.

---

"I'll have to ask them how to fix such things like
WARNING PostProc:Unable to rename "/mnt/disk1/share/nzbget/nzb/Big Brother (UK) - 2008-06-20 - Big Ears Show 5.nzb" to .processed "

didnt work.. I'll investigate that... actually I have some good ideas for post processing scripts

What you would want to do with .queued files? Just deleted them upon successful download/par-check? I could add an option to nzbget.

Quote:

---

Originally Posted by hugbug

What you would want to do with .queued files? Just deleted them upon successful download/par-check? I could add an option to nzbget.

---

Yeah that would be nice.... but someone (??) said

"I'm sorry to disappoint you, but I'm not planning any new features."

So I didnt ask any more..

I'm torn between two options now (not bad ones though).

I love SABnzbd for its usability but they won't improve the speed and said it's cos you write in C++ and they use Python that you can beat them for raw speed. I asked for a few other tweaks (because no program is ever perfect for you unless you write your own!!)

I love NZBget (yes, that WAS quick) because it's so quick. In many ways I am coming around to the idea of post processing by scripts, especially when ydrol's script uses PAR/RAR as lower priority processes. Nice script. But I still want more features in NZBget and I can understand your reluctance to add so many things. Have to also say that (touch wood) NZBget has been very stable!

I guess I'll have to make my mind up what I want. :o

Quote:

---

Originally Posted by methanoid

Yeah that would be nice.... but someone (??) said

"I'm sorry to disappoint you, but I'm not planning any new features."

---

he-he, I did not have plans, because I did not have feature requests ;)
I have implemented most of requested features (auto-par, xml-rpc, web-interface, etc).

But unraring can be done via postprocess-scripts even better than from nzbget. If there were "libunrar", nzbget could provide some benefits over scripts (like a better progress-indication in par-check/repair).

Quote:

---

they use Python that you can beat them for raw speed

---

Not just c++, but also:
- better algorithms like DirectWrite-feature (to avoid joining-step - reduce disk-io);
- many speed optimisations (after code-profiling);
- very thrifty memory usage.

To compare: nzbget is two (or three, don't remember numbers) times faster than Newsleecher, which is written in Delphi (as fast as c++).

But: you want write xml-rpc server in python, you use internal classes (part of python) and only implement your rpc-methods. In c++ you need to write web-server first, then write xml-parser and only then implement rpc-methods. If you got luck, you could find a suitable library on sourceforge, but it would have incompatible license or will not work on windows or will need other big libraries, which is not ported on optware yet.

------------

How about new (planned?) feature - categories:
- each nzb-file can be assigned to category;
- incoming-directory can have subdirectories (one level enough?); by uploading a nzb-file to the subdirectory, the file is automatically categorized. Like multiple blackholes in sabnzbd;
- for each category nzbget will create a subfolder under dst-directory;
- the ability to change category via web-interface;
Someone need that?

Quote:

---

Originally Posted by hugbug

How about new (planned?) feature - categories:
- each nzb-file can be assigned to category;
- incoming-directory can have subdirectories (one level enough?); by uploading a nzb-file to the subdirectory, the file is automatically categorized. Like multiple blackholes in sabnzbd;
- for each category nzbget will create a subfolder under dst-directory;
- the ability to change category via web-interface;
Someone need that?

---

I'm very happy with nzbget as it is, but it would be handy to have categories. This would be most useful in combination with integrating into nzbget an NZB downloader from Newzbin -- feed a NewZbin ID to nzbget via the web interface -- e.g. 3093573, nzbget would then download the NZB from NewZbin using their API, download the collection and unpack it into the appropriate category (e.g. TV).
That would also open the door for a third party to come up with an nzbdstatus like add-on (in fact nzbdstatus itself could easily support nzbget).

Anything more complicated than that and you may as well move the directories manually?

P.S. nzbget is currently downloading on my LinkStation at a rate faster than any of my Windows PCs can. It's fantastically fast!

Quote:

---

Originally Posted by neilt0

This would be most useful in combination with integrating into nzbget an NZB downloader from Newzbin

---

Yes, Newzbin-integration would be the next step.

Quote:

---

Anything more complicated than that and you may as well move the directories manually?

---

I'm not getting what you mean :confused:

If you have to monkey around with manually creating directories, it doesn't seem that much easier than dragging stuff manually?

Well I guess it's a bit easier. Um.

Quote:

---

Originally Posted by hugbug

But unraring can be done via postprocess-scripts even better than from nzbget. If there were "libunrar", nzbget could provide some benefits over scripts (like a better progress-indication in par-check/repair).

---

There IS a libunrar http://www.freshports.org/archivers/libunrar/

But I cannot see any ARM port of this :(

Quote:

---

Originally Posted by neilt0

If you have to monkey around with manually creating directories, it doesn't seem that much easier than dragging stuff manually?

---

The destinanion directories will be created automatically.
You need to create manually only the incoming subfolders and only if you want to put nzb-files in that folders manually.

If you upload files via web-interface, you just choose a category (via combobox probably). The same for newzbin - the category will be read from newzbin.

Quote:

---

Originally Posted by methanoid

There IS a libunrar http://www.freshports.org/archivers/libunrar/

---

It's interesting. Thanks.
I looked in Debian repository, in optware repository on rarsoft-site and did not found any libunrars. I thought there is none :)
I'll look into it.

This version contains fixes for several bugs, including the bug, that broke the web-interface on CPUs with Big-Endian architecture (ARM, PPC, etc). Other bugfixes are not so important but you might want to update anyway.
See the full list of changes here.

The new version is already in optware-repository.

-----------------

Roadmap (methanoid ;)):
- I'm now working on category-feature;
- next (probably): newzbin-integration.

Quote:

---

Originally Posted by hugbug

Roadmap (methanoid ;)):
- I'm now working on category-feature;
- next (probably): newzbin-integration.

---

Thanks, can you make an iPhone version too? ;)

I just did a clean install of nzbget on a new LinkStation Pro, all is working except post-processing perl scripts are seemingly skipped. Not sure why?

Didn't it even say "Executing post-process-script for..."?

Can you please test with binary "0.4.1-r185-testing" from sourceforge? And if it still does not work, then with "0.4.1-r178-testing", which already worked for you, just for test.

The first feature for version 0.5.0 is now implemented and available for testing (release "0.5.0-r191" in package "nzbget-testing").

About categories:
- each nzb-file can have a category assiged to it;
- for each category nzbget will create a subfolder under dst-directory (option <AppendCategoryDir>);
- incoming-directory can have subdirectories (one level of nesting, isn't enough?); by uploading a nzb-file to the subdirectory, the file is automatically categorized;
- new command-line switch <-K> used with switch <-A> to set the category by adding of new nzb-file to queue;
- new subcommand <K> in command-line-switch <-E> to change the category of existing group;
- new parameter to post-process-scripts;
- new parameter in XML-/JSON-RPC-command <editqueue>;
- automatic moving of already downloaded files after the changing of category.

There is also a new version of web-interface with ability to change the category (release "1.1-2" in package "web-interface-testing").

Appreciate any feedback.

Hi all,

Thanks for this topic, NZBGet is a GREAT alternative to sabnzbd.
Currently I'm using the following post-processing script:

Code:

---

#!/bin/sh
 
#  1 - path to destination dir, where downloaded files are located;
#  2 - name of nzb-file processed;
#  3 - name of par-file processed (if par-checked) or empty string (if not);
#  4 - result of par-check:
#      0 - not checked: par-check disabled or nzb-file does not contain any
#          par-files;
#      1 - checked and failed to repair;
#      2 - checked and sucessfully repaired;
#      3 - checked and can be repaired but repair is disabled;
#  5 - state of nzb-job:
#      0 - there are more collections in this nzb-file queued;
#      1 - this was the last collection in nzb-file;
#  6 - indication of failed par-jobs for current nzb-file:
#      0 - no failed par-jobs;
#      1 - current par-job or any of the previous par-jobs for the
#          same nzb-files failed;
 
Sendmail=False
from=MyBook@isp.com
sendto=ReMiA@isp.com
server=mail.isp.com
nzbdir=/tmp/harddisk/torrent/target/
 
UNRAR=True
declare -a RARFILES
dir=$1
dest=/tmp/harddisk/torrent/target/
PauseServer=True
 
if [ "$5" = "1" ]
then
      chmod -R 766 "$1"
      subject="Download of $1 completed"
      if [ "$4" = "0" ] ; then
            echo "PAR2 not checked: par-check disabled or nzb-file does not contain any par-files" > "$nzbdir/message.txt"
      elif [ "$4" = "1" ] ; then
            echo "PAR2 checked and failed to repair" > "$nzbdir/message.txt"
      elif [ "$4" = "2" ] ; then
            echo "PAR2 checked and sucessfully repaired" > "$nzbdir/message.txt"
      elif [ "$4" = "3" ] ; then
            echo "PAR2 checked and can be repaired but repair is disabled" > "$nzbdir/message.txt"
      elif [ "$4" = "" ] ; then
            echo "No PAR2 returncode" > "$nzbdir/message.txt"
      fi
      if [ -f "$1/_brokenlog.txt" ] ; then
                echo  >> "$nzbdir/message.txt"
                echo "Broken Files:" >> "$nzbdir/message.txt"
            cat "$1/_brokenlog.txt" >> "$nzbdir/message.txt"
      fi
fi
 
if [ $UNRAR = "True" ] ; then
# PAUSE Server
        if [ $PauseServer = "True" ] ; then
                /opt/bin/nzbget -P
        fi
        cd "$dir"
        RARFILES=(`ls | grep -E [.][pP][Aa][Rr][Tt][0]*[1][.][Rr][Aa][Rr] | tr ' ' '§'`)
        number_rar=${#RARFILES[*]}
        if [ $number_rar -ge 1 ] ; then
                for b in "${RARFILES[@]}"
                do
                        rar=${b//§/ }
                        f=${rar/[.][pP][Aa][Rr][Tt][01]*[.][Rr][Aa][Rr]/}
                        destdir=$dest$f
                        mkdir "$destdir"
                        unrar x -y -o- -p- "$rar" "$destdir"
                        echo "UNRARRED $rar to $destdir" >> "$nzbdir/message.txt"
                done
        else
                RARFILES=(`ls | grep -E [.][Rr][Aa][Rr] | tr ' ' '§'`)
                number_rar=${#RARFILES[*]}
                if [ $number_rar -ge 1 ] ; then
                for b in "${RARFILES[@]}"
                do
                        rar=${b//§/ }
                        f=${rar/[.][Rr][Aa][Rr]/}
                        destdir=$dest$f
                        mkdir "$destdir"
                        unrar x -y -o- -p- "$rar" "$destdir"
                        echo "UNRARRED $rar to $destdir" >> "$nzbdir/message.txt"
                done
                fi
        chmod -R 766 "$destdir"
        fi
 
        # UN-Pause server
        if [ $PauseServer = "True" ] ; then
        /opt/bin/nzbget -U
        fi
fi
 
if [ $Sendmail = "True" ] ; then
      sendEmail -t $sendto -f $from -u $subject -s $server -o message-file="$nzbdir/message.txt" -q
fi
exit 0

---

But there's an issue with the 'declare' in rule 27... what can I do about this? Or if anyone has a working post-process script to unrar and clean up files, post it here, it seems there are more people interested!

The following script is used on popcornhour box.
It was not designed to be easily portable, so you need to change the absolute paths.

Code:

---

#!/bin/sh
DownloadDir="$1" 
NzbFile="$2"
ParCheck=$4
NzbState=$5 
ParFail=$6

# Make a logfile
log="$DownloadDir"/unrar.log
export PATH=$PATH:/opt/sybhttpd/localhost.drives/HARD_DISK/Download

# Check if all is downloaded and repaired
if [ "$NzbState" -eq 1 -a "$ParCheck" -eq 2 -a "$ParFail" -eq 0 ]
then
  cd "$DownloadDir"

# Make a temporary directory to store the unrarred files
  mkdir extracted
 
# Remove the Par files
  rm *.[pP][aA][rR]2
 
# Pause NZBGet download until script finishes
  /mnt/syb8634/bin/nzbget -P -c /opt/sybhttpd/localhost.drives/HARD_DISK/.nzbget/nzbget.conf
 
# Unrar the files (if any) to the temporary directory, if there are no rar files this will do nothing
      if (ls *.rar >/dev/null)
  then
  /mnt/syb8634/bin/unrar x -y -p- -o+ "*.rar"  ./extracted/
  fi
 
# Remove the rar files (Temporaly disabled just remove # to activate it)
#  rm *.r[0-9][0-9]
#  rm *.rar
#  rm *.s[0-9][0-9]
 
# Go to the temp directory and try to unrar again. 
# If there are any rars inside the extracted rars then these will no also be unrarred
  cd extracted
  if (ls *.rar >/dev/null)
  then
  /mnt/syb8634/bin/unrar x -y -p- -o+ "*.rar"
  fi
 
# Delete the Rar files (Temporaly disabled just remove # to activate it)
#  rm *.r[0-9][0-9]
#  rm *.rar
#  rm *.s[0-9][0-9]
 
# Move everything back to the Download folder
  mv * ..
  cd ..
 
# Clean up the temp folder
  rmdir extracted
  chmod -R a+rw .
  rm *.nzb
  rm *.1

# Rename img file to iso so the NMT can read it
# It will be renamed to .img.iso so you can see that it has been renamed
  if (ls *.img >/dev/null)
  then
  imgname=`find . -name "*.img" |awk -F/ '{print $NF}'`
  mv $imgname $imgname.iso
  fi 
 
 
# Unpause NZBGet
  /mnt/syb8634/bin/nzbget -U -c /opt/sybhttpd/localhost.drives/HARD_DISK/.nzbget/nzbget.conf

fi 
#################

---

My observations:
- the command "export PATH=$PATH:/opt/sybhttpd/localhost.drives/HARD_DISK/Download" is probably not needed;
- the commands to pause/unpause are optional, you may comment them out to allow nzbget download files during unraring.

That script actually works, I've tested it on popcornhour. It should work on asus as well.

The script was written by Philos and Werner from pocornhour forum. See that thread.

I understand, I know that it should work, but my log says:

Quote:

---

Thu Jul 31 18:26:07 2008 DETAIL Post-Process: /tmp/harddisk/torrent//.nzb/scripts/myscript.sh: /tmp/harddisk/torrent//.nzb/scripts/myscript.sh: 27: declare: not found
Thu Jul 31 18:26:07 2008 DETAIL Post-Process: /tmp/harddisk/torrent//.nzb/scripts/myscript.sh: /tmp/harddisk/torrent//.nzb/scripts/myscript.sh: 60: Syntax error: "(" unexpected (expecting "fi")

---

OK, I'll test it on asus.

cool, thanks for your effort!

This script (formatted version to view in browser, download link) works on asus. I tested it.

working great, thanks for the tip!
I also like the clean-up feature (added some of my own stuff to it as well).

Testing-version can be downloaded from SourceForge.

Hi all,

Since we are on an asus forum here, I wonder if anyone has succeeded to install newer nzbget versions on the Asus box. Command ikpg list only offers version 0.2.3-1 which installs perfectly but doesnot seem to work with nzbget-web. I tried installing newer versions 0.4.x-x but this fails since version 0.4 has some additional dependencies (libpar2, libncurses). I tried to find ipk packages for Olegs optware but didn't find them sofar. Is there somebody who knows where to find libpar2 and libncurses that work with the asus optware?

You need to install oleg firmware and set ipkg-path to oleg-branch of optware repository.
Detailed how to.

After that you should be able to install the latest stable version of nzbget (0.4.1) with "ipkg install nzbget".

Thanks Hugbug,

pointing to the right package library did the job and everything works fine now.:D

For more please visit nzbget forum.

To upgrade installed version:

Code:

---

ipkg update
ipkg upgrade nzbget

---