Can't associate R750 to SZ5.2 when R750 has static IP address.

[hyosang_choi]

HI.

I recently heard that from partner we can't joining R750 with SZ5.2 when R750 has static IP address.

Thus I tested that, and I got same result.


Below is syslog on R750.


<---------when R750 is configured static ip address -------------->
Mar 12 01:46:36 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:46:41 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:46:46 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:46:51 RuckusAP local2.err syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255   
Mar 12 01:46:51 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:46:56 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7]  
Mar 12 01:47:16 RuckusAP daemon.err cubic[770]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and value 
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: update_ssh_public_key:781 Address [] is invalid address.[-258].  
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hub_registrar ... [stopped] (0.016)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hub_registrar: ref count 0 mon_level 2
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: sshclient ....... [failed ] (0.014)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: sshclient ....... [failed ] (0.006)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hotspot ......... [stopped] (0.006)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hotspot ......... [started] (0.006)
Mar 12 01:47:22 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:47:47 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:47:52 RuckusAP local2.err syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255   
Mar 12 01:47:52 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:47:57 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:48:52 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:48:53 RuckusAP local2.err syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255   
Mar 12 01:48:58 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:49:48 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:49:52 RuckusAP local2.err syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255   
Mar 12 01:49:53 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:50:08 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:51:01 RuckusAP local2.err syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255   
Mar 12 01:51:03 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:51:08 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].  
Mar 12 01:51:08 RuckusAP daemon.notice rsmd[189]: sshclient ....... [stopped] (0.027)



<---------when R750 is configured dynamic ip address -------------->

Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSHtunnel Public Key verify Successfully ServerIP=172.16.100.225
Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSH tunnel pararms: 172.16.100.225 128 
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: sshclient ....... [started] (3.324)
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: lldpd ........... [stopped] (0.005)
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: lldpd ........... [started] (0.054)
Mar 12 01:51:13 RuckusAP daemon.notice Firmware Daemon[689]: working|looking up control server IP
Mar 12 01:51:13 RuckusAP daemon.notice Firmware Daemon[689]: working|reading control file
Mar 12 01:51:14 RuckusAP daemon.notice Firmware Daemon[689]: working|reading firmware file header
Mar 12 01:51:22 RuckusAP authpriv.info dropbear[6623]: Child connection from 192.168.100.51:53206
Mar 12 01:51:24 RuckusAP authpriv.notice dropbear[6623]: Deferring to RKS shell to authenticate password.
Mar 12 01:51:24 RuckusAP authpriv.err dropbear[6623]: chown(/dev/ttyp0, 0, 5) failed: Read-only file system



When  R750 is configured static ip address, he don't update ssh public key by any reason.

Mar 12 01:47:16 RuckusAP daemon.err cubic[770]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and value 
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: update_ssh_public_key:781 Address [] is invalid address.[-258]. 



But When  R750 is configured dynamic ip address, he did update ssh public key well.

Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSHtunnel Public Key verify Successfully ServerIP=172.16.100.225
Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSH tunnel pararms: 172.16.100.225 128




Is there a bug report about this symptom?

[hyosang_choi]

That's too bad.
Do you think I don't check those?

[nnamjin_roh]

Diego!  You did  very stupid  comment.  You really think Mr jeronimo did not check default gateway and etc. don't you?
I faced same issue also.

[diego_garcia_de]

Sorry for the comment. Didn't mean it as a something obvious. . I had issues where the default gateway was configured but the route wasn't active in the ap. Is the IP range the same when using static or dhcp ? Smartzone uses an internal pool of ips to setup ssh tunneling between the ap and the controller. That range didn't use to be configurable and that range also couldn't be used on the APs themselves or on any other IP destination that smartzone would have to reach. On the latest versions the range is configurable. Any chance it might be using ips in the range 10.254.0.0/16 or 10.255.0.0/16?

More details here. https://forums.ruckuswireless.com/ruc...

Also, looking at the log, was the IP manually assigned ip 10.10.99.255? .. I imagine that there could be a code path on the ap checking that the IP doesn't end in 255 which would be valid as long as you're using masks in the /1-23 range. (meaning the check would be wrong).

Mar 12 01:46:51 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255

Or is it happening with any static IP?

I didn't notice your long post history jerónimo. Once again sorry of the first comment sounded wrong.

[hyosang_choi]

No problem bro.

[tim_lillis]

having same problem but with dhcp address same ap model