Cisco ASA EZVPN (Revisited)
KB ID 0001261 Problem EZVPN is a technology that lets you form an ISAKMP/IPSEC VPN tunnel from a site with a dynamically assigned IP (EZVPN Client,) back to a device with a static IP (EZVPN Server). I’ve called this EZVPN revisited, because this is a technology I’ve talked about before. So why am I here again? Well back then I used the ASDM. If you do that now, you need to go in and mess about with things to get it to work...
VMware: Windows VM – No Mouse & Cannot Install VMware Tools
KB ID 0001370 Problem Every time this happens to me I have a rant about it, and everyone looks perplexed, surely this does not only happen to me? Using ESX6.5 I build a new Windows VM, and theres no mouse, web client has nothing, try the VMRC then I get a mouse pointer, but it’s as responsive as trying to play chess with a firehose! Once you install VMware tools it’s fine, but here’s the problem – try...
ASA5505 – ‘This Licence Does Not Allow Configuring Of More Than 2 Interfaces’
KB ID 0001367 Problem When attempting to bring up a ‘3rd VLAN’ on an ASA 5505 firewall you see an error like this; Petes-ASA# configure terminal Petes-ASA(config)# int vlan 3 Petes-ASA(config-if)# nameif DMZ ERROR: This license does not allow configuring more than 2 interfaces with nameif and without a “no forward” command on this interface or on 1 interface(s) with nameif already configured....
Cisco ASA 8.2 Upgrade to 8.3
KB ID 0001366 Problem I can’t believe I’m writing this, it’s been so long since 8.3 was released (7 Years!) And still there’s firewalls out there running old code? Why is the 8.3 upgrade important? This update made some very major changes to the way we did NAT, and also the way we wrote ACL’s. It was a big change. I remember keeping my client firewalls on 8.2 for a while until I fully understood the...
Meraki Block Page http://wired.meraki.com:8090 ‘Not Found’
KB ID 0001365 Problem If you have a Meraki Security device and have enabled ‘Content Filtering’, instead of a nice ‘block-page’ informing you why you are being blocked you may see this; http://wired.meraki.com:8090 This is happening because your Corporate DNS is resolving ‘wired.meraki.com’ to 54.241.7.184, which you can also see if you look at the URL you are trying to connect to it on port 8090. A...