回复: [vpp-dev] Add ip route without next-hop-address

2019-09-09 Thread shi dave
don't want this ARP request, the 173.2.0.1 is a inner ip, VPP may could not get that ARP response. Best Rregards Dave 发件人: Neale Ranns (nranns) 发送时间: 2019年8月23日 15:18 收件人: shi dave ; vpp-dev@lists.fd.io 主题: Re: 回复: 回复: 回复: [vpp-dev] Add ip route

Re: 回复: 回复: 回复: [vpp-dev] Add ip route without next-hop-address

2019-08-23 Thread Neale Ranns via Lists.Fd.Io
, "vpp-dev@lists.fd.io" Objet : 回复: 回复: 回复: [vpp-dev] Add ip route without next-hop-address Hi Neale, sorry, clerical error, the flow is dpdk-input ip4-input (GigabitEthernet0/b/0) ip4-lookup ip4-rewrite (GigabitEthernet0/a/0) ipsec-output-ip4 dpdk-esp-encrypt dpdk-crypto-input ip4-lo

回复: 回复: 回复: [vpp-dev] Add ip route without next-hop-address

2019-08-23 Thread shi dave
Dave 发件人: vpp-dev@lists.fd.io 代表 shi dave 发送时间: 2019年8月23日 15:03 收件人: Neale Ranns (nranns) ; vpp-dev@lists.fd.io 主题: 回复: 回复: [vpp-dev] Add ip route without next-hop-address Hi Neale, When routing to GigabitEthernet0/a/0, it could run into ipsec-output-ip4

回复: 回复: [vpp-dev] Add ip route without next-hop-address

2019-08-23 Thread shi dave
-dev@lists.fd.io 主题: Re: 回复: [vpp-dev] Add ip route without next-hop-address Hi Dave, When routing to GigabitEthernet0/a/0 what destination MAC address should the packet have? /neale De : shi dave Date : vendredi 23 août 2019 à 05:01 À : "Neale Ranns (nranns)" , "vpp-

Re: 回复: [vpp-dev] Add ip route without next-hop-address

2019-08-22 Thread Neale Ranns via Lists.Fd.Io
Hi Dave, When routing to GigabitEthernet0/a/0 what destination MAC address should the packet have? /neale De : shi dave Date : vendredi 23 août 2019 à 05:01 À : "Neale Ranns (nranns)" , "vpp-dev@lists.fd.io" Objet : 回复: [vpp-dev] Add ip route without next-hop-address

回复: [vpp-dev] Add ip route without next-hop-address

2019-08-22 Thread shi dave
Hi Neale, yes, it's a correct behavior for VPP ARP for 173.2.0.1, but in my case, 173.2.0.1 is a inner ip(src 173.10.10.10, dst 173.2.0.1), the outer ip is IPSEC tunnel ip(src 172.16.3.15, dst 172.16.3.1), so that's no sense to get the mac of 173.2.0.1. so is there have any method to route the