Same problem, and I never fix it, every time I change globals.inc it make some permission errors. Can anyone help us to grant right permisions again ?

@vbentley: Do you have a public or private IP address on your WAN interface now? It is usual to have to configure the ADSL router to change from routing to bridging before PPPoE will work. I now have a public IP on the WAN interface, apparently these devices are configured in 'DHCP Passthrough' mode so it acts as a modem and then passes the connection specific configuration (IP, GW, DNS etc) through to the 'cable' router via DHCP.

Thanks for looking.  No major changes to the network, the load or the firewall config recently.  We don't have a HA pair.  We upgraded to 2.3-RELEASE on the 17th of last month. We do have a cold backup which I swapped over to but we had another crash afterwards,  I uploaded the crash report at about 08:24AM central time.  To be extra safe I did not transfer the config from the running firewall to the backup so it is still running the config from the 17th of last month when we upgraded both firewalls. The new crash looks pretty different from the last one I uploaded I am unsure if it still points towards the bce card/driver.

If we didn't enable the DHCP server by default, we'd be overrun with "I plug in and it doesn't do anything". Many comparable "enterprise" solutions enable DHCP server out of the box with the default config for the same reason. Not going to change, and not "home network or small business", it's more common than not.

Hello, no i do the same way and check connections with additional Linux-Servers and NRPE too. It`s a 2nd-way-Solution but works.

Thanks Chris! I will test it with the next snap.

That sounds like something upstream of your system is blocking all pings on that WAN.

I still not very explored the switches, are dlink 1510, I for now I have only created the VLANs on the switch and every door I put in state hybrid con vlan tagged as I attribute to vlan the radius server, which should aim at the switch?

Seems like you probably need NAT reflection enabled so that traffic gets sent back into your Exchange server.

I wasn't sure if a backup from an old version would work but since you mention it does, then yes, that sounds like a plan. I'll wait to see the new version then go ahead and upgrade or rebuild if upgrading didn't work. Thanks very much.

@jimp: Works fine here. Are you sure you didn't have some input error on the page? Perhaps your browser half filled in the proxy auth? Yes, tested again just to be sure. However, I did try it in Edge instead of Firefox and it worked. Very strange. I do have the NoScript in Addon in Firefox but its disabled on the firewall IP, so that should not interfear. Anyway, might be good info for someone else with the same problem in the future. Thanks for leading me in the right direction =) Edit: Holy crap did the web interface get slow.

Sorry for the delay. No, I am not touching nothing that should cause the mgmt network to become unreachable. I am 100% sure about that. This is caused almost certainly by the fact that the new 2.3 version is not dealing perfectly with the VM environment that I've created. I will keep on tweaking and maybe some other users can confirm this behaviour with KVM/Proxmox or maybe even come here to find the solution if I come up with any.

Ah ok, I didn't realize that would happen on upgrade too. I never had that box checked to begin with. Excellent.

I had this same very issue! My workaround was to remove the outlook profile then re-add it, all fixed, it took me hours and hours of tinkering to get to this point!

Yes, i can confirm that it is working correcty now. No crashes overnight.