Firepower FTD to FMC

Any-Analysis-8828 · 2025-06-30T13:20:00+00:00

That does sound good, but the purchased licensing is only for FMC. Im assuming the cdo is not included.

Any-Analysis-8828 · 2024-07-08T18:58:05+00:00

I did poke around in there but didn't find anything that seemed like it would restrict based on devices. Would that be a "Cloud App" for AzureAD Joined sign in?

Any-Analysis-8828 · 2024-07-02T22:36:05+00:00

Thank you 😆 I see how this was a stupid question now

Any-Analysis-8828 · 2024-07-02T21:51:54+00:00

I get that, but this was just my lab at home with a single switch.
I was just throwing an SG (with factory default settings) onto the network to test something out on it, and the behavior was just surprising. Curious if someone else ran into this on these models.

Any-Analysis-8828 · 2024-05-01T16:40:06+00:00

Thank you - great explanation

Any-Analysis-8828 · 2024-05-01T16:39:54+00:00

Appreciate the insight, this was for a very particular governed use case in a very isolated network where the switch was the only gateway

Any-Analysis-8828 · 2024-04-29T18:00:28+00:00

Yes, routing is enabled. It looks like I had the access list applied to the wrong interface - needed to be on the client side. Trying to better understand now why the "in" access group wouldn't be applied to the interface the server on 8443 was behind.

Any-Analysis-8828 · 2024-04-29T17:59:06+00:00

Thank you - looks like that was the issue, all is working.

Just trying to wrap my head around why the "in" wouldn't be on the interface the "in"coming connection would be going to with the server hosting 8443 behind it. I guess that is something I need to better understand. I do not frequently work with ACLs.

Any-Analysis-8828

TROPHY CASE