Ive managed to fix the issue. It wasn't with the MX it was with the Syslog server. There was a setting to specify source and the MX's IP address had changed from when it was in bridge mode to now be our gateway device. Many frustrating hours later. It was quite interesting as I'd never noticed that it shows the device name, normally there are that many MX records you never see the WiFi ones. At least some good has come out of this little challenge. Gary ... View more

Yes the AP's are all in the same network and organisation as the MX. Same subnet, no fancy VLANs or routing. They are also literally plugged in to the MX, same as the Syslog server. I haven't been brave enough to put the "beta" firmwares on, I did notice there is an updated Stable release candidate so will try updating it to 14.50 tonight. Gary ... View more

Hi, Thank you for your reply. Yes all the same port forwarding rules have been set up again (as it cleared those but kept the outgoing rules when I switched it over). I didn't notice but in your example where yours shows "MX1" ours only shows our WiFi AP names, there are none for the MX at all since I switched it over. Looking back I can see it used to log the MX flows.   Ive tried factory defaulting it this morning and getting the settings pushed down to it again. Ive tried removing and re-adding the syslog server, which is receiving but only "WiFi" flows, urls, events. On the syslog settings it is currently set to send out "Flows, URLs, Security Events, Appliance event log, Switch event log, Air Marshal events and Wireless event log". On the Firewall settings Inbound firewall logging is enabled and all of our 23 outbound rules all have logging enabled.   I cant find any other logging options that might need turning on? We are currently on MX14.45. Thanks Gary ... View more

Hi Raj, Thank you for that, works perfectly. Had a feeling it would be buried somewhere. Thanks Gary ... View more