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.
I have a site-2-site IPSec vpn between an 1801 ISR and an ASA 5510. Monitoring the vpn on the ASA, I see there is constant traffic on it, when I would have expected only intermittent traffic. How can I trace what is actually causing traffic to cross ...
I have just bought an ASA 5510 and am trying to configure it, but it is not working the way I expect.I have several internal servers which need to be accessed from the web. If I create a NAT entry for each, and a corresponding access rule, the server...
I have an 877 router that will not connect to my ISP. I've tried the troubleshooting docs, when I run a PPP debug, I get Vi2 CHAP: O RESPONSE id 1 len 34 from <my isp username>"Vi2 CHAP: I FAILURE id 1 len 42 msg is "CHAP authentication failure, unit...
I have a Easy VPN remote configured on an 877 router, connecting to an 1801 running Easy VPN server. The vpn connects, and the 877 can ping clients on the remote network, but no clients on the LAN connected to the 877 can ping the remote LAN. Both si...
Found the answer: Packet capture wizard in the ASA can track all packets between any interface or IP address/range. By capturing from the source subnet, then sending the output to Wireshark, the culprit is revealed.
Hi,I don't have a Netflow box, and it looks very complicated!!What I really need is a simple metod of tracing the source IP of traffic going through the VPN.
So, if I upgrade from 8.2 to 8.3, I could use the internal names/ip's in my ACLs? As you say, this would be much more flexible, as I do indeed plan to change external IP scheme eventually.
