Author Topic: Network At Times Does Not Connect After Sleep  (Read 1720 times)

dhicks

  • Jr. Member
  • **
  • Posts: 16
    • View Profile
Network At Times Does Not Connect After Sleep
« on: September 21, 2014, 02:13:19 PM »
Group........

We are encountering a situation where machines do not reactivate the network properly after sleep.  When this occurs, it generally works to manually turn the wireless off and then back on, but at times a reboot seems to be the only fix.  We have tried to use a script to force the network awake, which seemed to improve things, but not fix completely.  Has anyone run into a similar situation?

Hardware
Acer Travelmate B113 with Intel Centrino NIC

Ubermix ver: 2.1

Script we have attempted to use in /etc/pm/sleep.d

#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
;;
*)
;;
esac
exit $?

jnetman1

  • Administrator
  • Hero Member
  • *****
  • Posts: 286
    • View Profile
Re: Network At Times Does Not Connect After Sleep
« Reply #1 on: September 27, 2014, 09:38:18 AM »
Does your wireless use hidden SSIDs?

dhicks

  • Jr. Member
  • **
  • Posts: 16
    • View Profile
Re: Network At Times Does Not Connect After Sleep
« Reply #2 on: October 20, 2014, 09:37:34 PM »
Sorry for the delay in responding.....I truly do appreciate the help.  I fear as we've dug into the situation we are finding more pain rather than less.  ....to answer the actual question.....no, we don't have any hidden SSIDs on these.

We are finding this issue to be problematic on a number of types of machine/network cards and in two different sites.  The common situation is that we are running Aruba IAPs in both places.  The networks are using WPA2, though we've also tried open networks for testing.  We have tried both Ubermix and vanilla versions of Ubuntu.  We have also tried a variety of kernels, NetworkManager versions, and wpa_supplicant versions....and even a foray into using WICD instead of NM.  Basically, it seems that connections that were solid under Ub 12.04 are less stable (at least in our situation) in anything more recent.  It also seems more problematic if there is a dense AP environment.  Watching logs on the client, it scans the network repeatedly and keeps saying that authentication timed out.  ....even with open wifi.  We've spent hours on the phone with Aruba TAC and have tried various scenarios to clean it up.  We've also spent quite a bit of time looking around for possible solutions online.  The frustrating aspect is that we don't have challenges with our Windows or OSX clients.  We've even checked out the 14.10 beta to see if perhaps that fixes things and have also forced the version 2.3 of wpasupplicant........seems a bit better, but still some failures.

For the time being, we are using UM 1.x with Cinnamon in our most problematic situation and are hoping to find a resolution so we can move these units to UM 2.x.  If anyone out there has seen something similar (and has a resolution) it would be great.

Thanks for all......sorry for the rambling reply.