Reflexion will be End-of-life on March 31,2023. See Sophos Reflexion EoL FAQs to learn more.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 8 subscribers
  • Views 1905 views
  • Users 0 members are here
Options
Suggested
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

Access Point: Sophos AP120 - disconnect / red led

danish123

Sophos SG125


Access Point: Sophos AP120
The status LED switches from solid green to solid red and after 1-2 Minuten back to solid green. The Wireless Protection Live Log is the following:

2022:12:09-10:13:16 XXXXXXX logread[1444]: Logread connected to 192.168.2.2:415
2022:12:09-10:13:23 remote awed[1697]: [XXXXXXX] ll_read: short read or connection error: Connection reset by peer
2022:12:09-10:13:23 remote awed[1697]: [XXXXXX] disconnected. Close socket and kill process.
2022:12:09-10:13:25 remote awed[5273]: [MASTER] new connection from 192.168.2.50:43361
2022:12:09-10:13:25 XXXXXXX aweclient[1156]: Setting led mode to normal_operation
2022:12:09-10:13:26 remote awed[4801]: [XXXXXXX] APX120 from 192.168.2.50:43361 identified as XXXXXXX
2022:12:09-10:13:26 remote awed[4801]: [XXXXXXX] (Re-)loaded identity and/or configuration
2022:12:09-10:13:25 XXXXXXX pdog[691]: src/process.c:317/unregister_process: process with name cloudclient is not registered before
2022:12:09-10:13:25 XXXXXXX aweclient[1156]: Unable to unsubscribe cloudclient from pdog
2022:12:09-10:13:25 XXXXXXX aweclient[1156]: Cloudclient not found on ubus.
2022:12:09-10:13:25 XXXXXXX aweclient[1156]: Setting led mode to normal_operation
2022:12:09-10:13:40 XXXXXXX aweclient[1156]: aweclient.c (2080) No reply get from last message, close socket.
2022:12:09-10:13:41 remote awed[5273]: [MASTER] new connection from 192.168.2.50:43362
2022:12:09-10:13:40 XXXXXXX aweclient[1156]: Setting led mode to normal_operation
2022:12:09-10:13:41 remote awed[4801]: [XXXXXXX] ll_read: short read or connection error:
2022:12:09-10:13:41 remote awed[4801]: [XXXXXXX] disconnected. Close socket and kill process.
2022:12:09-10:13:41 remote awed[4816]: [XXXXXXX] APX120 from 192.168.2.50:43362 identified as XXXXXXX
2022:12:09-10:13:41 remote awed[4816]: [XXXXXXX] (Re-)loaded identity and/or configuration
2022:12:09-10:13:40 XXXXXXX aweclient[1156]: aweclient.c (2065) Reconfiguration required. need_reconf = 1
2022:12:09-10:13:40 XXXXXXX aweclient[1156]: aweclient.c (2581) Exit from main loop with no error. Get new configuration.
2022:12:09-10:13:41 XXXXXXX pdog[691]: src/process.c:317/unregister_process: process with name cloudclient is not registered before
2022:12:09-10:13:41 XXXXXXX aweclient[1156]: Unable to unsubscribe cloudclient from pdog
2022:12:09-10:13:41 XXXXXXX aweclient[1156]: Cloudclient not found on ubus.
2022:12:09-10:13:41 XXXXXXX aweclient[1156]: Setting led mode to normal_operation
2022:12:09-10:14:38 XXXXXXX kernel: [ 7089.733829]

Does somone of you have any ideas?



This thread was automatically locked due to age.
Parents
  • 0

    Hi,
    this APX120 is mostly bricked, if you open the case, you can find an RS232 header and can connect a USB to RS232.

    With this you "might" be able to debrick the APX120.

    It´s a bit tricky to catch the hardware clitch and enable uBoot cli at hardware level, but sometimes you can be lucky and the bootdelay is > 0

    But you will loose all required uBoot settings and need to set them manually.
    Then you might be able to load the current firmware with tftpboot and flash the image back.

    I just desoldered the uBoot and changed the bootdelay with hexed...

    Jürgen

Reply
  • 0

    Hi,
    this APX120 is mostly bricked, if you open the case, you can find an RS232 header and can connect a USB to RS232.

    With this you "might" be able to debrick the APX120.

    It´s a bit tricky to catch the hardware clitch and enable uBoot cli at hardware level, but sometimes you can be lucky and the bootdelay is > 0

    But you will loose all required uBoot settings and need to set them manually.
    Then you might be able to load the current firmware with tftpboot and flash the image back.

    I just desoldered the uBoot and changed the bootdelay with hexed...

    Jürgen

Children
No Data
Unfiltered HTML