opkg update issue

[l.j.nash]

Hi all,

I was trying to update my Humax box today but an error message briefly flashed up in the web interface indicating "HTTP/1.1 403 Forbidden" when trying to access "<http>://hpkg.tv/hdrfoxt2/base/Pacages.gz".

I've tried the telnet interface but receive the same error:

humax# wget http://hpkg.tv/hdrfoxt2/base/Packages.gz
Connecting to hpkg.tv (89.248.55.75:80)
wget: server returned error: HTTP/1.1 403 Forbidden

I can ping hpkg.tv from the telnet interface:

humax# ping hpkg.tv
PING hpkg.tv (89.248.55.75): 56 data bytes
64 bytes from 89.248.55.75: seq=0 ttl=243 time=21.302 ms
64 bytes from 89.248.55.75: seq=1 ttl=243 time=20.246 ms
64 bytes from 89.248.55.75: seq=2 ttl=243 time=21.247 ms
64 bytes from 89.248.55.75: seq=3 ttl=243 time=20.000 ms
64 bytes from 89.248.55.75: seq=4 ttl=243 time=22.000 ms

so I'm not sure what's wrong?

Any advice would be welcomed. Thanks.

Please note that I've had to put <> around http above, otherwise I couldn't post this message.

 

[prpr]

Works for me with wget:

humax ~ # cd /tmp
humax /tmp # wget -U "" http://hpkg.tv/hdrfoxt2/base/Packages.gz
--2024-12-29 11:26:01--  http://hpkg.tv/hdrfoxt2/base/Packages.gz
Resolving hpkg.tv... 2a00:5600:1600::50, 89.248.55.75
Connecting to hpkg.tv|2a00:5600:1600::50|:80... failed: Address family not supported by protocol.
Connecting to hpkg.tv|89.248.55.75|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18578 (18K) [application/octet-stream]
Saving to: 'Packages.gz'

Packages.gz                   100%[=================================================>]  18.14K  --.-KB/s    in 0.05s

2024-12-29 11:26:01 (346 KB/s) - 'Packages.gz' saved [18578/18578]

Works using opkg as well:

humax /tmp # opkg update
Downloading http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Inflating http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Updated list of available packages in /mod/var/opkg/base.

 

[/df]

The -U "" (ie, don't let on that the client is wget) is probably what makes the difference in the wget command. But IIRC we had problems before where the wrong, or an unexpected version of, wget was being invoked, due to PATH issues.

 

[l.j.nash]

Hi prpr and /df,

Thank you both for your replies. I tried out wget using -U "" which does work and successfully downloads Packages.gz.

humax# wget -U "" http://hpkg.tv/hdrfoxt2/base/Packages.gz
Connecting to hpkg.tv (89.248.55.75:80)
Packages.gz          100% |*******************************| 18478   0:00:00 ETA

However opkg update still doesn't work:

humax# opkg update
Downloading http://hpkg.tv/hdrfoxt2/base/Packages.gz.
wget: server returned error: HTTP/1.1 403 Forbidden
Collected errors:
 * opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/base/Packages.gz, wget returned 1.

I did a bit more digging and found a reference to opkg using /tmp/opkg-lists so I tried gunzip Packages.gz, then mv Packages opkg-lists (I downloaded Packages.gz to /tmp) and then tried opkg upgrade but that didn't work.

Do either of you know if its possible to use the downloaded Packages.gz to bypass the need for opkg update? Or how I check for PATH issues?

When I cat the Packages file I can see that my currently installed packages are really out of date!

humax# cat opkg-lists | grep auto-unprotect
Package: auto-unprotect
Filename: auto-unprotect_2.0.2_mipsel.opk
Depends: busybox,hmt,auto-unprotect

humax# cat opkg-lists | grep betaftpd
Package: betaftpd
Filename: betaftpd_0.0.8pre17-5_mipsel.opk

humax# cat opkg-lists | grep webif
Filename: webif_1.5.3-2_mipsel.opk
Depends: lighttpd(>=1.4.39),libutil,webif(>=1.2.7-2)

 

[prpr]

When I cat the Packages file I can see that my currently installed packages are really out of date!

So is your firmware I would expect then. You neglected to mention the version (like everybody else).
I expect you're on CF 2.something, which won't work. Upgrade to 1.03.12_mod_3.13

 

[l.j.nash]

You're correct. Sorry, I didn't think I would need to update the firmware in order to update the packages. I was running firmware v2.21 (build 1897) on a Humax Version 1.02.32.

Thanks again.

 

[Black Hole]

Sorry, I didn't think I would need to update the firmware in order to update the packages.

Well, yes. Clearly modern builds of packages will not necessarily be compatible with an out-of-date firmware foundation, otherwise it would not be necessary to issue updated firmware ever. But in your case, it was the package management which broke by being out of sync!

You can stick with the Humax 1.02.32 if that's what suits you, but keep the mod build up to the current main release (alternatively don't update the packages... or install new ones).

 

[prpr]

I didn't think I would need to update the firmware in order to update the packages. I was running firmware v2.21

2.21 is 11 years old. Surely you expect things to have changed (for the better) since then?
Even 3.00 is over 10 years old and package updates for 2.x stopped nearly 10 years ago.
Some references:
https://hummy.tv/forum/threads/cfw-2-21-customised-firmware-version-2-21.4455/post-55351
https://hummy.tv/forum/threads/cfw-3-00-customised-firmware-version-3-00-released.5216/
https://hummy.tv/forum/threads/no-m...r-custom-firmware-2-xx-after-march-2015.5867/