OpenBh 5.6 & Vu+ Zero

Welcome to openbh for vuzero
openbh 5.6 vuzero

vuzero login: root
Password:
root@vuzero:~# /usr/bin/wget -d --dns-timeout=10 --connect-timeout=30 http://feeds2.openbh.net/openbh/5.6/vuzero/vuzero/Packages.gz
Setting --dns-timeout (dnstimeout) to 10
Setting --connect-timeout (connecttimeout) to 30
DEBUG output created by Wget 1.25.0 on linux-gnu.

Reading HSTS entries from /home/root/.wget-hsts
Converted file name 'Packages.gz' (UTF-8) -> 'Packages.gz' (UTF-8)
--2026-02-03 07:19:09-- http://feeds2.openbh.net/openbh/5.6/vuzero/vuzero/Packages.gz
Resolving feeds2.openbh.net... 51.68.21.42
Caching feeds2.openbh.net => 51.68.21.42
Connecting to feeds2.openbh.net|51.68.21.42|:80... connected.
Created socket 3.
Releasing 0x004d3740 (new refcount 1).

---request begin---
GET /openbh/5.6/vuzero/vuzero/Packages.gz HTTP/1.1
Host: feeds2.openbh.net
User-Agent: Wget/1.25.0
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)
Date: Wed, 04 Feb 2026 22:02:05 GMT
Content-Type: application/octet-stream
Content-Length: 133358
Last-Modified: Tue, 03 Feb 2026 13:47:49 GMT
Connection: keep-alive
ETag: "6981fc85-208ee"
Accept-Ranges: bytes

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 133358 (130K) [application/octet-stream]
Saving to: ÔÇÿPackages.gzÔÇÖ

Packages.gz 100%[=================================================>] 130,23K --.-KB/s in 0,1s

2026-02-03 07:19:14 (1,15 MB/s) - ÔÇÿPackages.gzÔÇÖ saved [133358/133358]

root@vuzero:~#

==========================

. . . nothing. Always the same message.
 
Oooops! :rolleyes:
In the meantime I connected a USB Wi-Fi antenna (5370) and used my smartphone (another operator) as a hotspot and magically the feed for installing plugins works.
I don't know what to say!!! :oops:
 
When I switched back to the LAN connection, the problem recurred. :(
As soon as possible, I'll schedule an appointment with my internet provider (luckily, it's a local company with physical offices and technicians) to get an explanation and resolve the DNS timeout issue.
Or should I ask them for something else? :unsure:
Suggestions are welcome. ;)
Thanks
 
in 5.3 has been introduced that timeout.. to be honest it comes from oe-alliance... but it seems to me too aggressive.

Feel free to apply the workaround until the provider will answer
 
Welcome to openbh for vuzero
openbh 5.6 vuzero

vuzero login: root
Password:
root@vuzero:~# /usr/bin/wget -d --dns-timeout=10 --connect-timeout=30 http://feeds2.openbh.net/openbh/5.6/vuzero/vuzero/Packages.gz
Setting --dns-timeout (dnstimeout) to 10
Setting --connect-timeout (connecttimeout) to 30
DEBUG output created by Wget 1.25.0 on linux-gnu.

Reading HSTS entries from /home/root/.wget-hsts
Converted file name 'Packages.gz' (UTF-8) -> 'Packages.gz' (UTF-8)
--2026-02-03 07:19:09-- http://feeds2.openbh.net/openbh/5.6/vuzero/vuzero/Packages.gz
Resolving feeds2.openbh.net... 51.68.21.42
Caching feeds2.openbh.net => 51.68.21.42
Connecting to feeds2.openbh.net|51.68.21.42|:80... connected.
Created socket 3.
Releasing 0x004d3740 (new refcount 1).

---request begin---
GET /openbh/5.6/vuzero/vuzero/Packages.gz HTTP/1.1
Host: feeds2.openbh.net
User-Agent: Wget/1.25.0
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)
Date: Wed, 04 Feb 2026 22:02:05 GMT
Content-Type: application/octet-stream
Content-Length: 133358
Last-Modified: Tue, 03 Feb 2026 13:47:49 GMT
Connection: keep-alive
ETag: "6981fc85-208ee"
Accept-Ranges: bytes

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 133358 (130K) [application/octet-stream]
Saving to: ÔÇÿPackages.gzÔÇÖ

Packages.gz 100%[=================================================>] 130,23K --.-KB/s in 0,1s

2026-02-03 07:19:14 (1,15 MB/s) - ÔÇÿPackages.gzÔÇÖ saved [133358/133358]

root@vuzero:~#

==========================

. . . nothing. Always the same message.

thanks a timeout of 10 instead of 5 it would fix for you
 
Back
Top