NSA325-v2 - Issues installing Entware-ng repository - install SMB v2

Options
marfalk
marfalk Posts: 5 image  Freshman Member
First Comment
in Personal Cloud Storage

Hi all,

On my NSA325-v2 NAS I have successfully (re)installed the Mijzelf Meta Repository. I can see all the packages from both (fw4_stock and fw4) repositories listed.

Now I am trying to install the Entware-ng repository. My final goal is the enable the Samba replacement for the SMBv2 protocol.

From the Entware-ng repository install log, I was able to figure out that wget fails to establish an https connection. I edited the Entware-ng script in /usr/local/zy-pkgs/etc/init.d/ and replaced wget with curl -k -L, but now I get the following errors: 

[09:47:27]     Info: Basic packages installation...

[09:47:28]     Collected errors:

[09:47:28]     * opkg_download: Failed to download https://zyxel.ddnss.eu/Users/Mijzelf/Entware-ng/binaries/armv5/Packages.gz, wget returned 1.

[09:47:28]     Downloading http://pkg.entware.net/binaries/armv5/Packages.gz.

[09:47:28]     Updated list of available packages in /opt/var/opkg-lists/packages.

[09:47:28]     Downloading https://zyxel.ddnss.eu/Users/Mijzelf/Entware-ng/binaries/armv5/Packages.gz.

[09:47:28]     Collected errors:

[09:47:28]     * opkg_install_cmd: Cannot install package kernel-2.6.24-support.

[09:47:28]     Unknown package 'kernel-2.6.24-support'.

Please can anyone help me solve this?

Thank you in advance

Accepted Solution

  • Mijzelf
    Mijzelf Posts: 3,051 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    Answer ✓

    I think the server has been reconfigured. This redirect has not always been there, else MetaRepository couldn't have worked.

    I'll try to contact the maintainer.

All Replies

  • Mijzelf
    Mijzelf Posts: 3,051 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary

    Maybe you'd better change https to http. The installer uses firmware curl/wget, and I can imagine it can't handle the encryption used.

  • marfalk
    marfalk Posts: 5 image  Freshman Member
    First Comment

    Hi Mijzelf,

    thank you for your reply. The reason why I tried to use "https" instead of "http" is that if I specify "http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/" and "http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4_stock_packages/" in the MetaRepository configuration page, the packages list stays empty (of course I clicked the "Retrieve packages list" button again). Here is the log from /admin/zy-pkgs/MetaRepository:

    HandleZYPKG_INFO /NSA325-v2/4.80/zypkg
    
FindApp md5sum found /sbin/md5sum
    
ReadConfig Repositories
    
Start of block
    
http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4_stock_packages/ ZyXEL
    
http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ Mijzelf
    
/i-data/md0/admin/MyRepo/ Local
    
End of block
    
9 start: 09:20:27
    
7 start: 09:20:27
    
8 start: 09:20:27
    
7: FetchZYPKG_INFO /i-data/md0/admin/MyRepo/ 7 Local
    
9: FetchZYPKG_INFO http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4_stock_packages/ 9 ZyXEL
    
7: FindApp curl found /usr/bin/curl
    
8: FetchZYPKG_INFO http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ 8 Mijzelf
    
7: Fetch /i-data/md0/admin/MyRepo/ZYPKG_INFO.tgz /i-data/md0/admin/zy-pkgs/MetaRepository/i-data_md0_admin_MyRepo.tmp failed
    
7: Fetch /i-data/md0/admin/MyRepo/ZYPKGS /i-data/md0/admin/zy-pkgs/MetaRepository/i-data_md0_admin_MyRepo.tmp failed
    
8: FindApp curl found /usr/bin/curl
    
7: Failed
    
7 stop: 09:20:27
    
9: FindApp curl found /usr/bin/curl
    
9: Fetch http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4_stock_packages/ZYPKG_INFO.tgz /i-data/md0/admin/zy-pkgs/MetaRepository/http___zyxel.ddnss.eu_Users_Mijzelf_zypkg-repo_fw4_stock_packages_.tmp succeeded
    
8: Fetch http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz /i-data/md0/admin/zy-pkgs/MetaRepository/http___zyxel.ddnss.eu_Users_Mijzelf_zypkg-repo_fw4_.tmp succeeded
    
9: tar: invalid tar magic
    
8: tar: invalid tar magic
    
9: rm: can't remove '/i-data/md0/admin/zy-pkgs/MetaRepository/http___zyxel.ddnss.eu_Users_Mijzelf_zypkg-repo_fw4_stock_packages_.400.md5': No such file or directory
    
8: rm: can't remove '/i-data/md0/admin/zy-pkgs/MetaRepository/http___zyxel.ddnss.eu_Users_Mijzelf_zypkg-repo_fw4_.400.md5': No such file or directory
    
