Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo2] Hades possible WiFi issues

Your posts are usually sensible but on this ocassion you may wish to wind your neck in. Some people do not have the ability to hard wire and have bought a WiFi compatible receiver to use the WiFi part of it. It works in the Duo² flawlessly if the image is working properly so please stop moaning at others for using THEIR receivers the way THEY choose to use them.

I hold my hands up and apologise. I on a personal note haven't had much success with wifi dongles (and thats to do with the house layout more than anything) and much prefer hard wired, but you are right and I take back what I said. Soz Walt and others.


Sent from my iPhone using Tapatalk
 
I read that this wifi issue was also in later builds of apollo (but not earlier builds) and for some reason seems to only affect plugins, other things requiring internet access work fine!
 
It appears that this issue is in other images too. I hope a fix is found quickly as all my receivers run on WiFi. :(
 
should be fixed for next build.
 
should be fixed for next build.
Which might be a probelm in itself, given that you can't do an update if you have a Wifi connexion.
So you'd need to download elsewhere and flash via USB?

FWIW I've just finished testing my system with it's Wifi (which I've never used until today as I have a wired route next to the box). If I only have a Wifi connexion then an attempt at a Software Update produces this message:
Code:
  Your Miraclebox Premium Twin has no network access,
  please check your network settings and make sure you
  have network cable connected and try again.
If I then configure the wired interface as well the Software Update works (but there is nothing to do). And that is with the actual LAN cable unplugged!! (I'd forgotten I'd done that). So it does actually use the Wifi connexion.

So I'd guess that the issue isn't (wasn't) with the Wifi per se, but with the Software Update code checking for a specific interface rather than just trying to use the network? And the heck didn't work anyway.
 
Which might be a probelm in itself, given that you can't do an update if you have a Wifi connexion.
So you'd need to download elsewhere and flash via USB?

FWIW I've just finished testing my system with it's Wifi (which I've never used until today as I have a wired route next to the box). If I only have a Wifi connexion then an attempt at a Software Update produces this message:
Code:
  Your Miraclebox Premium Twin has no network access,
  please check your network settings and make sure you
  have network cable connected and try again.
If I then configure the wired interface as well the Software Update works (but there is nothing to do). And that is with the actual LAN cable unplugged!! (I'd forgotten I'd done that). So it does actually use the Wifi connexion.

So I'd guess that the issue isn't (wasn't) with the Wifi per se, but with the Software Update code checking for a specific interface rather than just trying to use the network? And the heck didn't work anyway.

Surely it's common sense that if you have issues with build 004 then you'd download build 005 and flash that rather than updating from 004.
 
Surely it's common sense that if you have issues with build 004 then you'd download build 005 and flash that rather than updating from 004.
So, anytime there is a problem in MS Windows you re-install from scratch with a fixed version??
Personally I'd fix a software bug by updating that software, and that just means overwriting the bugged files with new ones.
 
So, anytime there is a problem in MS Windows you re-install from scratch with a fixed version??
Personally I'd fix a software bug by updating that software, and that just means overwriting the bugged files with new ones.
If I'd not installed anything on my receiver, which I haven't, then yes of course you'd start again with the fixed build. Your comparison is flawed.
 
An update is fine.
Flashing fresh is fine too. Although I would prefer update.

If you want to replace the file, extract and place in the following location: /usr/lib/enigma2/python/Components
 

Attachments

An update is fine.
Flashing fresh is fine too. Although I would prefer update.

If you want to replace the file, extract and place in the following location: /usr/lib/enigma2/python/Components
Is this the fix for the WiFi problem? I've gone back to Apollo 166, hence the fresh flash required regardless of which build I flash.
 
In which case you wouldn't have the problem, so this situation would not obtain.
I think not.
Situation would not obtain? You make no sense at all and Tbh, you're not offering any help to anyone in this thread. so please leave the mods and coders to offer the help and support that they're so good at. Thanks.
 
@Walt, just to let you know that @Birdman has inputted some changes that are already in the image.

Can we a draw a line under this please? You are both right.

Many thanks
 
Sounds as though the default route isn't set up, so it can't reach any system off its own network.

While testing an USB wifi adapter, I had the same problem. Gateway ip-adress was not set.
Change the ip number of the 2nd nameserver into the ip number of your gateway (router).
Only use WPA2.

It's just a work-around. It needs further investigation.
 
An update is fine.
Flashing fresh is fine too. Although I would prefer update.

If you want to replace the file, extract and place in the following location: /usr/lib/enigma2/python/Components

This fixed the problem for me. Thank you.
 
I just put this file in and still get message no Unconfirmed IP address but can connect with my computer so very confused!
Now have put the ip address from the router in and it works fine as Peterj says above,
Thanks
 
Last edited:
had the same problem.Just configuring the ethernet interface identical to WIFI and let the box use them both did the trick.Simple but not normal.(just use WOL also when programmin)
 
While testing an USB wifi adapter, I had the same problem. Gateway ip-adress was not set.
Change the ip number of the 2nd nameserver into the ip number of your gateway (router).
Only use WPA2.

It's just a work-around. It needs further investigation.

I'll give that a go later. Thanks for your testing.
 

OpenViX Feeds Status

Back
Top