Reputation
Next privilege 125 Rep.
Vote down
Badges
5
Impact
~1k people reached

  • 0 posts edited
  • 0 helpful flags
  • 3 votes cast
Aug
21
awarded  Popular Question
Mar
6
awarded  Scholar
Mar
6
accepted No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
Mar
6
answered No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
Feb
23
comment No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
I've now got traffic flowing from the Cisco end to the Strongswan end by adding a reverse direction rule to the access list so I can browse the webserver from the client. I still can't get responses to pings in the opposite direction though I can see the packet count increasing in the SA details on the Cisco side in relation to the pings sent to it - another NAT or Access-List rule needed to avoid black holing?
Feb
20
revised No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
edited body
Feb
19
comment No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
Pasted a better formatted ping output in the question.
Feb
19
revised No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
fix typo
Feb
19
comment No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
@ecdsa apologies that was a typo: ip-10-87-50-96#ping 172.31.1.1 source gigabitEthernet 2 repeat 2 Type escape sequence to abort. Sending 2, 100-byte ICMP Echos to 172.31.1.1, timeout is 2 seconds: Packet sent with a source address of 10.87.189.59 .. Success rate is 0 percent (0/2)
Feb
18
awarded  Editor
Feb
18
revised No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
More diagnostic information
Feb
18
asked No traffic routing between Cisco CSR1000v and Strongswan IPSec end points on AWS
Feb
1
awarded  Supporter
Nov
10
awarded  Autobiographer