OK, he is a intreasting one. I have a ASA 5510 which has been running fine (and still is). Not had any problems with devices etc. connecting to outside work and back.
I'm trying to get a Meraki AP working to trial, however I'm getting something very odd happening. It connects to the cloud as it is registering, but it has a error message 'Bad Gateway'. I have been in contact with Meraki support and unfortantly not got very far. What we have found is that the return packets are being blocked by my inbound access-list. However this shouldn't be the case as it is a stateful firewall, so for the duration of that session any packets going out should have th return packets go through with out a problem. So why is it this isn't happeneing for this one device ?
Has anyone else got the Meraki AP's running with these firewalls? Is there something obvious I'm missing. VLAN, DHCP etc etc all fine, so we can rule out internal network etc.
Note:Try upgrading the AP firmware to latest ,Re-check Gatway settings on AP, try using other GW just for testing purpose ,these are all troublshooting steps you can check apart from the info mentioned in the link above.
i took this home on my internet broadband connection and the AP connects fine and the firmware is reported as up-to-date.
On the ASA 5510 the firewall is open for the ports in listed in the firewall section for outbound ACL's. As I said the odd part is we are getting an attempt by the Cloud Controller to come back in but the firewall is blocking on the inbound ACL. Which is correct as the return parts should be part of the stateful connection from the AP to the cloud controller. Unless there is a bug with the AP firmware and the packets are malformed.
Hence my question, is anyone else using the AP's with a Cisco ASA firewall. They must be surely.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...