Using ZyXEL packages (NSA-212)
Using MetaRepository it's possible to install ZyXEL packages on a Medion. However, not all packages work.
|BackupPlanner||Seems to work|
|DyDns||Seems to work|
|Gallery||Doesn't work||Page gives an error.|
|Google Drive||Not tested|
|NFS||Seems to work|
|Nzbget||Doesn't work||Needs another version of /usr/lib/libstdc++.so.6|
|PHP-MySQL-phpMyAdmin||Page loads, and gives a database error. I think it conflicts with build-in MySQL. But PHP seems to work.|
|Smart||Doesn't work||Needs another version of /usr/lib/libstdc++.so.6
Use the Medion package instead
|Syslog||Seems to work|
|Tftp||Seems to work|
|anyterm||Doesn't work||Needs another version of /usr/lib/libstdc++.so.6|
|ownCloud||Doesn't work||Kills httpd. Think it changes the configuration script, or adds an incompatible plugin to Apache.|
|pyLoad||Seems to work|
Note: Seems to work means the user interface works, I didn't test the underlying functionality.
On a ZyXEL box the package interface url is http://<ip-of-nas>/pkg/<package>. On my Medion it is http://<ip-of-nas>/r36258,/adv,/pkg/<package>. To solve this I added hotpatching to MetaRepository. The startscripts of other packages are hotpatched on start of MetaRepository, and on asking the url of MetaRepository itself. So if a new installed package uses a wrong url, refresh the page, to force the hotpatching.
Disabling malfunctioning packages
I advice to install Dropbear first, and to verify you can login over ssh, even after a reboot. When your webinterface dies, you can't enable the telnet backdoor anymore.
When a package is malfunctioning, and you can't disable it in the webinterface, you can disable it manually. Login over ssh, and execute
cd /usr/local/zy-pkgs/etc/init.d/ ls
Now you see a list of startscripts. Find the startscript which belongs to your target package, and execute:
packagescript shutdown packagescript disable reboot
Where you exchange 'packagescript' by the real name of the script.