This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos UTM 9.510-4 released - let's share experiences!

Released yesterday:

https://community.sophos.com/products/unified-threat-management/b/utm-blog/posts/utm-up2date-9-510-released

 

Found out so far, that mailmanager is broken:

Others? :-)



This thread was automatically locked due to age.
Parents
  • I had my AP55 at home drop all connections, rebooted it to get devices connected again.  Took a look in the wireless log, and it's full of this:

    2018:07:22-01:19:32 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:32 firewall awed[4678]: Use of uninitialized value in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:32 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:32 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:32 firewall awed[4678]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:32 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:35 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:35 firewall awed[4678]: Use of uninitialized value in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:35 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:35 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:35 firewall awed[4678]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:35 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:38 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:38 firewall awed[4678]: Use of uninitialized value in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:38 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:38 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:38 firewall awed[4678]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:38 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:41 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:41 firewall awed[4678]: Use of uninitialized value in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:41 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:41 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:41 firewall awed[4678]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:41 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:44 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:44 firewall awed[4678]: Use of uninitialized value in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:44 firewall awed[4678]: 1 main::updateActiveAweLocalChannels
    2018:07:22-01:19:44 firewall awed[4678]: WARN -------------------------------------------------------
    2018:07:22-01:19:44 firewall awed[4678]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:22-01:19:44 firewall awed[4678]: 1 main::updateActiveAweLocalChannels

  • does the ap55 still work?

  • AP55 is working after reboot.

    Here's something strange.  I modified /etc/hostapd/hostapd.conf-default to get the internal WiFi NIC working in case the AP55 wasn't going to by changing:

    #ht_capab=[<HT_CAPAB>]
    ht_capab=[HT40+][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]
     
    After reboot, I'm not seeing the flood of messages anymore.
Reply
  • AP55 is working after reboot.

    Here's something strange.  I modified /etc/hostapd/hostapd.conf-default to get the internal WiFi NIC working in case the AP55 wasn't going to by changing:

    #ht_capab=[<HT_CAPAB>]
    ht_capab=[HT40+][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]
     
    After reboot, I'm not seeing the flood of messages anymore.
Children
  • I removed the internal wifi (LocalWifi0) from the SSID, and the log flood returned, this time a little different:

    2018:07:23-17:01:02 crawl awed[4729]: WARN -------------------------------------------------------
    2018:07:23-17:01:02 crawl awed[4729]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:23-17:01:02 crawl awed[4729]: 1 main::updateActiveAweLocalChannels
    2018:07:23-17:01:02 crawl awed[4729]: WARN -------------------------------------------------------
    2018:07:23-17:01:02 crawl awed[4729]: Use of uninitialized value $phyNumber in string eq at awed_ng.pl line 2526.
    2018:07:23-17:01:02 crawl awed[4729]: 1 main::updateActiveAweLocalChannels
    2018:07:23-17:01:05 crawl awed[4729]: WARN -------------------------------------------------------
    2018:07:23-17:01:05 crawl awed[4729]: Use of uninitialized value $local_ActiveChannel in string ne at awed_ng.pl line 2515.
    2018:07:23-17:01:05 crawl awed[4729]: 1 main::updateActiveAweLocalChannels
    2018:07:23-17:01:05 crawl awed[4729]: WARN -------------------------------------------------------
    2018:07:23-17:01:05 crawl awed[4729]: Use of uninitialized value $phyNumber in string eq at awed_ng.pl line 2526.
    2018:07:23-17:01:05 crawl awed[4729]: 1 main::updateActiveAweLocalChannels
  • If you clear cache in IE it works fines. Assume the same for edge.

  • I refreshed the website several times (F5) and then it worked without resetting the web browser.