Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
After a long period of pretty stable operation, we have been experiencing semi-random outages for our WAN and after a brief suspicion of the external network connection are fairly certain our Firepower is actually the cause of the outage and just det...
I am using the Firepower Threat Defense on the Firepower 2100 series chassis and attempting to set up a remote access VPN. To establish the IdentityRealm, I am trying to use a simpleAD instance hosted on AWS. We have a working site to site VPN ...
I am trying to set up a simple site to site VPN from an NGFW Firepower 2110 device to an AWS Virtual Private Gateway. AWS emits a config file, though they don't seem to offer anything specific for the NGFW line. The AWS script starts with this cod...
Yes, took a while to catch it in the act and see the what was happening but there was a bug in an earlier version that basically panicked once the clock skew got too high (difference between network time and machine time exceeded a threshold after a ...
I was unable to resolve this and cisco support wasn't familiar with the device either (they are trying to find someone who is), so abandoning this line of attack and going with a proxy onsite. Everything in docs suggests this should be possible but...
Update: I am reasonably certain now that no packets are entering the AWS end of the network. The most likely cause is that the site to site VPN is not routing the directory lookup traffic . When the cisco device itself is connecting (or trying to...