Wyse devices pulling default Gateway as IP address?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #105248
    Avatardstabb
    Participant
    • Total Post: 4
    • Newbie

    This has been happening randomly over the past few weeks,

    I was working on a couple of laptops and suddenly the wifi lost internet connectivity. I logged into the wireless controller to see if this was the same issue we’ve been having where one of these Wyse thin clients grabbed the same IP address as the gateway and sure enough that was the issue.

    For some reason, this device simply grabbed 10.41.20.1 as it’s IP address. That address is the address of the wifi network gateway. This causes everything on the campus wireless Data network to stop communicating.

    I disassociated the device in the controller and then immediately another device next to it grabbed the same IP address (10.41.20.1). I disassociated that device and everything went back to working correctly.

    I’m not sure why this is happening. The gateway’s address should never be one that DHCP is handing out so it makes no sense.

    And just now, as I went to verify that things were back up to normal, sure enough the first device has the gateway address AGAIN! I disassociated it again and it then grabbed a normal IP. When I VNC into the device, I see that as the IP and the DHCP lease has 23 hours and 58 minutes left. It should have received a new DHCP lease at 3:00 when I disassociated it the first time. Why on earth would it even be trying to grab another IP address before its lease is up. This has happened on several platforms (3040, 5212, and 5470 AIO) on at least three different firmware. Most recently happening on devices with 8.6 MR9. Anyways, I highly doubt it is the Wyse clients causing this issue but its seemingly only happening to them, except I saw one cell phone grab the gateway.

     

    Ironically this all started as we upgraded our wireless controllers, but try telling the switch guy its his new Extreme controllers lol! Taking a look at the syslog of one of the devices, it never seems to grab the Gateway as the IP but it looks as if it is losing connection or something but the gateway is still active… Anyone ever have this issue before???

    #105270
    ConfGenConfGen
    Keymaster
    • Total Post: 11270
    • Jedi Master
    • ★★★★★★★

    I have never faced or heard about a similar issue. Therefore, I highly doubt that the Thin Client or ThinOS are the reason.
    Regarding your question about why ThinOS is renewing the IP address although the lease hasn’t expired.
    This is the standard process. Each device will try to renew the address after half of the lease time. If this fails, it will try again after half of the remaining time, and so on until the lease time is expired.

    CG

    #105318
    Avatargauteg
    Participant
    • Total Post: 1
    • Newbie

    It sounds like the WiFi gateway’s IP is part of a DHCP pool.

    What IP-range are you using for DHCP? Subnet mask? What is your LAN’s default gateway? What does the logs on the DHCP server say about leasing out ? Verify which DHCP-server the device that gets the IP has leased from (There may be a unknown device acting as DHCP-server)

    #105320
    Avatardstabb
    Participant
    • Total Post: 4
    • Newbie

    This has been happening randomly on both of our campus’, for this example I will refer to our main campus that uses 10.202.254.1 as the gateway/router IP. Here is an example snippet of a device log during when the issue occured:

    11:30:35.227 WLAN: deauthenticated by AP[489bd5:fcda34], reason 7.
    11:30:36.063 WLAN: link broken detected
    11:30:36.063 WLAN: Enable wireless
    11:30:36.063 WLAN: link broken detected
    11:30:36.063 WLAN: scanning and associating (SGHS Data2) …
    11:30:38.823 WLAN: AP candidate [d88466:d57280] (dBm=-69, ch=165)
    11:30:38.823 WLAN: AP candidate [489bd5:fcdbf4] (dBm=-56, ch=165)
    11:30:38.823 WLAN: AP candidate [489bd5:fcda24] (dBm=-41, ch=6)
    11:30:38.823 WLAN: AP candidate [489bd5:fcda34] (dBm=-22, ch=153)
    11:30:38.823 WLAN: AP [489bd5:fcda34] (dBm=-22, ch=153) selected!
    11:30:38.846 WLAN: success to associated. (17733406)
    11:30:38.846 WLAN: associated to [489bd5:fcda34] – 11ac, 5G, 20Mhz
    11:30:38.846 EAP: authenticating …
    11:30:41.791 WLAN:Next_beacon [177335] not found, time_now=[177337]
    11:30:41.791 WLAN: beacon lost
    11:30:45.342 WLAN: weak signal detected
    11:30:45.342 EAP: authenticate fail
    11:30:45.342 STA: AP[489bd5:fcda34] added to block list.
    11:30:45.342 WLAN: scanning and associating (SGHS Data2) …
    11:30:45.342 WLAN: AP [489bd5:fcda24] (dBm=-36, ch=6) selected!
    11:30:45.365 WLAN: success to associated. (17734058)
    11:30:45.365 WLAN: associated to [489bd5:fcda24] – 11n, 2.4G, 20Mh
    11:30:45.365 EAP: authenticating …
    11:30:45.646 EAP: authenticate success
    11:30:45.646 WLAN: roamed to AP[489bd5:fcda24]
    11:30:45.646 WLAN: Looking up IP address from DHCP …
    11:30:58.729 WLAN: deauthenticated by AP[489bd5:fcda24], reason 7.
    11:30:59.646 WLAN: link broken detected
    11:30:59.646 WLAN: Enable wireless
    11:30:59.646 WLAN: link broken detected
    11:30:59.646 WLAN: scanning and associating (SGHS Data2) …
    11:31:02.226 WLAN: AP candidate [489bd5:fcda24] (dBm=-42, ch=6)
    11:31:02.226 WLAN: AP candidate [d88466:d57280] (dBm=-69, ch=165)
    11:31:02.226 WLAN: AP candidate [489bd5:fcda34] (dBm=-22, ch=153)
    11:31:02.226 WLAN: AP candidate [489bd5:fcdbf4] (dBm=-56, ch=165)
    11:31:02.226 WLAN: AP [489bd5:fcda34] (dBm=-22, ch=153) selected!
    11:31:02.249 WLAN: success to associated. (17735746)
    11:31:02.249 WLAN: associated to [489bd5:fcda34] – 11ac, 5G, 20Mhz
    11:31:02.249 EAP: authenticating …
    11:31:02.260 EAP: authenticate success
    11:31:02.260 WLAN: roamed to AP[489bd5:fcda34]
    11:31:02.260 WLAN: Looking up IP address from DHCP …
    11:31:03.811 ICA[Cerner-Prod]: Click icon for menu warn timer 0
    11:31:08.821 Obtain IP[10.202.60.162] from DHCP server[10.100.100.2]
    11:31:08.821 DHCP lease time: 8 day 00:00:00
    11:31:08.831 WLAN: set default gateway 10.202.254.1
    11:31:08.831 Set Name Servers: DNS DOMAIN=[sghs.org]
    11:31:08.831 Set Name Servers: DNS=[10.100.100.2; 10.100.100.3; 10.100.100.1]
    11:31:08.831 WMS agent process is closed!
    11:31:08.832 Contacting WMS Server …
    11:31:12.698 WMS agent is retrieving full configurations.
    11:31:12.987 WMS agent: finds cached file(wnos.ini)!
    11:31:12.988 WMS agent is retrieving assigned certificate DigiCertGlobalRoot.cer …
    11:31:12.988 WMS agent is retrieving assigned certificate DigiCertSHA2SecureServerCA.cer …
    11:31:12.988 WMS agent is retrieving assigned certificate SGHSWildcard2016.cer …
    11:31:13.181 WMS agent received configurations
    11:31:13.182 WMS agent checked in …
    11:31:13.186 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:31:18.033 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:31:18.033 Certificate ‘DigiCertSHA2SecureServerCA.cer’ installed!
    11:31:18.033 Certificate ‘SGHSWildcard2016.cer’ installed!
    11:31:18.043 WLAN: roaming point dbm[-70].
    11:31:18.289 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:31:21.144 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:31:24.275 ftp:/wnos/cacerts/DigiCertSHA2SecureServerCA.cer: file not exists.
    11:31:27.384 ftp:/wnos/cacerts/SGHSWildcard2016.cer: file not exists.
    11:31:30.513 Fail to validate file server
    11:31:31.003 Received Full configuration from WMS.
    11:31:48.423 WLAN: deauthenticated by AP[489bd5:fcda34], reason 7.
    11:31:48.745 WLAN: link broken detected
    11:31:48.745 WLAN: Enable wireless
    11:31:48.745 WLAN: link broken detected
    11:31:48.745 WLAN: scanning and associating (SGHS Data2) …
    11:31:51.325 WLAN: AP candidate [489bd5:fcda24] (dBm=-36, ch=6)
    11:31:51.325 WLAN: AP candidate [d88466:d57280] (dBm=-68, ch=165)
    11:31:51.325 WLAN: AP candidate [489bd5:fcda34] (dBm=-28, ch=153)
    11:31:51.325 WLAN: AP candidate [489bd5:fcdbf4] (dBm=-49, ch=165)
    11:31:51.325 WLAN: AP [489bd5:fcda34] (dBm=-28, ch=153) selected!
    11:31:51.348 WLAN: success to associated. (17740608)
    11:31:51.348 WLAN: associated to [489bd5:fcda34] – 11ac, 5G, 20Mhz
    11:31:51.348 EAP: authenticating …
    11:31:54.267 WLAN:Next_beacon [177407] not found, time_now=[177409]
    11:31:54.267 WLAN: beacon lost
    11:31:57.710 WLAN: weak signal detected
    11:31:57.710 EAP: authenticate fail
    11:31:57.710 STA: AP[489bd5:fcda34] added to block list.
    11:31:57.710 WLAN: scanning and associating (SGHS Data2) …
    11:31:57.710 WLAN: AP [489bd5:fc78d4] (dBm=-56, ch=44) selected!
    11:31:57.734 WLAN: success to associated. (17741246)
    11:31:57.734 WLAN: associated to [489bd5:fc78d4] – 11ac, 5G, 20Mhz
    11:31:57.734 EAP: authenticating …
    11:32:00.276 WLAN:Next_beacon [177413] not found, time_now=[177415]
    11:32:00.276 WLAN: beacon lost
    11:32:01.456 WLAN: deauthenticated by AP[489bd5:fc78d4], reason 7.
    11:32:03.776 WLAN: weak signal detected
    11:32:03.787 EAP: authenticate fail
    11:32:03.787 STA: AP[489bd5:fc78d4] added to block list.
    11:32:04.787 WLAN: Switch WLAN profile
    11:32:04.787 WLAN: scanning and associating (SGHS Data2) …
    11:32:07.287 WLAN: AP candidate [d88466:d57280] (dBm=-68, ch=165)
    11:32:07.287 WLAN: AP candidate [489bd5:fc78d4] (dBm=-56, ch=44)
    11:32:07.287 WLAN: AP candidate [489bd5:fcda34] (dBm=-21, ch=153)
    11:32:07.287 WLAN: AP candidate [489bd5:fcda24] (dBm=-41, ch=6)
    11:32:07.287 WLAN: AP [489bd5:fcda34] (dBm=-21, ch=153) selected!
    11:32:07.310 WLAN: success to associated. (17742204)
    11:32:07.310 WLAN: associated to [489bd5:fcda34] – 11ac, 5G, 20Mhz
    11:32:07.310 EAP: authenticating …
    11:32:07.321 EAP: authenticate success
    11:32:07.321 WLAN: Looking up IP address from DHCP …
    11:32:09.360 ICA[Cerner-Prod]: Click icon for menu warn timer 0
    11:32:11.592 Obtain IP[10.202.60.162] from DHCP server[10.100.100.2]
    11:32:11.592 DHCP lease time: 8 day 00:00:00
    11:32:11.602 WLAN: set default gateway 10.202.254.1
    11:32:11.602 WMS agent process is closed!
    11:32:11.602 Contacting WMS Server …
    11:32:11.768 WMS agent is retrieving full configurations.
    11:32:12.022 WMS agent: finds cached file(wnos.ini)!
    11:32:12.024 WMS agent is retrieving assigned certificate DigiCertGlobalRoot.cer …
    11:32:12.024 WMS agent is retrieving assigned certificate DigiCertSHA2SecureServerCA.cer …
    11:32:12.024 WMS agent is retrieving assigned certificate SGHSWildcard2016.cer …
    11:32:12.211 WMS agent received configurations
    11:32:12.213 WMS agent checked in …
    11:32:12.216 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:32:15.326 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:32:15.326 Certificate ‘DigiCertSHA2SecureServerCA.cer’ installed!
    11:32:15.326 Certificate ‘SGHSWildcard2016.cer’ installed!
    11:32:15.336 WLAN: roaming point dbm[-70].
    11:32:15.571 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:32:17.331 WLAN: set default gateway 10.202.254.1
    11:32:18.437 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:32:18.437 ftp:/wnos/cacerts/DigiCertSHA2SecureServerCA.cer: file not exists.
    11:32:18.437 ftp:/wnos/cacerts/SGHSWildcard2016.cer: file not exists.
    11:32:18.438 Fail to validate file server
    11:32:18.003 Received Full configuration from WMS.
    11:32:34.353 ICA[Cerner-Prod]: Click icon for menu warn timer 0
    11:33:56.774 Failed to connect to MQTT server wmsserver.sghs.org:1883, errno:101
    11:35:13.865 WLAN: deauthenticated by AP[489bd5:fcda34], reason 1.
    11:35:14.882 WLAN: link broken detected
    11:35:14.882 WLAN: Enable wireless
    11:35:14.882 WLAN: link broken detected
    11:35:14.882 WLAN: scanning and associating (SGHS Data2) …
    11:35:17.363 WLAN: AP candidate [489bd5:fcda24] (dBm=-35, ch=6)
    11:35:17.363 WLAN: AP candidate [489bd5:fcda34] (dBm=-28, ch=153)
    11:35:17.363 WLAN: AP candidate [d88466:d57280] (dBm=-66, ch=165)
    11:35:17.363 WLAN: AP candidate [489bd5:fcdbf4] (dBm=-51, ch=165)
    11:35:17.363 WLAN: AP [489bd5:fcda34] (dBm=-28, ch=153) selected!
    11:35:17.386 WLAN: success to associated. (17761255)
    11:35:17.386 WLAN: associated to [489bd5:fcda34] – 11ac, 5G, 20Mhz
    11:35:17.386 EAP: authenticating …
    11:35:17.397 EAP: authenticate success
    11:35:17.397 WLAN: Looking up IP address from DHCP …
    11:35:21.980 Obtain IP[10.202.60.162] from DHCP server[10.100.100.2]
    11:35:21.980 DHCP lease time: 8 day 00:00:00
    11:35:21.990 WLAN: set default gateway 10.202.254.1
    11:35:21.990 WMS agent process is closed!
    11:35:21.990 Contacting WMS Server …
    11:35:22.165 WMS agent is retrieving full configurations.
    11:35:22.429 WMS agent: finds cached file(wnos.ini)!
    11:35:22.431 WMS agent is retrieving assigned certificate DigiCertGlobalRoot.cer …
    11:35:22.431 WMS agent is retrieving assigned certificate DigiCertSHA2SecureServerCA.cer …
    11:35:22.431 WMS agent is retrieving assigned certificate SGHSWildcard2016.cer …
    11:35:22.610 WMS agent received configurations
    11:35:22.611 WMS agent checked in …
    11:35:22.615 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:35:25.689 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:35:25.689 Certificate ‘DigiCertSHA2SecureServerCA.cer’ installed!
    11:35:25.689 Certificate ‘SGHSWildcard2016.cer’ installed!
    11:35:25.699 WLAN: roaming point dbm[-70].
    11:35:25.936 The existed certificate ‘DigiCertGlobalRootCA.cer’ has the same content as the imported certificate ‘DigiCertGlobalRoot.cer’
    11:35:29.060 ftp:/wnos/cacerts/DigiCertGlobalRoot.cer: file not exists.
    11:35:32.171 ftp:/wnos/cacerts/DigiCertSHA2SecureServerCA.cer: file not exists.
    11:35:35.300 ftp:/wnos/cacerts/SGHSWildcard2016.cer: file not exists.
    11:35:38.421 Fail to validate file server
    11:35:39.003 Received Full configuration from WMS.

     

    #105321
    Avatardstabb
    Participant
    • Total Post: 4
    • Newbie

    DHCP config

     

    heres a pic of the DHCP config that these devices on the main campus are talking to.

    As you can see the range doesn’t include the gateway address, and according to device logs and DHCP logs, the gateway isn’t handed out. This all started when we upgraded our wireless controllers, what concerns me is it only seems to have affected Thin Clients aside from the one Cell Phone that was affected once.

    To me it seems like the clients are getting kicked off the Access Point and losing their IP but are retaining the default gateway or something. I have no idea really. It has happened to multiple platforms 3040, 5212, 5470, and several different firmware’s all the way from 8.6_027 all the way up to 8.6 MR9 which all devices have currently been upgraded to.

    #105322
    Avatardstabb
    Participant
    • Total Post: 4
    • Newbie

    Since all this has happened, we have moved to wire most of the clients we can, we are down to about 30 unavoidable Wifi connected, and we have moved those over to their own SSID so that they do not bring down our entire data network that consists of about a thousand devices out side of Wyse.

    In this new SSID, I have reserved the address in DHCP for the clients and am still having this issue. It happens maybe once a day, all the way up to 5 times, sometimes one device, sometimes up to 2 or 3 will be affected at once each time.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.