accel-ppp.git/accel-pppd/net.c, branch 1.14.0High performance PPTP/L2TP/SSTP/PPPoE/IPoE server for Linux (mirror of https://github.com/accel-ppp/accel-ppp.git)
https://git.amelek.net/accel-ppp/accel-ppp.git/atom?h=1.14.02021-12-20T15:00:32+00:00T55: add netlink buffer size configuration parameters2021-12-20T15:00:32+00:00Sergey V. Lobanovsergey@lobanov.in2021-12-20T15:00:32+00:00urn:sha1:5249bf6428e70aa489aa9b8c44b16935c391a7fe
Netlink buffers may overflow so it might be useful to increase send and receive
netlink buffer sizes.
Two parameters to [common] configuration section added: nl-rcv-buffer,
nl-snd-buffer.
It is required to set (sysctl) net.core.wmem_max>=nl-snd-buffer and
net.core.rmem_max>=nl-rcv-buffer before running accel-pppd
To check current netlink buffer size and related info use the following command:
% ss -f netlink -m
0 0 rtnl:kernel * skmem:(r0,rb212992,t0,tb212992,f0,w0,o0,bl0,d0)
0 0 rtnl:-1140221812 * skmem:(r0,rb2048000,t0,tb80000,f0,w0,o0,bl0,d0)
0 0 rtnl:accel-pppd/14285 * skmem:(r0,rb2048000,t0,tb65536,f0,w0,o0,bl0,d0)
...
(Please check man ss to get the meaning for r,rb,t,tb,f,w,o,bl and d params)
In the ss output you will see the values doubled from configured.
First accel-pppd netlink socket will use default values (rcv=1048576, snd=32768)
regardless of configured nl-rcv-buffer and nl-snd-buffer values.
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
vrf: T10: Add VRF support2021-12-16T20:03:52+00:00DmitriyEshenkodmitriy.eshenko@vyos.io2021-12-10T16:43:42+00:00urn:sha1:737bf4d8b6e9e1bf50be69e8c99028bb2696190c
Co-authored-by: Sergey V. Lobanov <svlobanov@users.noreply.github.com>
Co-authored-by: Vladislav Grishenko <themiron@users.noreply.github.com>
Move debug print to proper place2021-03-16T12:34:06+00:00[anp/hsw]sysop@880.ru2021-03-16T12:34:06+00:00urn:sha1:2785d81ec848ebb920c8a612b4eae7876a619a18T13: Fix build procedure2020-04-07T19:59:43+00:00DmitriyEshenkosnooppy@mail.ua2020-04-07T19:59:43+00:00urn:sha1:681299ec22c38c4cb121904238d4d327bfa1498dnet: new function get_ifindex2020-03-18T08:07:38+00:00Simon Chopins.chopin@alphalink.fr2020-02-28T10:28:07+00:00urn:sha1:f5b1c3f98bf082d4ecf57e8f2e3c61fc993d80e7
The index of a given interface is an operation that highly depends on
the network namespace we're in. This patch simply cuts out a function to
get the index for a given interface name from the session initialization
code, and expose it in the ap_net structure.
This function can then be used to refresh the index when moving
interfaces around.
Signed-off-by: Simon Chopin <s.chopin@alphalink.fr>
check for setns availability2016-07-19T13:22:57+00:00Dmitry Kozlovxeb@mail.ru2016-07-19T13:22:57+00:00urn:sha1:5af337d4bd95ba001527f1a298f4594ad643f57bnet: code cleanup2016-07-14T17:33:48+00:00Dmitry Kozlovxeb@mail.ru2016-07-14T17:33:48+00:00urn:sha1:69ddf69d08072819deb3adde2be28f613f92cac3fix def_move_link2016-07-14T17:33:12+00:00François Cachereulf.cachereul@alphalink.fr2016-07-12T13:56:55+00:00urn:sha1:52912d5b9980bb11b611d8668da9449e34830887
Do not know how this could work. It make more sense to move an interface
from its original namespace not from its destination.
Signed-off-by: François Cachereul <f.cachereul@alphalink.fr>
implemented support for network namespace2016-07-11T06:47:04+00:00Dmitry Kozlovxeb@mail.ru2016-07-11T06:47:04+00:00urn:sha1:e0cca4344f70b9c9e23e3c6a7e17c8e93c765184
This is done using radius attribute NAS-Port-Id. The new format of this attribute is NAS-Port-Id=[ns/][name].
Namespaces must be created malually by "ip netns add ..." command
preparation for DPDK intergation (part 6)2016-04-15T14:24:10+00:00Dmitry Kozlovxeb@mail.ru2016-04-15T13:06:20+00:00urn:sha1:b80e64a320b22c0e966ec1e42bda4929d5a748ec