Sophos Firewall: v18.5 MR1: Feedback and experiences

  • Running in HA, upgraded and both nodes got up OK with new version, now I get "Only administrator can access the auxiliary device" when logging into the "primary" node.... Internet works, so not critical, can try to reboot or swap the nodes, but any suggestions before that?

    ----

    Best regards Martin ;-)

    Sophos UTM Certified Engineer v9.7
    Sophos  XG  Certified Architect v18.5
    Homelab: 1 x XGS2100 SFOS v18.5  - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)

  • Good points.
    A very quick upgrade, one of fastest I can remember.

    fix to the reporting date issue.

    lots of new toys for the business users.

    sad points

    no extra features in IPv6 sections.

    ddos still appears to have a bug which appeared in v18.0.4

    some experimenting to do to see what else has been changed/fixed that is not readily obvious.

    ian

     
    V18.5.x - e3-1225v5 6gb ram with 4 ports - 20w. 
    3 AP55s and 2 APX120s having a holiday until software update is released.
    If a post solves your question use the 'This helped me' link.
  • Seems like the HA is not up2date right now and take some time. The Webadmin will take some more time to get up. 

    __________________________________________________________________________________________________________________

  • No I actually found the cause!

    Creating a in-cognito browser session, allows me to login, so a cokkie session of some sort?! :-)

    Using the "old" browser windows still gives the above warning, closing and reopening browser solves it.

    ----

    Best regards Martin ;-)

    Sophos UTM Certified Engineer v9.7
    Sophos  XG  Certified Architect v18.5
    Homelab: 1 x XGS2100 SFOS v18.5  - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)

  • PS: Try the new DPI Engine Performance. 

    __________________________________________________________________________________________________________________

  • PS2: Keep an eye for Facebook / sites + Firefox with DPI: https://support.sophos.com/support/s/article/KB-000042276?language=en_US

    __________________________________________________________________________________________________________________

  • So the AP-models was ceased to exist after 18.5:

    Legacy AP Series support on upcoming SFOS versions and future hardware platforms (sophos.com)

    But as I see in 18.5 MR-1 there are still support and firmware for the old models, have you changed plans?

    ----

    Best regards Martin ;-)

    Sophos UTM Certified Engineer v9.7
    Sophos  XG  Certified Architect v18.5
    Homelab: 1 x XGS2100 SFOS v18.5  - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)

  • Which platform are you currently talking about? XG Hardware should still support legacy AP. XGS Hardware will not support Legacy AP. 

    SFOS running on XGS Series hardware does not support the following accessories and components:

    • APX 320X is currently not supported in SFOS on any platform. It is supported only in Sophos Central.
    • Legacy access points: AP 15, AP 15C, AP 55, AP 55C, AP 100, AP 100C, AP 5, AP 10, AP 30, AP 50
    • Flexi Port modules for XG Series hardware models.
    • Desktop 3G/4G and Wi-Fi modules for XG Series hardware.

    __________________________________________________________________________________________________________________

  • "In SFOS version 18.5 and higher running on XG Series appliances, support will no longer be included for the AP Series access points which reached their end-of-life date in 2018. "

    So XG without the (S), cannot read about the XGS thing from the KB :-)

    ----

    Best regards Martin ;-)

    Sophos UTM Certified Engineer v9.7
    Sophos  XG  Certified Architect v18.5
    Homelab: 1 x XGS2100 SFOS v18.5  - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)

  • Seems like the KBA is outdated. I forwarded this request to update the KB. 

    __________________________________________________________________________________________________________________