9 stop: 09:20:27
    
8 stop: 09:20:27
    
Pushlist...
    
ReadConfig Pushlist
    
Start of block
    
End of block
    
Blacklist...
    
ReadConfig Blacklist
    
Start of block
    
YouNameIt
    
End of block
    
/bin/sed -i s/^YouNameIt/#YouNameIt/I /i-data/md0/admin/zy-pkgs/MetaRepository/NSA325-v2/4.80/zypkg/List.19030
    
Sort...
    
Choose packages...
    
Choose DEPS...
    
Create ZYPKG_INFO.tgz
    
TarHeader
    
FindApp curl found /usr/bin/curl
    
Fetch /i-data/md0/admin/zy-pkgs/MetaRepository/NSA325-v2/4.80/zypkg/ZYPKG_INFO.tgz - succeeded
  • Mijzelf
    Mijzelf Posts: 3,051 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary

    This is weird.

    8: Fetch http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz /i-data/md0/admin/zy-pkgs/MetaRepository/http___zyxel.ddnss.eu_Users_Mijzelf_zypkg-repo_fw4_.tmp succeeded
8: tar: invalid tar magic

    MetaRepository first tries to download ZYPKG_INFO.tgz, and if that fails, it tries ZYPKGS. On zyxel.ddnss.eu there is no ZYPKG_INFO.tgz, so that yields a 404. But in your case it doesn't. According to curl the download succeeded, so MetaRepository continues to unpack it, but the downloaded file isn't a tar archive.

    Why doesn't you box get a 404? Is it behind some transparent proxy or fancy firewall? What happens if you in the same network try to download http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz in a browser?

  • marfalk
    marfalk Posts: 5 image  Freshman Member
    First Comment
    edited March 22

    Thank you again. I have no firewall here. If I try to download http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz in a browser I get a 404 Not Found but before it is redirected to the https version of the same url.

    If I connect to my NAS via telnet, this is the curl verbose output:

    ~ # curl -v http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz >/dev/null

    • About to connect() to zyxel.ddnss.eu port 80 (#0)
    • Trying 158.101.164.98... connected
    • Connected to zyxel.ddnss.eu (158.101.164.98) port 80 (#0)

    GET /Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz HTTP/1.1
    User-Agent: curl/7.18.2 (arm-unknown-none) libcurl/7.18.2 OpenSSL/1.0.1j zlib/1.2.5
    Host: zyxel.ddnss.eu
    Accept:    /

    < HTTP/1.1 301 Moved Permanently


    < Date: Sat, 21 Mar 2026 20:20:55 GMT

    < Server: Apache/2.4.58 (Ubuntu)

    < Location: https://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz

    < Content-Length: 354

    < Content-Type: text/html; charset=iso-8859-1

    <
    { [data not shown]
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    100 354 100 354 0 0 5222 0 --:--:-- --:--:-- --:--:-- 0* Connection #0 to host zyxel.ddnss.eu left intact

    • Closing connection #0

    As you can see, it seems not to follow the redirect. As a matter of fact this is the html page it gets:

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head>
    <title>    301 Moved Permanently</title>
    </head><body>

    <h1>Moved Permanently</h1>
    <p>The document has moved <a href="https://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz">here</a>.</p>
    <hr>
    <address>Apache/2.4.58 (Ubuntu) Server at zyxel.ddnss.eu Port 80</address>

    </body></html>

    This is the reason why it does not get a 404 Not Found.

    If I try adding the -Lk parameters to the curl command:

    curl -v -Lk http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/fw4/ZYPKG_INFO.tgz >/dev/null

    then it follows the redirect, it ignores the https certificate so that finally it gets the 404 Not Found response:

    < HTTP/1.1 404 Not Found
    
< Date: Sat, 21 Mar 2026 20:34:02 GMT
    
< Server: Apache/2.4.58 (Ubuntu)
    
< Content-Length: 277
    
< Content-Type: text/html; charset=iso-8859-1

    NSA325v2 is not able to deal with https certificates: a plain curl (without -Lk options) is not enough to make it fulfill a download request successfully.

    This behaviour explains why when the http://zyxel.ddnss.eu used to deliver its content over http ONLY (not https), NSA325v2 had no issues going through the whole process of installing the Entware-ng repository.

  • Mijzelf
    Mijzelf Posts: 3,051 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    Answer ✓

    I think the server has been reconfigured. This redirect has not always been there, else MetaRepository couldn't have worked.

    I'll try to contact the maintainer.

  • marfalk
    marfalk Posts: 5 image  Freshman Member
    First Comment

    Thank you so much, Mijzelf!

    I can confirm that now the site is using http only. I was able to install the Entware-ng repository and the samba-replacement package for the SMBv2 protocol.

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）