Hello. Received my WF2IR this afternoon and thought I'd share my problems and how I solved them (so far). Basically it seems like WPA2 and WEP 128-bit both don't work. I'm using a Belkin router with 802.11b/g. When I tried to set up with WPA2 (which was the protocol I've been using) the itach would not connect to my network (solid power LED after reboot). There are so many settings it was quite difficult to troubleshoot (DCHP and static tried, also tried removing all the default WEP keys even though I wasn't using them). Finally I noticed that it worked fine when I disabled my router's security... while this wasn't acceptable it showed me that it was a security problem, at least. So cycling through the options I finally found one that worked - 64-bit WEP... I entered all four keys manually and the passphrase I used to create them. The itach connected to the network and I just did a quick test to verify everything is working (it is). Now to program my remote...
82 comments
-
Josh Sherman @Sean - There should be no conflict when using a GC-100 with a WF2IR. The default IP address of the WiFi units is not the same as the default IP for hardwired units so this won't be an issue. If your unit works properly, then the IP address that you have set for it works. The only thing you will need to watch out for is IP address conflicts when using multiple wireless units on the network.
@Frederic - It sounds as though the access point is dropping the unit after a period of time. Do you have another wireless router or access point with which you could test to see if the same symptom presents? If the LED stops blinking entirely, then the unit has dropped from the network. What is the exact model of the Linksys device you are using?
-
Vasco I've received my WF2IR a couple of days ago and I'm still trying to connect it to my network. The only connection that is acceptable is infrastructure with fixed IP address and WPA enabled. This because of other hardware in the network and also other people who like to use open or bad encrypted WLAN networks in the neighborhood.
Before I bought the unit I read a lot on the internet about the WF2IR and find out that my D-Link would be any problem. Well, that is not true I need to say. I can not get it work with my D-Link 320 and I'm really not a nitwit with networks.
What I already did:
- Connect a pc to adhoc and configure the WF2IR - WORK
- Configure to infrastructure with fixed IP and WPA2 - LED BLINK / DO NOT WORK (this is what it must going to be)
- Configure to infrastructure with DHCP and WPA2 - DO NOT WORK
I'm sure that the WPA or WEB key's where correct (even copy/paste them to make sure). I used HEX values for the WEB keys, 10 character for 64bits and 26 characters for 128bits. The WEB key's typed with and without 0x leading in the HEX key. When the LED blinks I can also see at the status of the accesspoint that it's connected but cannot ping or load the webpage from the WF2IR.
Also the networkname will be a little to long if you look at the standard, 15 char max is the best because of NetBIOS enabled networks. Maybe using only the MAC ID as networkname will solve that because that are 12 chars or put only GC in front of the MAC ID. What I still missing in the network page of the configuration is a gateway and DNS setting.
Please provide a fix!
-
Vasco After posting I see some text is missing at the bullets.
Here the missing part:
- Configure to infrastructure with fixed IP and WEB 128 - LED BLINK / DO NOT WORK
- Configure to infrastructure with DHCP and WEB 128 - DO NOT WORK
- Configure to infrastructure with DHCP and WEB64 - DO NOT WORK
- Configure to infrastructure with fixed IP no security - WORK (but not acceptable)
Also an explanation why at gateway and DNS to the network configuration. I have a six networks with routing tables running in the bulding. Without a gateway only machines in the same network can access the WF2IR. -
Vasco And again, after posting I see some text is missing.
Here again the missing part:
- Configure to infrastructure with fixed IP and WEB 64 - LED BLINK / DO NOT WORK
Maybe create a fix for this website also ;-) -
Uwe Jeck Josh, I am having my WiFi2IR since March 2011 and was not able to use it in a secure way, by means not using it at all as an integrated unit in my WiFi setup. Already on 01 March you wrote in this threat to fix the problem until end March if not sooner. It is now July and the problem is still not fixed. People are still reporting the same or very similar problems.
Please be so kind and give us a clear status what is going on. When we can expect a new version of firmware which is able to handle the encryption protocol? Thanks for your help
-
Vasco I did some tests with two other accespoints this morning, here are the results.
Draytek Vigor 2900 (test with mixed and b-only mode):
- No security, Fixed IP - Blink and work
- WEB64, Fixed IP - Blink and work
- WEB128, Fixed IP - BLINK BUT DOESN'T WORK
- WPA2, Fixed IP - Blink and work
Netgear N150 (test with mixed and b-only mode):
- No security, Fixed IP - Blink and work
- WEB64, Fixed IP - Blink and work
- WEB128, Fixed IP - BLINK BUT DOESN'T WORK
- WPA2, Fixed IP - Blink and work
So I can conclude that the very well documented WiFi implementation is not correct in the WF2IR (and maybe also in all the other WF### modules). The WEB128 do not work at all on what kind of accesspoint I tested so far, even in b-only mode. I also will contact the reseller in Holland about this because I will do a final test this evening when I'm home with WPA2, and if it do not work I'll send it back. I pay (a lot of) money for this so it must work or it's not worth the money I spend.
I can only think about a mistake I made myself with the WPA2 because this work fine this morning with the two other accesspoints. If not, I tested this weekend a solution from a friend with an USB IR Transmitter connected to a Silex SX2000WG+ USB over WiFi Ethernet Server and that was working very well.
There is really some work for Global Caché to fix the WEB128 security in the firmware, that's for sure! -
Vasco Here are the results from my test yesterday evening at home with the WF2IR connecting to the D-Link 320.
- No security, Fixed IP - Blink and work
- WEB64, Fixed IP - Blink and work
- WEB128, Fixed IP - BLINK BUT DOESN'T WORK
- WPA2, Fixed IP - Blink and work (I turned AES to TKIP for this)
So I can tell that for my situation it's ok now, I tried to send some IR to my TV with HomeSeer and it goes well. But for all those people who cannot run WPA2 it is clear that there is a bug in the firmware when you need to use WEB128. On all three accesspoints it blinks but won't work when using WEB128. -
Josh Sherman Currently there are two known problems related to wireless network security, both of which are limited in scale and only affect some routers. The first is WEP 128. This bug has to do with authentication, which does not allow for a finalized connection to the network. This leaves the unit in a state where the router has communicated with it, shows up in the router table but is unable to communicate properly with the network. The other problem is related to disconnects from WPA/WPA2 networks. Currently there are no documented routers where WPA/WPA2 does not work, but some routers prevent units from reconnecting when the unit needs to reestablish its connection for any of the many reasons wireless connections reset. These are both being fixed in the -05 revision of the iTach firmware, which is still being processed by our engineering team. I will make sure to post on this thread when the release is finished and hopefully this will solve the problems you guys are seeing.
-
Catalin Actually your list of only two problems is not correct - the symptom you describe for WEP128 (device in router table but status LED solid green and no communication possible) also happens with WPA2. I just received my WF2IR today and I am experiencing the same problems as those described above, here are the details:
D-Link DIR655 router - SSID is broadcast, 802.11b is enabled, signal strength from WF2IR is 85%, security mode Auto (WPA or WPA2), cypher type TKIP or AES
WF2IR is set up in WPA mode with DHCP
The device appears in the router table with the correct MAC and a valid IP but the status LED does not blink but is on all the time, cannot ping WF2IR and iHelp cannot see it.
This is an existing WiFi network with other devices already on it and running in any mode but WPA2 is not acceptable. I know that people having no problems with the WF2IR do not post here but it would be interesting to know what percentage of users do have problems with this device right out of the box.
Is there a firmware update addressing these issues planned in the immediate future and if yes, how can we update the firmware if we cannot connect to the device?
-
Catalin Here is an update - some minor progress but no cigar. Setting up the WF2IR with a static IP and WPA2 partially works. The WF2IR responds to pings and the web server can now be accessed. However, iHelp is unable to find the device so I assume it is still useless. I tried to turn off the firewall but that didn't help either. At this point I am out of things to try and this looks like $100 down the drain.
Josh, I think you are heavily underestimating the issues when you say that there are only two problems and they are limited in scale. You are selling a device that does not work as advertised.
-
Catalin With security turned off and DHCP this is actually worse. I see the device in the router table and it gets a valid IP but the status LED doesn't blink and the web server doesn't work. This issue of getting an IP but not responding doesn't look like a security related problem at all at this point.
-
Vasco Catalin, I also had problems the first time setting up WPA2 to my D-Link 320 because of AES I guess. After I turned WPA2 AES to WPA2 TKIP it works well (for now but I hope for all time). After some search on internet about AES and TKIP I found that AES is not a WiFi standard where TKIP is. AES is a hardware encryption method where TKIP is a software method but is a slower solution.
The firmware need to come quickly for those users (4 months waiting is really to long for people who spend more than 100 dollar) and also the manuals/quick guides need an update with correct information. When you selling stuff for prices like this you're not at a hobby project anymore, hardware should be tested well and working before selling to the world. If, e.g. Sony, do things like this with there televisions now one will buy Sony anymore.
I agree with the others here that the problems need to be solved by Global Cache. They advertised with something (when it works well it's really great to use) on the internet and also at a shop in Holland where I bought the unit. I contacted the Dutch shop about this problem in the firmware and the known problems at this time. Luckily in europe we've got a 7 day policy law when something do not work as aspect we can return it and get our money back. I hope you have also a law like this too in the US, companies need to do there job otherwise they get back there stuff because of this law.
Do not understand me wrong, what Global Cache do with this kind of hardware is really great when it works. -
Josh Sherman When your unit is blinking and you are able to view the web server from the network, then your unit is successfully connected and you are only dealing with something blocking iHelp from seeing the network packets. When iHelp does not find a unit on the network, there are a few possible causes to the problem. First would be some sort of firewall related issue. iHelp joins the multicast group, which might be blocked by a PC firewall. A way to test this would be to disable any active firewall on your machine. Another possible cause would be some sort of multicast filtering on your network. The iTach discovery beacon is a UDP broadcast, which can be blocked by network settings. A way to check this would be to see if there is a different network to connect the unit to to see if the same result occurs, or possibly trying with a different PC on the same network.
Since iHelp is used to discover and upgrade units, you will only be able to update your unit's firmware if you can find what environment related issue is causing the problem in your network. -
Catalin Vasco,
The time I wasted trying to make this thing work is already worth more than $100 to me, so even if I return it and get my money back I am still behind. Here in NA you can get a full 802.11g router for less than $25 and it works right out of the box. We are paying over $100 for a WiFi end point that blinks some LEDs and we get to do the beta testing too! I was expecting more for my money.
Josh,
I have tried a WIndows 7 64-bit computer and a Windows XP one. In both cases turning off the firewall made no difference. I have enabled "Multicast Streams" in my D-Link DIR-655 router and that made no difference either, iHelp does not see the WF2IR.The automatic detection feature in iHelp is nice but in my case I already know what the WF2IR IP is, since static IP and WPA2 is the only combination that actually works for me. Making firmware update depend on iHelp being able to automatically recognize the device when I could tell it what the device IP is creates an unnecessary chicken and egg problem.
Is there anything else beside the WF2IR webserver (which works) and iHelp (which doesn't) that I can use to quickly test the device?
It looks like I will have to get another $25 wireless router to further test your $100 WiFi endpoint.
-
Catalin Here is the conclusion of my WF2IR saga. The WiFi connection works in WPA2 and Static IP mode, which is what I actually need. But I was simply lucky because no other combination works with my D-Link DIR655 router.
I gave up on making iHelp recognize the WF2IR - there is nothing more I can do to my router to make this work. This means no future firmware updates for me, I really think you should add a fixed IP mode to iHelp and not rely on the flaky automatic discovery process.
I am using iRule to control the WF2IR and the funny thing is that it has no problem discovering the unit in less than 2 seconds, so maybe the issue is still iHelp and not my router setup. Maybe you can ask your iRule partners how they do it and implement that in iHelp.
As a final conclusion, the hardware side of the WF2IR works well but this thing is overpriced, if the market takes off we will be inundated by $25 knock-offs from China. The software side, iHelp, iLearn and such however is a joke. If you are lucky and are able to make it work quickly the way you need it, fine, otherwise this is a big time sink and a major source of hair loss.
I just got an ASUS 802.11b/g wireless router/access port/bridge for $25 that is smaller than the WF2IR. The installation software is superb and it took less than 5 minutes to have it configured and running. It also comes with a real manual, on paper and on CD, not a book mark sign. Adding an IR sensor and driving a few IR blasters (the WF2IR only drives one, to force you to buy more $100 units) to this WiFi router should be no big deal.
When people start discovering that they can use their Apple/Android phones and tablets to get rid of the multitude of remote controls cluttering their coffee tables the demand will pick up and the $100 solution that takes a week to set up will go the way of the Pronto. Just look at iRule if you want to see the future of the remote control.
-
Josh Sherman Technically, iRule uses the same mechanism to discover units as the iHelp application. If your phone is not being blocked but your PC is, then you will need to look into your firewall settings to see if the iHelp program is blocked in any way. The idea of using a static IP address for iHelp upgrades is a good one and will be added to our engineering request listing for future revisions. Our units cost what they do because you are dealing with an American company with a product made in the USA. It sounds as though our unit is working for you, so please let us know if you have any difficulties or questions in the future.
-
Catalin As I already mentioned, I have turned off the firewall on multiple computers, both Win7 and WInXP and it did not help iHelp. But it is easier to blame your customers than fix your own software. The price might be American but I have seen Chinese products that worked much better. The unit is working because I am lucky and was able to find the only WiFi setting that actually works with my router, not because of the quality of your software.
I might sound bitter but I wasted so much time with this thing when it should have worked right out of the box. I live in North America too so my time is not cheap either. Let us know if you need more free beta testers.
-
Josh Sherman We are not in way speaking about blame, only reasons behind what you are seeing. Our intention is to help you with technical issues, and we apologize that you are unable to unblock whatever is preventing your computer from seeing the UDP broadcast beacon. Your complaints are heard and noted, but have no effect on the blocked status of your iHelp software. We recommend making sure your firewall is enabled, and going into the actual firewall settings to see if there is a way to make sure the network resource is available to the software. Our units are fully open platform, so feel free to read up on the discovery beacon, which is what iHelp and iRule both use to discover the unit. My guess would be that a custom piece of software running on your computer doing the same thing that iHelp does would be unable to discover the unit due to the same reasons stated before.
-
Vasco I agree with Catalin, the firmware/software is buggy and the customers need to find out what work with there accesspoints first. Any other WiFi device works out of the box with all kind of settings so running in a couple of minutes. The WF2IR cost me days before it was running like I would. I was not suspecting to do the testing for your company for a product with that price.
I've tried a Silex SX-2000WG (USB over ethernet/WiFi) with an USB-UIRT IR transmitter from a friend and I had that running in about 15 minutes. Doesn't mather what kind of router/accesspoint you're running with what kind of security at all. Yes, the combination I borrowed from that friend is cheaper to buy but I like the combination all in one very small device. It has not to be the cheapest solution for me. I'm a certified network engineer and know very well what I'm doing with network devices, firewalls, etc. Because it was even hard for me to get it work I will not advise others to buy a WF2IR add this time.
What I say earlier, the device is great but fix the firmware/software because not everybody is a die hard network specialist. -
Vasco What is the roadmap for the new firmware update?
People ask this earlier and you answered on March 1, 2011, and I quote; "We are currently working to fix the 128bit WEB encryption issue we are having with some routers. We plan to have an iTach firmware release handling this problem by month's end if not sooner."
Well that was in March, after my first post begin July someone noticed that there is still no update as promised and also July is running out. Please, give users a clear status what is going on. There is no clear communication to end users who invest money in your products and are ending with devices that still do not work because of problems in firmware.
When can we expect the new firmware that handle the problems? -
Josh Sherman Currently, we are in the QC phase of the firmware release, where the units go through intensive testing in order to be certified for release. This phase is implemented in order to find as many interaction differences with different routers and access points so that we will be able to eliminate as many of them as possible before the release. We apologize for the delays, but there have also been additions to the iTach firmware in regards to new unit functions which have greatly delayed the firmware revision process. We are currently slated to enter the final testing phase in the very near future, but chasing down bugs such as the WEP128 issue as well as others which have been found during intensive testing does take time. We cannot promise anything due to the nature of embedded programming, but we plan to have the firmware released by the end of this month.
-
greg ator Just wanted to add that I have WAP54G vers 2 by Linksys and it required OPEN security to get to work.....painful!
-
Josh Sherman Once you have confirmed that open security works properly, you can continue to complicate your setup by adding network settings to see if you are having a problem with a certain one. There are many times when users have problems with a certain setting which applies to a security type or something of that nature, and can be isolated and found by slowly adding more variables to the setup as you go. The first thing we recommend trying would be to add simple WEP64 security to the unit's settings first, then applying the same settings to the network (so as to prevent you having to default and reconfigure your unit from scratch). It is important to note that the shared key option should only be used if the router you are using explicitly shows that setting being used. If your unit's power LED begins blinking after the settings have been applied then the unit is successfully connected to the network. We currently do not have a router of the exact model you are using, but according to our testing documentation we have tested that router without any reported issues. Please let us know if you have difficulties getting this working and we will help you get this configured the way you want it.
-
Ulrich Eggert Any news about the new firmware? QC ok? Releasedate? :-)
I have a FRITZ!Box 7390 Router. FRITZ!Box (http://www.avm.de/en/Produkte/FRITZBox/index.html) is a very popular Router in D-A-CH. I have tried the configuration, whitch are explained in the comment above ^^, but no luck. Only for a couple of hours, after that the connection is lost. Restart WF2IR and/or the Router doesn't help. So I hope the new Firmware will fix my problem...
Sorry for my bad englisch... ;-)
-
Craig Lonie Hi
i have just received my itach ip2ir and wf21r units in the post tis morning .I have a problem which is neither my mac or my windows xp pc is picking up the wifi unitI have downloaded ihelp for both pc and mac and still it wont show on the networkIs there something im doing wrongThe mac is intel based running lion and is two years old and i got the ihelp etc programs from this site http://www.rmartijnr.eu/iTest/index.htmlThe xp pc is a million years old but still works and is running xp pro i have studied the tutorials at the itach website and roughly understand what im suppose to do to get these up and running but i really need the wifi unit to be visible on the network firstYou will probably have guessed im not in the IT game so if you could reply in as simple a way as possible with lots of pictures lol i should be able to get this up and running also i would prefer it to be running of the macMy thanks in advance
-
Josh Sherman When in default conditions, wireless units will begin broadcasting their adhoc network within about 30 seconds, at which point the unit's power LED will begin blinking once per second. If your unit does not do this, use a paperclip as is explained in the quickstart documentation to default your unit. If the problem persists, make sure the unit is not within range of a device which could be creating wireless interference, like a router or access point, as these can create sufficient noise to stop our units from broadcasting their wireless network.
In order to connect your wireless unit to your network, you will need to input the wireless settings of your network into the network page of your wireless unit. Once your unit reboots, the power LED of your unit will begin to cycle on and off to indicate wireless network connection. If your unit's power LED remains solid, then the unit is not connecting to the network. This either means that you have incorrectly input your network settings into the unit, or there is a setting on the network which is preventing connection. Something to check in these cases is the wireless radio mode of your router. Forcing the router into 802.11b only wireless mode may allow for connection, as our units use 802.11b type WiFi and some routers do not properly implement 802.11b mixed mode.
If iHelp is not finding your hardwired unit (or your wireless unit after you get it connected to the network), you will want to temporarily disable any firewall software on the computer you are using and see if that makes a difference. This will hopefully allow you to find the IP addresses of your units on the network which is what you need to set up any control software.
-
marc notelteirs My WF2IR does not broadcast a network.
I already did a reset but problem persists.
Any other tips?
-
Josh Sherman When a unit does not broadcast, you will want to move it away from any device which could be causing interference. When bringing up the adhoc network, it is possible for a radiating antenna to prevent our unit from fully broadcasting, but should not have any negative effect once the unit has connected to your network.
-
RobAGD Hello,
I am having a rather odd issue with my Wifi2IR unit. I can get at it via my 2 laptops and my next book, but I cant from my Android Phone.
I have set up the Wifi2IR and its got the address I assigned it and is accessible via that IP from other machines. What I am wondering is what protocols is it wanting to use ?
Also will the wifi2ir respond to pings?
Thanks
-Robert
-
RobAGD The unit is not in adhoc mode, it has been set up via a laptop for infrastructure the a static ip and the security key for the net work.
I can get into the unit via ip and a web browser from any pc on my net work, but can not from the android device. Now as an oddity I have not been able to get any pc to get a reply ping from the wifi2ir.
-Robert