Hi Adarsh,
Would you be able to try the following?
In startup config for now, could you add the following change in the unix
section of the vpp startup.
# nodaemon
interactive
Also, I see you have the line gid vpp. I am not sure what that does. Most of
the configs I see do not have that.
What:
Modifying VPP jobs to build on CPOC containers. This change will impact
all vpp-* jobs except vpp-csit-verify-hw-perf*. This change will also
automatically retry failed builds a single time.
When:
2018-02-26 @ 1500 UTC (7:00am PST)
Where:
Please contact us via IRC lf-infra
On 02/22 15:35:06, Marco Varlese wrote:
> Please, see below...
>
> Maybe we should go back to 17.11 as the default version for now (18.02 is
> broken
> for arm64 - confirmed over #dpdk channel on IRC).
>
> Alternatively, a workaround is to disable the DPAA stuff:
> CONFIG_RTE_LIBRTE_DPAA_BUS=n
> Hi devs! I want to know will there any plans for implementation RADIUS
> authentication for policing and ACL to NAT plugin?
> Im telling about VPP as RADIUS client.
Not as far as I know.
Feel free to make a patch or submit a request with more details of how this
would work.
Cheers,
Ole
Hi Brian,
On Thu, 2018-02-22 at 11:48 -0600, Brian Brooks wrote:
> On 02/22 15:35:06, Marco Varlese wrote:
> > Please, see below...
> >
> > Maybe we should go back to 17.11 as the default version for now
> > (18.02 is broken
> > for arm64 - confirmed over #dpdk channel on IRC).
> >
> >
I think, RADIUS should accept following attributes:
1) Login IP address (private address, for mapping NAT 1:1)
2) Framed IP address (public address, if NAT 1:1 is required)
3) Downstream speed (for speed limit, of course, VPP should work as speed
shaper, or NAT plugin should work with speed
Please, see below...
Maybe we should go back to 17.11 as the default version for now (18.02 is broken
for arm64 - confirmed over #dpdk channel on IRC).
Alternatively, a workaround is to disable the DPAA stuff:
CONFIG_RTE_LIBRTE_DPAA_BUS=n
CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=n
