input -> line_input
i got it.


[email protected]
 
From: Luke, Chris
Date: 2018-04-18 00:02
To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco); 
[email protected]; vpp-dev
Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
Yes please, ideally with a Jira ref in the title :)
 
Chris
 
> -----Original Message-----
> From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> [mailto:[email protected]]
> Sent: Tuesday, April 17, 2018 12:01 PM
> To: Luke, Chris <[email protected]>;
> [email protected]; vpp-dev <[email protected]>
> Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Yes it does, do I need to double commit?
> 
> > -----Original Message-----
> > From: Luke, Chris <[email protected]>
> > Sent: Tuesday, April 17, 2018 6:00 PM
> > To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > <[email protected]>; [email protected]; vpp-dev <vpp-
> > [email protected]>
> > Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> >
> > Does this impact stable/1804 also?
> >
> > Chris.
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:[email protected]] On Behalf Of
> > > Klement Sekera
> > > Sent: Tuesday, April 17, 2018 11:50 AM
> > > To: [email protected]; vpp-dev <[email protected]>
> > > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> > >
> > > Hi,
> > >
> > > This patch should fix the CLI issue...
> > >
> > > https://gerrit.fd.io/r/#/c/11851/
> > >
> > > Regards,
> > > Klement
> > >
> > > > -----Original Message-----
> > > > From: [email protected] <[email protected]> On Behalf Of
> > > > [email protected]
> > > > Sent: Tuesday, April 17, 2018 10:55 AM
> > > > To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > > > <[email protected]>; vpp-dev <[email protected]>
> > > > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> > > >
> > > > Thanks
> > > > But it still fail by return : Invalid interface name
> > > >
> > > > my CLI: set interface reassembly GigabitEthernet2/0/0  ip4 also
> > > > not good to use Idx i am sure the intfc-name is right.
> > > >
> > > >
> > > > Help please!
> > > >
> > > > ________________________________
> > > >
> > > > [email protected]
> > > >
> > > >
> > > > From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at
> > > > Cisco) <mailto:[email protected]>
> > > > Date: 2018-04-17 16:22
> > > > To: [email protected] <mailto:[email protected]> ;
> > > vpp-dev
> > > > <mailto:[email protected]>
> > > > Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> > > > Hi,
> > > >
> > > > IP reassembly is a feature which needs to be enabled - did you
> > > enable
> > > > reassembly on your interface? - it doesn't look so from your packet
> trace.
> > > > You can use `set interface reassembly' CLI or the corresponding
> > > > API `ip_reassembly_enable_disable'.
> > > >
> > > > Regards,
> > > > Klement
> > > >
> > > > > -----Original Message-----
> > > > > From: [email protected] <[email protected]> On Behalf Of
> > > > > [email protected]
> > > > > Sent: Tuesday, April 17, 2018 8:39 AM
> > > > > To: vpp-dev <[email protected]>
> > > > > Subject: [vpp-dev] IP Reassembly does not work at 18.04
> > > > >
> > > > > Hello,
> > > > >     I see VPP can support IP Reassembly at 18.04.
> > > > >     I compile the deb and install at ubuntu 16.04,  start vppctl and 
> > > > > up
> > > > the
> > > > > interface & set ip-A, then i could ping the ip(no extra-parm).
> > > > > But it failed with "-l 1473"(at windows), who can help? Thanks
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > first segment-pkt's trace node path:
> > > > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > > > ip4-icmp-input ->
> > > > ip4-
> > > > > icmp-echo-request
> > > > > -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output ->
> > > > > GigabitEthernetX-tx
> > > > >
> > > > >
> > > > > second's trace node path:
> > > > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > > > ip4-icmp-input ->
> > > > ip4-
> > > > > punt -> error-punt
> > > > >
> > > > > ________________________________
> > > > >
> > > > > [email protected]
> > > >
> > > >
> > >
> > > 

Reply via email to