aRFR on 2.0

I;m guessing that you are using the release version of 2.0  (build 149) . My arfr seems to work well with it . One of the earlier builds ( I think it

was build 136 had a glitch in it that allowed the arfr to see the master but not connect to it.  At least in the case of the Gio. That problem was fixed

a few builds later.  I had some problems as well because I  changed the name of the console at one point and forgot to update the arfr with

the new name.   It's worth double checking console names and ip addresses.   Hope you get it solved.

My aRFR on a Samsung tablet with ICS connects and runs fine on v2.0

Steve B.

Brooklyn College

i had both my samsung smartphone (android 2.3 i think) as well as my asus tablet (android 4.0.1) connect to a gio running 2.0 without problems

i had both my samsung smartphone (android 2.3 i think) as well as my asus tablet (android 4.0.1) connect to a gio running 2.0 without problems

Thanks for your responses, I'll keep investigating then. 

Try re-setting the password in aRFR for that console.  

As well, I sometimes have to go into the Settings and "find" the console again, then it'll let me connect.

This on the iRFR as well as aRFR.

SB

We've got them working now.

Upon further investigation, it seems that before 2.0, both Android phones were set up to obtain IP addresses via DHCP and got a 10.101.125.blah IP address from the router fine. (They should have been static addresses, like everything else on our system, but apparently many months ago when the operators first bought the app and started using their phones, the only option available in their phones' setup was DHCP - which seems odd to me but I don't do Android!).

When we upgraded to 2.0 on Friday, it seems that the router stopped giving out addresses in the correct range (they were the 169.blah range I think). We then discovered the option of Static had now appeared (had always been there?) in the phones. I gave them static addresses and it still didn't work. Today we realised that was because the Network Prefix Length was set as 24, not 16 (as our subnet mask is 255.255.0.0). So now it all works fine. (Why can't Android call it a subnet mask?!)

The DHCP versus Static thing....has something changed in 2.0 that would have stopped the router giving out addresses within the correct range? There's no option in our router's setup to specify a range. I'm afraid my knowledge of all that side of things is limited so would be interested to know how a router knows which range to give out, if there's no option to specify. Or has something else changed that would impact this?

Thanks,

Jane

169.254.x.x is the "Automatic Private" or "Automatic Link Local" address range, which most equipment will use if it doesn't get an answer to a DHCP request.

It sounds like the DHCP server got turned off.

Eos can't change settings in any WiFi router or access point, however Eos can act as a DHCP server so it may have been the Eos handing out IPs and not the router.

All our devices had DHCP turned off, although I think the address service on the RPU was turned on. I guess this must be where the wireless router was getting its IP range from...? As the network tab settings are slightly different now, I suppose this is why it stopped working.