Release Notes: https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_185_rn.html
"Old" V18.5 MR1 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/128960/sophos-firewall-v18-5-mr1-feedback-and-experiences/
"Old" V18.0 MR5 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/127053/xg-firewall-v18-mr-5-feedback-and-experiences
Please review: https://support.sophos.com/support/s/article/KB-000043489?language=en_US
The specific change you mention was a result of a security review we carried out on the OTP functionality. It is not good practice to provide methods to recover existing secrets because this makes it much…
Installed and all our workstation Heartbeats are missing (after rebooting workstations).
Quite an issue as heartbeats are required for all workstation connectivity. Had to physically connect to the XG to put a temporary access rule in.
Seems to be faster, less having to refresh pages to get all inserts.
No improvements to IPv6.
Added:- still have the heartbeat service failure.
Probably a bit harsh with the no improvements in IPv6, seeing there is a fix listed.
The FQDN tab still does not recognise IPv6 addresses, so when will this be fixed?
XG115W - v19 GA - Home
1225v5 6gb ram, SSID, 4 NICs 20w - v19 EAP - on holiday.
If a post solves your question please use the 'Verify Answer' button.
I think I may have solved this. Details are in a similar issue I had before when I had to re-register an XG in Sophos Central - https://community.sophos.com/sophos-xg-firewall/f/discussions/130861/how-does-heartbeat-work
For future reference and so I can anticipate this in advance, is it normal for new certificates to be generated for a firmware update, or is this specific to this firmware update?
This should not be the case and is not expected to break after the firmware update. Could you create a support case to get the sorted out?
Also have the heartbeat error.
I also get the following message under --> System --> Sophos Central.
Security Heartbeat is not available due to licenses. Check your licenses. Please contact your Sophos partner to update your Sophos Central or Sophos Firewall licenses.
The license is okay, though. Re-registering the XG in Central did not help either.
If it is indeed a certificate issue, your endpoints need access to the internet and a DNS server to be able to update their certificate. This is the problem for us, because without a heartbeat, our endpoints are blocked on our network, so they can't update the certificate. I have to change our firewall rules so they can get the certificate and then they got there Heartbeats and I could change the firewall rules back.
Not sure if you have the same sort of setup so I don't know if this will help you resolve your issue.
I have passed on an Access ID via emmosophos so that devs can have a look at the logs.
Same Issue here. Clients on the VLAN that does NOT require HB on the firewall rule that allows http/https to WAN work fine, clients are authenticated using HB. Clients on the VLAN that requires HB to access the internet cannot authenticate using HB and cannot access anything on the WAN. This was an upgrade 18.5.1 -> 18.5.2 on an XG flashed SG430.
After removing the HB and "match known users" requirement from the firewall rule the clients started authenticating using HB again.
Yes, MR2 regenerate a certificate on the firewall level. We will update all needed documents to reflect this and what to do.
Additionally we are checking, why a client is not able to update in the state of missing hb.
I would have thought that the issue (at least for us) was DNS. Even when we allowed internet access, certificates could not be renewed because we also require Heartbeat to access our internal DNS server (which isn't the XG). Unlike Heartbeat itself, which connects to a fixed IP, certificate renewal must use a URL. If you can't resolve that URL then you aren't going to be able to renew the certificate whatever internal firewall exceptions are present on the XG. Certificates renewed fine once we allowed access to our DNS without a Heartbeat.
Here is a KB about this state: https://support.sophos.com/support/s/article/KB-000043489?language=en_US