NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Same Model System, Different Behavior??
I had recently posted on here that although my Orbi system was running well, the Orbi app would not list devices under the "Network Map" option. I have tried all sorts of things to get this to work ...
SOLVED ISSUE Of Network Map Not Rendering Properly and Showing Devices By Connection On Android!!!!!!!
BLUF: My original local SSID was "Daily Planet" The Space in the SSID was preventing the "CONNECTION TYPE" and "CONNECTED ORBI" fields from being reported to the Orbi App! (My neighbors SSID is only 4 characters long with no spaces so theirs worked properly)
This only affected Android devices running the Orbi App... Not Apple Devices
Process I took per FURRYe38 recommendation:
- Disconnected satellites (2 of them)
- Hard reset Router
- Rebooted & initial set up
- Tested (It didnt work since I used my original SSID "Daily Planet")
- Reverted to an Earlier Firmware version thinking that may help -- rebooted and set up but used the default SSID (ORBI38)
- Noticed all was working properly!
- Changed SSID to "Daily Planet"
- Noticed it DIDNT WORK again with an SSID with a space in it
- Changed SSID to "Daily_Planet"
- Noticed it was working properly!
- Updated Firmware to current version
- Verified it is still working properly on all android devices.
- Turned back on Satellites
- Updated Settings for Reserved IPs etc and reattached wireless devices with new SSID
- Poured myself a cocktail and am a happy man!
Orbi and the Orbi APP CANNOT HANDLE SSID's with spaces in them. They will not render the network map properly if so.
To resolve: Take out the spaces -- replace with underline and it should work properly!!!!!!
A couple of heroes out there who deserve recognition for helping & discussing this
Pass the word. If you have spaces in your SSID, Android phones will not render the Attached devices properly under the DEVICE LIST nor the NETWORK MAP!
Chances are, someone ought to report this to the Orbi App Folks and this solution should be pinned at top for reference
No QoS enabled in Orbi. The word they use is "yet". Been "yet" forever. And the speedtest is just embedded Ookla. That is really sad.
SOLVED ISSUE Of Network Map Not Rendering Properly and Showing Devices By Connection On Android!!!!!!!
BLUF: My original local SSID was "Daily Planet" The Space in the SSID was preventing the "CONNECTION TYPE" and "CONNECTED ORBI" fields from being reported to the Orbi App! (My neighbors SSID is only 4 characters long with no spaces so theirs worked properly)
This only affected Android devices running the Orbi App... Not Apple Devices
Process I took per FURRYe38 recommendation:
- Disconnected satellites (2 of them)
- Hard reset Router
- Rebooted & initial set up
- Tested (It didnt work since I used my original SSID "Daily Planet")
- Reverted to an Earlier Firmware version thinking that may help -- rebooted and set up but used the default SSID (ORBI38)
- Noticed all was working properly!
- Changed SSID to "Daily Planet"
- Noticed it DIDNT WORK again with an SSID with a space in it
- Changed SSID to "Daily_Planet"
- Noticed it was working properly!
- Updated Firmware to current version
- Verified it is still working properly on all android devices.
- Turned back on Satellites
- Updated Settings for Reserved IPs etc and reattached wireless devices with new SSID
- Poured myself a cocktail and am a happy man!
Orbi and the Orbi APP CANNOT HANDLE SSID's with spaces in them. They will not render the network map properly if so.
To resolve: Take out the spaces -- replace with underline and it should work properly!!!!!!
A couple of heroes out there who deserve recognition for helping & discussing this
Pass the word. If you have spaces in your SSID, Android phones will not render the Attached devices properly under the DEVICE LIST nor the NETWORK MAP!
Chances are, someone ought to report this to the Orbi App Folks and this solution should be pinned at top for reference
Kewl, great find. Something that NG should look into with this space in between the SSID names. Shouldn't matter.
Glad it's working now. Mark your post solved so others will know.
- Well done Chuck_M, this is an excellent finding.
- Have you also tested the remote management configuration above?
- Regarding QoS, I see that Orbi has some defined priorities, which makes me think that NG will add configuration possibilities soon:
qos_list1=IP_Phone 0 IP_Phone 0 TCP 6670 6670 ---- ----
qos_list2=IP_Phone 0 IP_Phone 0 UDP 6670 6670 ---- ----
qos_list3=Skype 0 Skype 0 TCP 80,443 80,443 ---- ----
qos_list4=0
qos_list5=Netgear_EVA 0 Netgear_EVA 0 UDP 49152 49155 ---- ----
qos_list6=0
qos_list7=Vonage_IP_Phone 0 Vonage_IP_Phone 0 UDP 53,69,5060 53,69,5061 ---- ----
qos_list8=0
qos_list9=Google_Talk 0 Google_Talk 0 TCP 443 443 ---- ----
qos_list10=0
qos_list11=MSN_messenger 0 MSN_messenger 1 TCP 1863,1503,6891,6901 1863,1503,6900,6901 ---- ----
qos_list12=MSN_messenger 0 MSN_messenger 1 UDP 1503,2001,6801,6901 1503,2120,6801,6901 ---- ----
qos_list13=Yahoo_messenger 0 Yahoo_messenger 1 TCP 5050,5000,5100 5050,5010,5100 ---- ----
qos_list14=Yahoo_messenger 0 Yahoo_messenger 1 UDP 5000,5100 5010,5100 ---- ----
qos_list15=Netmeeting 0 Netmeeting 1 TCP 389,522,1503,1720,1731 389,522,1503,1720,1731 ---- ----
qos_list16=0
qos_list17=AIM 0 AIM 1 TCP 5190 5190 ---- ----
qos_list18=AIM 0 AIM 1 UDP 5190 5190 ---- ----
qos_list19=SlingStream 0 SlingStream 1 UDP 554 554 ---- ----
qos_list20=0
qos_list21=SSH 0 SSH 1 TCP 22 22 ---- ----
qos_list22=0
qos_list23=Telnet 0 Telnet 1 TCP 23 23 ---- ----
qos_list24=0
qos_list25=VPN 0 VPN 1 UDP 1701 1701 ---- ----
qos_list26=0
qos_list27=On_line_Game 0 On_line_Game 1 TCP 0 0 ---- ----
qos_list28=On_line_Game 0 On_line_Game 1 UDP 0 0 ---- ----
qos_list29=FTP 0 FTP 2 TCP 20,21 20,21 ---- ----
qos_list30=0
qos_list31=SMTP 0 SMTP 2 TCP 25 25 ---- ----
qos_list32=0
qos_list33=PPlive 0 PPlive 2 UDP 7100,7101,8000 7100,7101,8000 ---- ----
qos_list34=0
qos_list35=WWW 0 WWW 2 TCP 80 80 ---- ----
qos_list36=0
qos_list37=DNS 0 DNS 2 UDP 53 53 ---- ----
qos_list38=0
qos_list39=ICMP 0 ICMP 2 TCP 0 0 ---- ----
qos_list40=ICMP 0 ICMP 2 UDP 0 0 ---- ----
qos_list41=eMule 0 eMule 3 TCP 4242 4242 ---- ----
qos_list42=0
qos_list43=Kazaa 0 Kazaa 3 TCP 1214 1214 ---- ----
qos_list44=0
qos_list45=Gnutella 0 Gnutella 3 TCP 80,6346,6347 80,6346,6347 ---- ----
qos_list46=Gnutella 0 Gnutella 3 UDP 3646,6347 3646,6347 ---- ----
qos_list47=bt_azureus 0 bt_azureus 3 TCP 6881 6881 ---- ----
qos_list48=0
qos_list49=Counter-Strike 1 Counter-Strike 1 UDP 27015 27019 ---- ----
qos_list50=0
qos_list51=Age-of-Empires 1 Age-of-Empires 1 TCP 23978 23978 ---- ----
qos_list52=Age-of-Empires 1 Age-of-Empires 1 UDP 23978 23978 ---- ----
qos_list53=Everquest 1 Everquest 1 TCP 7000 7000 ---- ----
qos_list54=0
qos_list55=Quake-2 1 Quake-2 1 TCP 27960 27960 ---- ----
qos_list56=Quake-2 1 Quake-2 1 UDP 27960 27960 ---- ----
qos_list57=Quake-3 1 Quake-3 1 TCP 27960 27960 ---- ----
qos_list58=Quake-3 1 Quake-3 1 UDP 27960 27960 ---- ----
qos_list59=Unreal-Tourment 1 Unreal-Tourment 1 TCP 7777,27960 7783,27960 ---- ----
qos_list60=Unreal-Tourment 1 Unreal-Tourment 1 UDP 7777,27960 7783,27960 ---- ----
qos_list61=Warcraft 1 Warcraft 1 TCP 6112 6112 ---- ----
qos_list62=0
