Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-11 Thread Muthu Raj
utput > feature, but we don’t run features for packets that hit the glean (i.e. I > need to ARP) adjacency. So the route needs to resolve via a neighbour > adjacency. It doesn’t have to be a complete adj, hence you don’t need an > ARP response, so any address will do. > > > >

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-11 Thread Muthu Raj
teps that you might > typically use to run a debug version of the vpp executable file, generate > packets, and to analyze results. > wiki.fd.io > > -- > *From:* Muthu Raj > *Sent:* Thursday, May 7, 2020 7:04 PM > *To:* Filip Tehlar -X (ftehlar - PA

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-11 Thread Muthu Raj
; > >ip route add 10.6.0.0/16 via 172.30.x.y lan0.218 > > > > x and y can be anything, apart from x=0 and y=5. > > > > /neale > > > > *From: * on behalf of Muthu Raj < > muthuraj.muth...@gmail.com> > *Date: *Monday 11 May 2020 at 17:3

[vpp-dev] Troubleshooting IPSec in VPP

2020-05-18 Thread Muthu Raj
Hello, I am trying out IPSec on VPP, and used the wiki[1] to create an IPSec tunnel between an AWS instance(remote) and my home. The tunnel was established successfully, and when pinging an IP on the remote side, the icmp req flows over the tunnel, is seen by the remote box, and responded back as

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-14 Thread Muthu Raj
ir.hi 0x0 fdir.lo 0xed0f5862 Packet Types RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers IP6: 12:27:3c:81:f8:f3 -> 12:43:12:c4:21:97 IPSEC_ESP: 2001::1 -> 2001::2 tos 0x00, flow label 0x0, hop limit 253, payload length 132 Let me know if you need more info. Thank

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-15 Thread Muthu Raj
n the SPD. > > The match in the SPD is against SA 20’s tunnel addresses not the policy’s > local/remote range. > > > > /neale > > > > > > *From: *Muthu Raj > *Date: *Thursday 14 May 2020 at 15:51 > *To: *"muthuraj.muth...@gmail.com" > *Cc:

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-13 Thread Muthu Raj
Hi Muthu, > > > > I tried your 4over6 config, it doesn’t work… here’s the fix: > > https://gerrit.fd.io/r/c/vpp/+/27019 > > > > /neale > > > > *From: *Muthu Raj > *Date: *Monday 11 May 2020 at 21:36 > *To: *"Neale Ranns (nranns)" > *Cc:

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-11 Thread Muthu Raj
over the tunnel. On Mon, May 11, 2020, 10:26 PM Neale Ranns (nranns) wrote: > > > > > *From: *Muthu Raj > *Date: *Monday 11 May 2020 at 18:42 > *To: *"Neale Ranns (nranns)" > *Cc: *"Filip Tehlar -X (ftehlar - PANTHEON TECH SRO at Cisco)" < > fte

Re: [SUSPECTED SPAM] [vpp-dev] Troubleshooting IPsec peer behind NAT (AWS instance)

2020-05-28 Thread Muthu Raj
version explaining more things (more like capturing what neale explained to me) with traces in the VPP user docs. Thanks Neale, Filip and everyone. On Fri, May 15, 2020 at 3:11 PM Neale Ranns (nranns) wrote: > > > Hi Muthu, > > > > *From: * on behalf of Muthu Raj < >

Re: [vpp-dev] Observing multiple VRRP Routers acting as master while testing Master/Back-up functionality using vrrp plugin

2020-06-13 Thread Muthu Raj
Hello Amit, state Master flags: preempt yes accept *no* unicast no Your clue lies here. Check https://vpp.flirble.org/master/d7/d40/vrrp_8c_source.html#l00182 and https://vpp.flirble.org/master/dc/dfb/vrrp__cli_8c.html#a2fd76fa6d5cd9ddfef75af8f0d12e016 HTH. Muthu On Sat, Jun 13, 2020 at