15 Jan 2016
15:47 UTC
Tom Hill
fw2.man has been rebooted and this will have cleared the issue for now.
Longer term, it seems we may need to schedule an upgrade to the latest version of OpenBSD, and/or a migration to a new firewall pair (whichever causes less pain!)
15 Jan 2016
14:19 UTC
Tom Hill
All traffic is now routing through fw1.man, and this appears to alleviated the issue for now.
We're having a look through fw2.man to see if there's any useful diagnostic output that would explain the behaviour. Once that's done, we'll be rebooting it.
However, fw1.man will remain the primary firewall from here on, so the reboot of fw2.man will not affect your connections any further.
15 Jan 2016
13:55 UTC
Tom Hill
Hello,
We've received two corresponding reports of packet loss through the router fw2.man (which is the primary in the pair fw1.man & fw2.man).
We'll be failing connectivity over to fw1.man shortly, to alleviate the issue.