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.
FTD 2140 running 7.0.5I need to allow ICMP from outside to an inside server. The requests make it through the FTD's and the log on the server shows it receiving and responding. The Analysis on the FTD never shows the reply and the initiating device...
Network design: core 6509 (VTP server) with multiple 3750 and 3560 model switches directly connected.I added a new 3750 to the network today but it was unable to receive VLAN updates from the VTP server. The domain, password, and all other VTP confi...
The traffic leaves from and returns to the same internal interface. It is policy mapped to the NAT interface. The reply traffic is routed the exact same way as outbound request traffic and it works fine. Only the reply traffic fails.
I don't see how - this internal IP is only allowed to this NAT. But I will definitely check into it more. I'm leaving for a three day weekend but will dig into it on Monday. Thanks for the advice.
More than one. We've run a packet trace on active pings to the public IP and this is the reason for the drop: "(no-adjacency) No valid adjacency". I don't know how it's possible the FTD doesn't have a valid next hop for a response to a packet it ju...
The translated traffic is working both directions. The server in this case is a Meraki MX100 that is hosting around 70 VPN's. Traffic hitting the public IP is being translated to the internal and traffic from the Meraki's IP is being translated to ...
It's a downstream L3 core switch and it is communicating without issue. The server in this case is a Meraki MX100 that is a VPN concentrator and it has around 70 VPN's constantly working. This issue is definitely within the FTD's and how they handl...
