Reef Angel Forum

Hey everyone, running into an issue here that I can't crack. I have a fairly advanced grasp of networking so i'm hoping it's just my inexperience with the system keeping me from getting this to connect.

After setting up the wifi module successfully on my old router, I can't get it to connect successfully on a new router i've purchased. Router is a Cisco N750 dual band router. I believe that the wifi addon can't connect to my router by the SSID, as i'm getting the same results in the Wifi_Utility program when i use the correct SSID or an invalid SSID, has any one run into this before with newer routers?

when running the wifi_Utility program, it's assigning an IP of 10.1.10.95 instead of my local network of 192.168.1.1/50, i'm assuming this specific IP address is an error code. Any idea what it stands for?

I've gone through this process before and it's not that difficult. The new router is transmitting all channels (b/g/n), any chance that there's an issue or feature keeping the wifi module from connecting during setup?

Seeing if anyone has encountered this before and if so what the resolution was (or if I need to use a program other than the wifi_Utility program).

I tried using dave's wifi setup program from github, but that is also not able to connect or configure the wifi addon. I'm getting the following when trying to save settings. Any Idea what the BAD CONFIG is saying? I have the wifi addon isolated to the 2.4ghz band of the router. My router is set to WPA2 /WPA Mixed mode.

set w a 4

AOK
<4.00> set w p nofatchicks

AOK
<4.00> set w s The2400Club

AOK
<4.00> save

Storing in config
*BAD CONFIG*
<4.00> reboot

*Reboot*

And here's the current wifi settings from greg's program:

CMD
get ip

IF=DOWN
DHCP=ON
IP=10.1.10.95:80
NM=255.255.255.0
GW=10.1.10.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0
<4.00> get w

SSID=The2400Club
Chan=0
ExtAnt=0
Join=1
Auth=MIXED
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=0
Passphrase=nofatchicks
EAP_Id=
EAP_User=

Thanks for the help! Please let me know if you need any more information!

for some reason ( or a another nearby router) is putting out a 10.1.10.X address. My Comcast cable box\router does that. What address is your local PC? On the 192 network, or on the 10.1? Do you have a cisco\linksys or some other kind of router looked to a cable modem? THat would probably be what's causing it. I ended up getting rid of my second router and just letting the comcast box doe the dhcp, the wifi, etc.

I don't think it's getting the IP from another router. It does say the interface is "DOWN".

Looks pretty similar to my config.
The only difference is mine is explicitly using "Auth=WPA1", though the AP is "WPA2/WPA Mixed Mode". Interestingly, I thought I set it to "Mixed WPA1 & WPA2-PSK" originally (set w a 3), perhaps the device changed it after it's first negotiation, or maybe I'm just crazy?
(Linksys E3200 dual-band here, I think that qualifies as "newer"-ish)

I also get *BAD CONFIG* ... haven't figured out exactly what it means yet.

Interestingly, you're doing "set w a 4", which the documentation says is "WPA2-PSK", but it shows up as "MIXED" afterward.
Also worth noting, the WiFly documentation says "WPA2-PSK (AES only)"-- I can't find any documentation about whether the N750 supports TKIP or AES (or both) for WPA2-PSK, maybe that's worth checking ?


Edit: I also had a 10.*.*.* address before the device connected for the first time.

The cisco routers now have a guest network. I know my cisco gives a range in the 10.1.xxx.yyy range. I would make sure you are hitting the right sid.

Can you ping the ip given from your workstation?

I have a Cisco N750 router.
I tried connecting to the 2.4ghz band.
pinging 10.1.10.95 doesn't resolve to anything.

I feel like if I was able to connect to the router i would get a valid IP in my local block, hence the weird 10.1 address. There are no other routers in my house besides my main one, and no ad-hoc or other networks within range.

I'm strangely also having problems with 2 of my laptops, but my windows phone, ipad, laptop with an intel wireless adapter, TV, and printer all can connect without issues to my router. The laptop with a broadcom and Atheros wireless adapters can't connect. Baffling.

Is there a way to tell what the current driver version is of the wifi addon? If not I might just try updating to the latest driver from the wifly site and going through the install process again. Since it's displaying the same issues as these 2 laptops i'm thinking it has to be adapter related.

Do you know how to use a serial terminal? Like putty or tera term?

Your logic sounds a bit flawed to me...you have two laptops that can't connect either yet it must be the adapter? I would scrub the router config... As i said that ip block is similar to what I get on my Cisco so that doesn't seem out of the ordinary.

Fwiw, i would start with making sure the guest network is disabled and I would also try another auth type on the router.

I know that the wifi adapter can get hung up on one of the authentication methods. I forget the specific mode though. Also some older adapters have trouble with some of the modes hence why your other devices may be having issues.

My feeling is that the module may be having trouble with the auth on your main net and getting joined to the guest one inadvertently which is why its getting an ip. But since it's on the guest it would be isolated and unpingable from the rest of your network.

I know you said you only had one ssid, but it may be possible that both are advertising under the same setting.

This is my hunch whats going on here.

I haven't used putty in years but i'll download it now.

@lnevo, sorry I wasn't explaining myself better. I was trying to say that I have 2 laptops that can't connect, the addon may have the same incompatibility as the laptops with this router, not that the addon is in any way responsible for that.

Also, reconfigured my router. Here's the current setup:
Encryption: AES
Type: WPA2-Personal only.
Wireless mode: Mixed (i'm assuming this means b/g/n)
Guest access: disabled.
bandwidth: auto (assuming this is 20/40)

I fired up my old router to take a look at it's settings, It's set to:
TKIP
WPA/WPA2-Personal (PSK)
802.11b&802.11g&802.11n
bandwidth: 20/40
802.11e/WMM QoS: On

The new router doesn't allow me to set TKIP vs AES.

I've run the wifi_utility program again under this setup and it gets the same results as above.

Opening Serial Port...
Verifying speed at 9600 baud
Connected to serial port COM3
> $$$
> set u b 57600
> set s p 0
> save
> reboot
Verifying speed at 57600 baud
Removing connection to COM3
Connected to serial port COM3
> $$$
< CMD
Wifi is communicating at 57600 baud rate

> reboot
< reboot
Removing connection to COM3
---------------------------------------------------------------------
Wifi Attachment Connected to COM3
---------------------------------------------------------------------

Opening Serial Port...
Connected to serial port COM3
> $$$
< CMD
> ls
< ls
<
< FL# SIZ FLAGS
< 2 79680 3 WiFly_GSX-2.36
< 22 -1 10 config
< 23 -1 10 user
< 34 83648 3 WiFly_GSX-2.45
< 78 86328 3 wifly-GSX-400
< 79 46632 3 wps_app-GSX-131
< 80 66240 3 eap_app-GSX-101
< 81 74920 3 web_app-GSX-106
< 82 37282 0 web_config.html
< 83 512 0 link.html
< 84 7268 0 logo.png
<
< 127 Free, Boot=78, Backup=2
< <4.00>
> load user
< load user
< AOK
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> set o d ReefAngelWifi
< set o d ReefAngelWifi
< AOK
< <4.00>
> set w s The_2400_Club
< set w s The_2400_Club
< AOK
< <4.00>
> set w p nofatchicks
< set w p nofatchicks
< AOK
< <4.00>
> set w k 00000000000000000000000000
< set w k 00000000000000000000000000
< AOK
< <4.00>
> set ftp address 198.175.253.161
< set ftp address 198.175.253.161
< AOK
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> reboot
< reboot
> $$$
< CMD
> show n
< show n
< SSid=The_2400_Club
< Chan=1
< Assoc=FAIL
< Rate=12, 24Mb
< Auth=FAIL
< Mode=NONE
< DHCP=FAIL
< Boot=0
< Time=OK
< Links=0
< <4.00>
> get i
< get i
< IF=DOWN
< DHCP=ON
< IP=10.1.10.95:2000
< NM=255.255.255.0
< GW=10.1.10.1
< HOST=198.171.134.6:80
< PROTO=TCP,
< MTU=1524
< FLAGS=0x6
< TCPMODE=0x0
< BACKUP=0.0.0.0
< <4.00>
> reboot
< reboot
Removing connection to COM3
---------------------------------------------------------------------
Your Reef Angel Wifi Attachment is now configured with the settings provided.
---------------------------------------------------------------------

If the blue LED is still blinking, it means that the Reef Angel Wifi Attachment could not connect to your wifi network.

Found router IGD

Port 2000 is now being forwarded to 10.1.10.95


I fired up my old router and gave it a different SSID, here's the connection when connecting to the old router:

Opening Serial Port...
Connected to serial port COM3
> $$$
< CMD
> ls
< ls
<
< FL# SIZ FLAGS
< 2 79680 3 WiFly_GSX-2.36
< 22 -1 10 config
< 23 -1 10 user
< 34 83648 3 WiFly_GSX-2.45
< 78 86328 3 wifly-GSX-400
< 79 46632 3 wps_app-GSX-131
< 80 66240 3 eap_app-GSX-101
< 81 74920 3 web_app-GSX-106
< 82 37282 0 web_config.html
< 83 512 0 link.html
< 84 7268 0 logo.png
<
< 127 Free, Boot=78, Backup=2
< <4.00>
> load user
< load user
< AOK
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> set o d ReefAngelWifi
< set o d ReefAngelWifi
< AOK
< <4.00>
> set w s The_2400_Club_OLD
< set w s The_2400_Club_OLD
< AOK
< <4.00>
> set w p nofatchicks
< set w p nofatchicks
< AOK
< <4.00>
> set w k 00000000000000000000000000
< set w k 00000000000000000000000000
< AOK
< <4.00>
> set ftp address 198.175.253.161
< set ftp address 198.175.253.161
< AOK
< <4.00>
> save
< save
< Storing in config
< *BAD CONFIG*
< <4.00>
> reboot
< reboot
> $$$
< CMD
> show n
< show n
< SSid=The_2400_Club_OLD
< Chan=10
< Assoc=OK
< Rate=12, 24Mb
< Auth=OK
< Mode=MIXED
< DHCP=FAIL
< Boot=0
< Time=OK
< Links=1
< <4.00>
> get i
< get i
< IF=DOWN
< DHCP=ON
< IP=0.0.0.0:2000
< NM=0.0.0.0
< GW=0.0.0.0
< HOST=198.171.134.6:80
< PROTO=TCP,
< MTU=1524
< FLAGS=0x6
< TCPMODE=0x0
< BACKUP=0.0.0.0
< <4.00>
> reboot
< reboot
Removing connection to COM3
---------------------------------------------------------------------
Your Reef Angel Wifi Attachment is now configured with the settings provided.
---------------------------------------------------------------------

If the blue LED is still blinking, it means that the Reef Angel Wifi Attachment could not connect to your wifi network.

Found router IGD


The biggest difference I see is that the ASSOC=OK when using my old router, while the new router gives ASSOC=FAIL

Could there still be some settings stored in the wifi addon from setting up against the old router that are causing it to not connect to the new router?

use putty at 57600 baud
send "$$$", the module will enter command mode.
Now, send "scan"
What do you get back?

SCAN:Found 3
01,06,-79,04,1104,1c,00,7c:bf:b1:65:f0:c0,Removals
02,10,-38,04,1104,14,40,00:17:3f:c0:b5:9d,The_2400_Club_OLD
03,10,-41,04,3104,28,00,c8:d7:19:3a:6a:24,The_2400_Club

Looks like it's able to see the router.

I actually had to select type 2 and that seemed to give me an auth of WPA2 in the controller (doesn't match with the manual). After setting this even rebooting isn't assigning me a correct IP:
<4.00> save
Storing in config
*BAD CONFIG*
<4.00> reboot
*Reboot*CMD
get w
SSID=The_2400_Club
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=0
Passphrase=nofatchicks
EAP_Id=
EAP_User=
<4.00> get i
IF=DOWN
DHCP=ON
IP=10.1.10.95:2000
NM=255.255.255.0
GW=10.1.10.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0

What do you get if you send "join 3"?

I think I found the problem:
http://forum.reefangel.com/viewtopic.php?p=23931#p23931
Can you try this?
If this does work, I'll have to patch the wifi utility.

I was unable to get this to work. I reloaded the 2.36 image and then set it up again performing the join wlan 1 and resetting factory defaults:

Here's me trying to connect again via putty:

<2.36>
SCAN:Found 2
Num SSID Ch RSSI Sec MAC Address Suites
1 The_2400_Club_OLD 10 -34 WPA2PSK 00:17:3f:c0:b5:9d TKIPM-TKIP WPS 1104
2 The_2400_Club 10 -29 WPA2PSK c8:d7:19:3a:6a:24 AESM-AES 3104

when i try to join 2, then i get the following:
join 2
Auto-Assoc 2 chan=0 mode=NONE FAILED


*Reboot*CMD
get i
IF=DOWN
DHCP=ON
IP=10.1.10.95:2000
NM=255.255.255.0
GW=10.1.10.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0
<2.36> get w
SSID=The_2400_Club
Chan=10
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon=5
Passphrase=nofatchicks


I've been doing some more research into this with router incompatibility and there are some wireless adapters that will not connect to routers that do not start with a mac address beginning with 00: (I believe this to be the issue with the other devices in my house that will not connect to this new router, wondering if the wifi adapter falls into the same category). As you see from the scan above, the mac address of my new router begins with C8:, and my old router begins with 00: as expected. Is anyone successfully connecting via WPA2 to a router beginning with a mac address other than 00?

Mine is 58:*:*:*:*:*

Sorry, I gave you the wrong command...
It needs to be either
join The_2400_Club
or
join # 2

I wonder if the _ is messing with the encryption.
Try renaming to only alphanumeric SSID.

I've hit my limit with this router. I think there's something seriously wrong with it since there's a bunch of other devices I have that can't connect.

I'm going to get an ASUS RT-N66U, anyone else using this router or have the wifi addon successfully connect to it? Just looking to get something that'll work with everything in the house.

I love my ASUS RT-N66U.. I have the Reef Angel Connected to it and also a Neptune Apex and many many more devices..

After you get it working out of the box you may want to switch it over to Merlins firmware
http://www.smallnetbuilder.com/forums/f ... y.php?f=42

Before you get too frustrated, you should try Roberto's suggestion to remove the underscore from the SSID. I would also try a different authentication method. I doubt the MAC has much to do with it, but it's certainly possible, but more likely that Manufacturer has issues since the prefix is tied to the company.

Wanted to give an update with this. I don't believe it was the MAC as i originally stated, but the router's 2ghz channel being defunct. This is why i was able to connect with some devices at my house, but not others (they were connecting to the 5ghz channel). I'm guessing that the reef angel wifi doesn't support 5ghz band wireless?

Either way i sent that router back and got a new one. Connected no problem and is now set up with no issues! Thanks for all the help and advice! It was actually enjoyable.

Cool!!
Yes, the module doesn't work on 5GHz.

rimai wrote:Cool!!
Yes, the module doesn't work on 5GHz.

Could this be put on the first page of the wifi manual (any page for that matter) or on the product info page?

sorry to bring up old thread.