01-04-2019 11:32 AM - edited 02-21-2020 08:37 AM
Ok I have to admit I am an old CLI guy and a medicore FW guy at best anyway. So, saying that, I can see specific ACLS when I issue "the show access-list command" on the CLI on my FWS. however since this is Firepower/FMC we have to use FMC to modify them. For the life of me I cant find THEM!!! I have no problem identifying objects, ports and policies but specific ACLS might as well be on an the Dead Sea Scrolls. I checked all the docs and I just cant find it.. Help !!
01-04-2019 12:31 PM
01-04-2019 02:10 PM
Hello JJEOROME,
As RJI say, the main access lists are found under Policies > Access Control.
If you are looking for other standard or extended ACLs (like for identifying split tunnel or VPN filters, etc) you need to look under the main OBJECTS tab. On the left you will find a section for standard and extended access lists.
Hope this helps,
Matt.
01-05-2019 02:35 AM
Hi,
In FTD you can create ACL's in two way's - Access Control Policy & Pre-Filter Policy.
You can check the ACL's from FMC:
Policy > Access Control Policy
Policy > Pre-Filter Policy
FTD is not like to manage easy like ASA, as most of the Folks are familiar to manage via cli for configuration and tshoot. On FTD case its everything changed and we need to do all the configuration/verification's via the management console and we can tshoot via FTD cli.
HTH
Abheesh
01-08-2019 05:51 AM - edited 01-08-2019 05:55 AM
You can still can run the "show access-list" or "show running-config access-list" command from the LINA CLI of the FTD device. However, you can only view the ACL and not edit it from there. (Unless you know the super-secret TAC method :))
Also note that the ACL in FTD is global, so you don’t need to use a different ACL per interface.
01-08-2019 07:15 AM
01-08-2019 07:22 AM
@Chess Norriskindly please share this super command with us too
01-09-2019 12:54 AM
TAC helped us with this before when one FTD 4100 appliance went berserk after a FXOS upgrade and shut down all sub interfaces – including the management interface - of the device.
This resulted in that we lost all communication between the FMC and the FTD and there was no way we could bring the interfaces up again from the FMC.
To resolve this, TAC had to get config access from the CLI and manually do a “no shut” on all sub interfaces.
I am not sure exactly how they did it, but it was a quite complicated process and you had to modify the /mnt/disk0/enable_configure file from expert mode.
You will then get a warning message when you type the “config terminal” command saying something like “This command is not supported and should not be used”
I therefore don’t recommend anyone to mess with this. The chance that you will end up with a broken configuration is probably huge and you will most likely not be getting any help from TAC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide