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.
So I have a PTP S2S IPSEC tunnel created for a location I was able to get the connection up I can ping all the Endpoints in the route okay on both sides. However I noticed connecting to RDP or doing SMB it was SLLLOOOOOW. Or just disconnected due to ...
I am working on building out the S2S tunnels and I noticed that the internal IPs of the remote site show as the "unsafe" outside WAN Zone. I am now trying to find a better solution to identify the traffic and do it the right way to separate the traff...
So I am working on getting our firepower for our company setup. So far got things set up for the most part. Now I am just getting connectivity over site-to-site and make sure I can access servers and services throughout. I was adding rules for our XD...
After support calls with cisco and ubiquiti. I took another glimpse. Turned out to be LACP config issue. I thought LACP On in cisco world meant LACP negotation. My Switching LACP to active corrected everything crazy stuff literally a dropdown.
Now is there a way to just do this on the VTI. Or do I have to do on the uplink. Cause if that’s the case I most likely would want second uplink for tunnels? Leave my regular traffic with mtu of 1500
Also Here is the only route I have in FMC per Cisco documentation for that tunnel. Internal Subnet selected include10.0.0.0/2410.0.60.0/2410.0.2.0/2410.0.3.0/24With a metric of 4. The General WAN traffic has metric 20
Good morning, I'm gravitating to that as well but its weird everything looks to be in the right spot. Here is the Routes on the Extranet Router(I put *** to point it out):10.0.0.0/24 dev br0 proto kernel scope link src 10.0.0.1
10.0.1.0/24 dev br1001...
Alright so this is what I have unboxed so far..... So when I was grabbing you that information I spotted something going on which maybe the answer to all of this. From client 10.2.2.100 - > I can ping say 10.0.0.2 but can not ping 10.0.0.3 (another...
