View Full Version : [VU+ Duo2] Hades possible WiFi issues
I've just flashed Hades and couldn't get the built in WiFi to be stable. Kept coming up with encryption unsupported, even though I was using exactly the same settings as with Apollo. Could someone take a look at it and see if it's a bug or my receiver playing up?
Cheers.
same here.WIFI not working even with encryption.Going back to apollo
thecaretaker
01-05-15, 22:51
Same here... :-(
OK,I correct that. The wifi is working. I can stream iptv. It is the plugin feeds where I get a message that the Lan isn't connected. Also the software update link says to allow unstable feeds pick that in the software update settings. I have done that and no joy.
Could it be due to plugin site has not been set up yet for the new image?
abu baniaz
01-05-15, 23:07
What encryption type too?
Tried WPA/WPA2 and WPA2 on its own. Sorry, forgot to enable logs.
thecaretaker
01-05-15, 23:33
log attached Hope this is useful
42253422544225542256
got WLAN working after setting up 4 times with wpa+wpa2.Seems OK (save) not workig as it should be.But not possible to find feeds for plugins so useless for the moment.
got WLAN working after setting up 4 times with wpa+wpa2.Seems OK (save) not working as it should be.Plugins not possible.Got back to english and cabled internet.Downloading fine and installing plugins.After that configured WIFI and working fine now.
only problem is downloading plugins on WIFI.Even CrossEPG is working fine now and box starting much faster.Thx guys for the update :lifting::thumbsup::thumbsup::thumbsup:
This wifi problem emerged already with the latest apollo versions in my ultimo. Software update and plugin download won't work with wifi, only with fixed lan. All the plugins work with wifi, the network is connected. This must be a software issue. It exludes the wifi.
Is there any update on this issue?
can one of you guy's run
ifconfig
in telnet
on ethernet box :
eth0 Link encap:Ethernet HWaddr 00:1D:EC:05:E1:DB
inet addr:192.168.1.110 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::21d:ecff:fe05:e1db/64 Scope:Link
inet6 addr: 2a02:a03f:24c4:7500:21d:ecff:fe05:e1db/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2309200 errors:0 dropped:3 overruns:0 frame:0
TX packets:3494637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:242475999 (231.2 MiB) TX bytes:4093303294 (3.8 GiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:478 errors:0 dropped:0 overruns:0 frame:0
TX packets:478 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:56493 (55.1 KiB) TX bytes:56493 (55.1 KiB)
On WIFI box :
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6216 (6.0 KiB) TX bytes:6216 (6.0 KiB)
wlan0 Link encap:Ethernet HWaddr 78:44:76:B5:5D:85
inet addr:192.168.1.120 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::7a44:76ff:feb5:5d85/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8096 errors:0 dropped:0 overruns:0 frame:0
TX packets:4392 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11865138 (11.3 MiB) TX bytes:402446 (393.0 KiB)
I'am getting the exact same as above
Ditto running vu solo SE and vu zero.
Andy_Hazza
02-05-15, 18:43
You all need to be hard wired instead of the shitty temperamental wifi dongles.
Sent from my iPhone using Tapatalk
This wifi problem emerged already with the latest apollo versions in my ultimo. Software update and plugin download won't work with wifi, only with fixed lan. All the plugins work with wifi, the network is connected. This must be a software issue. It exludes the wifi.Sounds as though the default route isn't set up, so it can't reach any system off its own network.
You all need to be hard wired instead of the shitty temperamental wifi dongles.
Sent from my iPhone using Tapatalk
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.
quote : You all need to be hard wired instead of the shitty temperamental wifi dongles
Bloody shit.In my VU duo2 there is standard WIFI and that is not working anymore to for plug ins.Not everybody has the possibility to have cables all over the house.
PS : worked fine before ,even with apollo 166.
Andy_Hazza
02-05-15, 19:14
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.
That's great to hear. Thanks for your time on it. Any idea when it'll be released?
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:
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:
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.
abu baniaz
03-05-15, 00:47
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
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.
If I'd not installed anything on my receiver, which I haven't,In which case you wouldn't have the problem, so this situation would not obtain.
Your comparison is flawed.I think not.
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.
abu baniaz
03-05-15, 01:10
@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
Situation would not obtain? You make no sense at all Then try using a dictionary...
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
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.
This fixed the problem for me. Thank you.
Also, the DNS2 had to be added, the same as DNS1. Then it is really fixed.
I've flashed Hades 005 but it's no improvement on this problem. Is there something I am missing?
deividuska
04-05-15, 22:23
I've flashed Hades 005 but it's no improvement on this problem. Is there something I am missing?
We same here :confused:
I've flashed Hades 005 but it's no improvement on this problem. Is there something I am missing?
yes a cat6 cable :thumbsup:
We same here :confused:
Do a manual setup of the wifi and use the file posted earlier by abu. For some reason the new file doesn't have the fix in it that abu's file does.
deividuska
04-05-15, 22:26
yes a cat6 cable :thumbsup:
Ha not funny :mad:
yes a cat6 cable :thumbsup:
cat6a is better lol
cat6a is better lol
only over a longer distance :)
deividuska
04-05-15, 22:31
cat6a is better lol
CAT7 is the daddy ;)
Do a manual setup of the wifi and use the file posted earlier by abu. For some reason the new file doesn't have the fix in it that abu's file does.
it could be the fix is still in dev, it will be pushed to master image soon.
I arranged it by configuring the ethernet and WIFI with the same adresses and setting them both ON.On installing ethernet set WOL also on.Working fine now without any tricks.
I arranged it by configuring the ethernet and WIFI with the same adresses and setting them both ON.On installing ethernet set WOL also on.Working fine now without any tricks.
is encryption still showing unsupported for you?
yes , but box is working as it should be.On WIFI I gave in my password from my router and connection is ok.Have internet and plugin updating possible.Streaming over WIFI or internet is also working.
I arranged it by configuring the ethernet and WIFI with the same adresses and setting them both ON.On installing ethernet set WOL also on.Working fine now without any tricks.
yes , but box is working as it should be.On WIFI I gave in my password from my router and connection is ok.Have internet and plugin updating possible.Streaming over WIFI or internet is also working.
Both WIFI & LAN using the same IP?
Both WIFI & LAN using the same IP?Shouldn't really matter. As long as the Wired interface is configured and running the errant code will think you have a network connexion on eth0 and allow you to continue. You don't even need to have a cable plugged in.
The the box will then actually use the working Wifi link.
abu baniaz
05-05-15, 00:58
IMO, there are two issues.
One is the issue on the software update. This has been fixed.
The other is the unsupported encryption type. The first does not matter if your wifi adpater is not connecting. Andy mentioned somethigng about routers having to use a certain encryption type for a connection to be established. Using "WPA or WPA2" does not work. "WPA" or "WPA2" should work.
Shouldn't really matter. As long as the Wired interface is configured and running the errant code will think you have a network connexion on eth0 and allow you to continue. You don't even need to have a cable plugged in.
The the box will then actually use the working Wifi link.
Nope, no two live interfaces should ever be configured to use the same IP address, only asking for more problems.
Please excuse my coding ignorance but, how has this bug crept in when it was working perfectly on Apollo? I must say I did notice it on my zero on build 166 but thought it was my crap dongle.
Please excuse my coding ignorance but, how has this bug crept in when it was working perfectly on Apollo? I must say I did notice it on my zero on build 166 but thought it was my crap dongle.
Think you need to accept bugs/issues can creep in when something is under constant development.
Think you need to accept bugs/issues can creep in when something is under constant development.
Please don't misunderstand me. It's purely curiosity. I'm fully aware that bugs/issues can and will creep in. I was just wondering how. I guess without doing a course on programming there isn't a way to explain it to someone without coding experience?
I haven't read every post in this thread, wifi is working, just access to online update and plugins via wifi is not, which I believe is fixed and should be in public build soon.
as said 10 times before : just configure the WIFI and the ethernet with the same parameters and set them both ON.Everything is working fine than.You can do all updates and wait until this bug is fixed. :thumbsup: :thumbsup: :mad: :bored:
There can be an issue with WiFi using DHCP. In some cases the Gateway is not configured.
You can fix it 2 ways:
- put the Gateway/router ip address in 2nd nameserver.
- Better way is to set DHCP off and fill in static an ip-address.
Set also 'use a gateway' to yes and fill in your gateway/router ip address.
After saving this configuration, you can set back to 'use DHCP = yes'.
You gateway ip-address will be remembered.
Also for WiFi security use WPA2.
Fix for this should be in Hades 006.
Outher than the wifi issues is the any more bugs
Updated to Hades Build 011 and now my wifi says unsupported encrytion and wont connect. Using Ralink rt2800usb. Any help appreciated :)
Updated to Hades Build 011 and now my wifi says unsupported encrytion and wont connect. Using Ralink rt2800usb. Any help appreciated :)
stop drinking so much...
:fart2:
Looks like my adapter is fried. Tryed it in PC.
Thanks
Wiz
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.