Guest User!

You are not Sophos Staff.

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

WLAN Problem mit RED 15w

Hallo zusammen,

ich habe hier ein kleines Problem mit einer RED 15w. Hier wird immer wieder der AP der RED in den Status inaktiv versetzt.
Wenn ich dann den AP lösche und die RED neu starte geht der AP wieder.

Das Problem tritt erst seit dem Update auf 9.6x auf. Akuteller Firmware Stand 9.603-1 die UTM ist eine SG105 r1
So weit ich sehen kann tritt der Fehler auch nur auf wenn die UTM ihre Internet Verbindung verliert. So z.B. gesten um 17:00 Uhr

Was mir aufgefallen ist dass, zumindes dem Log nach das RED eine andere Uhrzeit als die UTM hat.

Hatt von euch jemand schon mal so ein Problem?

Grüße Thomas

Hier der Ausschnitt aus dem Wireless Log.
_____________________________________________________________________________________________________________________ 2019:07:21-14:54:23 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19119 2019:07:21-14:54:24 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19119 2019:07:21-14:54:39 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19120 2019:07:21-14:54:40 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19120 2019:07:21-16:54:09 gse awed[4081]: [MASTER] start processing configuration change 2019:07:21-16:54:10 gse awed[4081]: [MASTER] end processing configuration change 2019:07:21-14:54:56 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19121 2019:07:21-14:54:57 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19121 2019:07:21-14:55:12 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19122 2019:07:21-14:55:13 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19122 2019:07:21-14:55:27 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19123 2019:07:21-14:55:28 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19123 2019:07:21-14:55:43 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19124 2019:07:21-14:55:44 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19124 2019:07:21-14:56:00 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19125 2019:07:21-14:56:01 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19125 2019:07:21-14:56:15 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19126 2019:07:21-14:56:16 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19126 2019:07:21-14:56:31 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19127 2019:07:21-14:56:32 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19127 2019:07:21-14:56:48 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19128 2019:07:21-14:56:49 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19128 2019:07:21-14:57:04 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19129 2019:07:21-14:57:05 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19129 2019:07:21-14:57:19 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19130 2019:07:21-14:57:20 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19130 2019:07:21-14:57:35 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19131 2019:07:21-14:57:37 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19131 2019:07:21-14:57:52 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19132 2019:07:21-14:57:53 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19132 2019:07:21-14:58:07 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19133 2019:07:21-14:58:08 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19133 2019:07:21-14:58:23 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19134 2019:07:21-14:58:24 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19134 2019:07:21-14:58:40 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:622 Sending TCP keepalive frame 19135 2019:07:21-14:58:41 RED15 lua syslog: [/usr/lib/lua/redd/utm.lua]:661 Receiving TCP keepalive frame 19135 2019:07:21-16:59:21 gse awed[10698]: [A36017FA7A85102] ll_read: dead socket: Resource temporarily unavailable 2019:07:21-16:59:21 gse awed[10698]: [A36017FA7A85102] disconnected. Close socket and kill process. 2019:07:21-17:55:40 gse awed[4081]: [MASTER] start processing configuration change 2019:07:21-17:55:41 gse awed[4081]: [MASTER] end processing configuration change 2019:07:21-18:23:40 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57278 2019:07:21-18:23:40 gse awed[27892]: [A36017FA7A85102] RED15w from 192.168.52.253:57278 identified as A36017FA7A85102 2019:07:21-18:23:40 gse awed[27892]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:40 gse awed[27892]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it. 2019:07:21-18:23:41 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57280 2019:07:21-18:23:41 gse awed[27895]: [A36017FA7A85102] RED15w from 192.168.52.253:57280 identified as A36017FA7A85102 2019:07:21-18:23:41 gse awed[27895]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:41 gse awed[27895]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it. 2019:07:21-18:23:41 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57282 2019:07:21-18:23:41 gse awed[27897]: [A36017FA7A85102] RED15w from 192.168.52.253:57282 identified as A36017FA7A85102 2019:07:21-18:23:41 gse awed[27897]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:41 gse awed[27897]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it. 2019:07:21-18:23:41 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57284 2019:07:21-18:23:41 gse awed[27899]: [A36017FA7A85102] RED15w from 192.168.52.253:57284 identified as A36017FA7A85102 2019:07:21-18:23:41 gse awed[27899]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:41 gse awed[27899]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it. 2019:07:21-18:23:41 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57286 2019:07:21-18:23:41 gse awed[27902]: [A36017FA7A85102] RED15w from 192.168.52.253:57286 identified as A36017FA7A85102 2019:07:21-18:23:41 gse awed[27902]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:41 gse awed[27902]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it. 2019:07:21-18:23:41 gse awed[4081]: [MASTER] new connection from 192.168.52.253:57288 2019:07:21-18:23:41 gse awed[27907]: [A36017FA7A85102] RED15w from 192.168.52.253:57288 identified as A36017FA7A85102 2019:07:21-18:23:41 gse awed[27907]: [A36017FA7A85102] (Re-)loaded identity and/or configuration 2019:07:21-18:23:42 gse awed[27907]: [A36017FA7A85102] Corrupt payload. Device may have wrong key. MD5 of the key is 750fb41827ae1443177475723c5032fa. Delete device to re-register it.



This thread was automatically locked due to age.
Parents Reply Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?