Searched full:vrfs (Results 1 – 9 of 9) sorted by relevance
| /linux/Documentation/networking/ |
| H A D | vrf.rst | 11 routing and forwarding domains (aka VRFs, VRF-lite to be specific) in the 24 In addition, VRF devices allow VRFs to be nested within namespaces. For 73 A single l3mdev rule is sufficient for all VRFs. The VRF device adds the 148 outside and inside VRFs) in conjunction with ``net.ipv4.tcp_l3mdev_accept=1`` 155 exclusively be handled by sockets bound to VRFs, as would be the case with 162 Using iproute2 for VRFs 175 covers all VRFs. The l3mdev rule is created for IPv4 and IPv6 on first 178 2. List VRFs 180 To list VRFs that have been created::
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A D | README | 12 However, a similar kind of flexibility can be achieved by using VRFs and 26 The VRFs act as lightweight namespaces representing hosts connected to
|
| /linux/tools/testing/selftests/net/ |
| H A D | vrf_strict_mode_test.sh | 106 log_test ${rc} 0 "${nsname}: add vrf ${vrfname}, ${cnt} vrfs for table ${vrftable}" 121 log_test ${rc} 2 "${nsname}: CANNOT add vrf ${vrfname}, ${cnt} vrfs for table ${vrftable}" 241 log_test ${strictmode} 0 "${nsname}: strict_mode=0 by default, ${vrfcnt} vrfs"
|
| H A D | vrf_route_leaking.sh | 59 # while it is forwarded between different vrfs.
|
| /linux/tools/testing/selftests/net/tcp_ao/lib/ |
| H A D | kconfig.c | 141 "VRFs are not supported (CONFIG_NET_VRF)",
|
| /linux/drivers/net/ |
| H A D | vrf.c | 76 * This means that no matter how many new vrfs will register on the 87 * from a table with exactly two associated vrfs. 96 struct list_head vrf_list; /* VRFs registered to this table */ 256 /* vrfs cannot share the same table */ in vrf_map_register_dev() 1810 * vrfs that share one or more tables. in vrf_strict_mode_change() 1816 /* no tables are shared among vrfs, so we can go back in vrf_strict_mode_change()
|
| /linux/net/ipv6/ |
| H A D | ip6_input.c | 454 /* skb->dev passed may be master dev for vrfs. */ in ip6_protocol_deliver_rcu() 565 /* skb->dev passed may be master dev for vrfs. */ in ip6_mc_input()
|
| /linux/net/ipv4/ |
| H A D | devinet.c | 1395 /* For VRFs, the VRF device takes the place of the loopback device, in inet_select_addr()
|
| H A D | ipmr.c | 2197 /* skb->dev passed in is the loX master dev for vrfs. in ip_mr_input()
|