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
-
RobAGD Ok there is something going on that just is not kosher.
The WinXp and Win7 PC can see and ping the iTach no issues.
NONE of my andorid devices can, pings just die, http into the ip gets a page not found.
While I can do what ever I want though a PC the iTest and iHelp find the devices there is something different about what the android devices are trying to do to reach the devices.
This has been tested on a netgear n300 and a Dlink 615 E3
I have tried no security, MAC address, DNS restriction and static ips
The ONLY way I have managed to get the android devices to see the iTach is by having Everything connected through my Evo Phone as a hot spot.
I need the ports it is trying to work over and how it is trying to make these connections.
The network is also locked to B only no G or N
-Robert
-
Josh Sherman Please make sure that your unit is fully up to date, as we currently have no known interaction issues with Android OS browsers (Dolphin, Firefox and stock Google). Web traffic goes over port 80, while command data goes to our units over TCP port 4998. If you continue to have problems, confirm the IP address of the Android device and make sure that you are in the same subnet with the unit as well.
-
RobAGD It is current firmware
I have tried Opera, Sky ( browser on the Fire ), Stock HTC browser and Ill be trying Firefox mobile and Dolphin.
I am not blocking anything on the dlink, and it cant be blocking the port as the itest/ihelp apps work on the windows boxes.
Here is a report from the Fire using Fing
http:://www.robagd.com/DVDP/tsr/Darkhold.html
1 is router
100 is Netbook
101 is Netbook
103 is the Fire
I'll take some screen shots of settings and more reports and report back tonight
-
RobAGD Ok here is the work from last night.
.254 is my Evo 4G running as a hot spot and everything connecting to that.
http://www.robagd.com/DVDP/tsr/itach1.png Shows current software version
http://www.robagd.com/DVDP/tsr/itach-Kindle-Evo.png Showing the iTach web page on the kindle
http://www.robagd.com/DVDP/tsr/ Kindel-Evo-iTach.png Shows how the Kindle sees the iTach and ports 80 and 4998 were open when I scanned it.
I am going to reset the router tonight, and try again but for some reason the android devices will not see the itach, everything else shows up.
anyways appreciate the help and ideas.
-Robert
http://www.robagd.com/DVDP/tsr/RobEvo2.html
Ihelp/ilearn have always worked from the windows machines.
-
Josh Sherman It sounds as though the iTach is working, and some Android devices (Kindle) are seeing the unit but you are running into an issue with your HTC. What version of the Droid OS are you running on the phone? Are you able to ping the phone from your network? Is your phone able to see the router's embedded web pages? Based on what you are saying, it sounds as though the problem is somewhere within the settings or firmware of the Evo.
-
RobAGD Not quite :
When I use the Evo as my hotspot ( think hub or router for shared internet ) everything works like it should, evo sees the itach and teh Kindle does as well and can send commends and I can http into the device.
When I connected everything to the dlink 615 or a netgear n300 the windows devices will see and interact with the itach, but the android ( Evo and Kindle ) will not see the itach. Everything has IPs and the router can ping the android devices and the itach but the android devices can not reach anything on the network.
I has set up the network with WAP2, none, WEP, DHCP, Static IP,s etc etc and i am finding it weird that BOTH routers have exactly the same behavior.
-Robert
-
Josh Sherman In situations like this, you may want to set up a computer that's directly connected to the router with Wireshark (www.wireshark.org). In order for you to see the traffic, you will need to set up the network with both a main router and a separate wireless access point. The wireless access point would be your current router, but only be set up as an access point. That way, the data from your wireless device will hit the access point, but still need to be sent to the router and you will see all the traffic. If you have problems analyzing your capture, you can post it back in this thread and we can take a look at the transaction.
-
RobAGD Welp here is the long and short of it :
Got fed up and flashed dd.wrt on the dlink and everything works.
Not sure what Netgear and dlink are blocking with their stock config software but dd-wrt fixed it. Everything was running with in 20 min after I flashed it with no issues.
-Robert
-
ckcrunch To pick up right where RobAGD left off - I have the exact same problem. My router is a TP-Link router with 3 additional wireless access points. Like RobAGD, I can ping and access the iTach web interface from my PC (connected via wire), as well as from my laptop and iphone (connected via wifi). I have tried all 3 wireless access points, and it works with my laptop and iphone.
However my kindle cannot access the iTach. A ping results in "Destination unreachable". Strangely, inside iRule on the kindle, the kindle can detect the gateway, so it is picking up the iTach broadcasts. I cannot send any irule commands from the kindle to the itach, so it looks like its a one-way issue.
I've copy and pasted the relevant wireshark capture when I try to ping the iTach from my kindle below (iTach is fixed IP at 192.168.1.201, my kindle is at 192.168.1.100:
No. Time Source Destination Protocol Length Info
158 81.005083 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 158: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)No. Time Source Destination Protocol Length Info
159 82.491169 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 159: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
160 83.490702 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 160: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
161 84.005313 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 161: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)No. Time Source Destination Protocol Length Info
162 84.490602 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 162: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
163 85.517710 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 163: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
164 86.514011 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 164: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
165 87.008212 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 165: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)No. Time Source Destination Protocol Length Info
166 87.514000 Private_5f:8a:5c Broadcast ARP 60 Who has 192.168.1.201? Tell 192.168.1.100Frame 166: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: Private_5f:8a:5c (f0:a2:25:5f:8a:5c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)No. Time Source Destination Protocol Length Info
167 88.677313 192.168.1.201 239.255.250.250 UDP 249 Source port: dddp Destination port: dddpFrame 167: 249 bytes on wire (1992 bits), 249 bytes captured (1992 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.1.201 (192.168.1.201), Dst: 239.255.250.250 (239.255.250.250)
User Datagram Protocol, Src Port: dddp (9131), Dst Port: dddp (9131)
Data (207 bytes)0000 41 4d 58 42 3c 2d 55 55 49 44 3d 47 6c 6f 62 61 AMXB<-UUID=Globa
0010 6c 43 61 63 68 65 5f 30 30 30 43 31 45 30 32 35 lCache_000C1E025
0020 41 38 41 3e 3c 2d 53 44 4b 43 6c 61 73 73 3d 55 A8A><-SDKClass=U
0030 74 69 6c 69 74 79 3e 3c 2d 4d 61 6b 65 3d 47 6c tility><-Make=Gl
0040 6f 62 61 6c 43 61 63 68 65 3e 3c 2d 4d 6f 64 65 obalCache><-Mode
0050 6c 3d 69 54 61 63 68 57 46 32 49 52 3e 3c 2d 52 l=iTachWF2IR><-R
0060 65 76 69 73 69 6f 6e 3d 37 31 30 2d 31 30 30 31 evision=710-1001
0070 2d 30 35 3e 3c 2d 50 6b 67 5f 4c 65 76 65 6c 3d -05><-Pkg_Level=
0080 47 43 50 4b 30 30 32 3e 3c 2d 43 6f 6e 66 69 67 GCPK002><-Config
0090 2d 55 52 4c 3d 68 74 74 70 3a 2f 2f 31 39 32 2e -URL=http://192.
00a0 31 36 38 2e 31 2e 32 30 31 3e 3c 2d 50 43 42 5f 168.1.201><-PCB_
00b0 50 4e 3d 30 32 35 2d 30 30 32 36 2d 30 36 3e 3c PN=025-0026-06><
00c0 2d 53 74 61 74 75 73 3d 52 65 61 64 79 3e 0d -Status=Ready>.No. Time Source Destination Protocol Length Info
168 90.005850 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 168: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)No. Time Source Destination Protocol Length Info
169 93.005971 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 169: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)No. Time Source Destination Protocol Length Info
170 96.006153 GlobalCa_02:5a:8a Broadcast ARP 60 Gratuitous ARP for 192.168.1.201 (Reply)Frame 170: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: GlobalCa_02:5a:8a (00:0c:1e:02:5a:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP) -
RobAGD I have no idea what android is doing to muck up things but its at the router level.
Go see if you can load dd-wrt onto your router and see if that will sort you out.
-Robert
-
ckcrunch Unfortunately my router is not dd-wrt compatible, so I wanted to see if the Global Cache guys can figure it out. If they can't, I am going to buy a new router (they are so cheap nowadays...)
An update - I did some more troubleshooting:
- I have 3 wireless access points and a router. The WF2IR is connected to one of the access points.
Router -- AP1 -- wireless bridge-- AP3
|__ AP2
The router runs the DHCP server, with the WF2IR's MAC reserved with a fixed IP
The WF2IR is connected to AP3. Interestingly, AP1, AP2, and AP3 can all ping the WF2IR, but the router cannot (returns "destination not reachable").
Trying to isolate the problem, I moved the DHCP server to AP1. This did not solve the problem.
-
Josh Sherman Is it possible for you to set a static ARP entry in the main router? It is possible that the router is not seeing the ARP replies from our wireless unit which could be resolved by adding the entry manually into the router or computer with which you are trying to reach the unit.
-
ckcrunch I tried setting a static ARP entry and unfortunately it did not work.
Another piece of interesting troubleshooting, if my iPhone connects to the router's wireless AP, it cannot connect to the iTach (ping or otherwise), but if it connects to any other AP, it can connect without any problems. However, the kindle still cannot access the iTach no matter which AP it is connected to.
-
Gianluca Meardi *** CHANNEL SOLUTION *** I give you quite a simple possible solution, 'cos I got crazy when I recently bought a new (top line) router, the new Netgear R7000 Nighthawk. After setting up the new wifi network the WF2IR didn't connect anymore... I tried (really) everything... and only two minutes ago I understood it was a CHANNEL problem. My new router automatically chose channel 13 for wifi b/g (because of other interfering networks around my house): the global cache device can ONLY MANAGE UP TO CHANNEL 11. As soon as I manually switched the router on ch11, it worked again, immediately. -
Walter Komorowski I set up the wifi2ir about 2 weeks ago. It was working dine until tonight. Now I can no longer connect to it. ihelp shows it it receiving packets from its its ip. My router shows it to be connected, the light is blinking slowly green, but I can not connect via a web page. Went through the set up process again 3 times, static ip, dhcp, different static ip. It worked fine yesterday. No other issues on my network. Advice?
-
Walter Komorowski it may not be clear in my comment. The unit worked fine and connected to homeseer, was accessible via the web, then last night it no longer worked. It connects to the network, but is not accessible. It pings to ihelp but unless I reset it, I can not connect.
