Timeline for Protect traffic originated in remote Cisco ASA
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2017 at 17:02 | comment | added | Ron Maupin♦ | Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. | |
| Jun 16, 2015 at 2:51 | comment | added | Ronnie Smith | Not to be nit picky but protect and encrypt are two very different concepts. Nothing networked is truly protected (e.g. iCloud hack, Fed gov't breach, Iranian Nuclear Power Plant breach, Merkels cell phone tapped, etc.) Ultimately if you want to protect information, do not store or transmit it in electronic format. Again, I don't mean to sound nit picky but this is an important point. | |
| Jun 15, 2015 at 20:44 | answer | added | Sergio | timeline score: 1 | |
| Jun 2, 2015 at 22:19 | comment | added | Sergio | How can I protect traffic originated on the remote ASA? If I ping from the remote ASA (CLI) , I see it's using the External interface (internet) as source IP, but it's not going through the IPSEC tunnel. | |
| S May 29, 2015 at 9:32 | history | suggested | Citizen | CC BY-SA 3.0 |
formatting and a tag, clarified a statement
|
| May 29, 2015 at 5:24 | comment | added | Citizen | Can you clarify and add a specific question? Are you having routing issues? | |
| May 29, 2015 at 5:23 | review | Suggested edits | |||
| S May 29, 2015 at 9:32 | |||||
| May 29, 2015 at 1:04 | answer | added | Ricky | timeline score: 2 | |
| May 29, 2015 at 1:00 | comment | added | Ricky | serverfault.com/questions/346557/… (pre-dates NE) | |
| May 28, 2015 at 21:15 | review | First posts | |||
| May 29, 2015 at 0:19 | |||||
| May 28, 2015 at 21:12 | history | asked | Sergio | CC BY-SA 3.0 |