1) I read in another thread that Mikrotik's have IPSEC issues with Cisco's (VPN 3000 and/or PIX) due to Cisco not following RFC guidelines in relation to SA lifetime. I've been testing a setup to a VPN 3000 and once the tunnel is up it seems fine, but I've seen a few cases where the tunnel doesn't appear to come up (perhaps after a config change, etc.) There is an SA present when this happens that shows 0 current bytes. This still needs more testing on my side to consistently replicate the issue. Is this still a known issue? VPN reliability/re-establishment is absolutely critical for us.
2) For client sites, we'll assign a subnet such as 10.1.1.0/29. But, we want all traffic from that subnet to 10.0.0.0/8 tunneled. We have this working fine. But, if 10.1.1.1/29 is assigned to a Mikrotik interface and a client at 10.1.1.2 tries to ping 10.1.1.1, that traffic is sent over the tunnel. The Mikrotik doesn't see that it's a local subnet (high priority) and respond to that ping. Is there an easy fix for this?
3) What is the best Mikrotik solution to act as a VPN concentrator for other Mikrotik's that can handle hundreds of VPN tunnels (with average throughput of 100-500 kbps each)?
4) What is the best way to establish redundancy/high availablity from client Mikrotiks to our concentrator? If item 1 is resolved, we'd like to stick with a redundant pair of ASA's. Should we just do GRE instead with VRRP, or is there something else that you can suggest?
Thanks.