Home
last modified time | relevance | path

Searched full:routers (Results 1 – 25 of 80) sorted by relevance

1234

/linux/tools/testing/selftests/net/
H A Dsrv6_hencap_red_l3vpn_test.sh14 # Routers rt-1,rt-2,rt-3 and rt-4 implement IPv4/IPv6 L3 VPN services
73 # Every fcf0:0:x:y::/64 network interconnects the SRv6 routers rt-x with rt-y
91 # operator's network and SRv6 routers.
111 # Policy (i.a) steers tunneled IPv6 traffic through SRv6 routers
127 # Conversely, Policy (ii.b) steers tunneled IPv4 traffic through SRv6 routers
151 # Policy (i.c) steers tunneled IPv6 traffic through SRv6 routers rt-2,rt-4.
160 # Policy (i.d) steers tunneled IPv6 traffic through SRv6 routers rt-1,rt-3.
187 # IDs of routers and hosts are initialized during the setup of the testing
189 ROUTERS=''
304 # destroy routers
[all …]
H A Dsrv6_hl2encap_red_l2vpn_test.sh14 # Routers rt-1,rt-2,rt-3 and rt-4 implement L2 VPN services
63 # Every fcf0:0:x:y::/64 network interconnects the SRv6 routers rt-x with rt-y
81 # operator's network and SRv6 routers.
110 # Policy (i.b) steers tunneled L2 traffic through the SRv6 routers
138 # IDs of routers and hosts are initialized during the setup of the testing
140 ROUTERS=''
255 # destroy routers
256 for i in ${ROUTERS}; do
313 # Setup the basic networking for the routers
393 # $3 - SRv6 routers configured for steering traffic (End behaviors)
[all …]
H A Dsrv6_end_flavors_test.sh56 # two hosts (hs-1, hs-2) and four routers (rt-1, rt-2, rt-3, rt-4).
57 # Hosts hs-1 and hs-2 are connected to routers rt-1 and rt-2, respectively,
103 # Every fcf0:0:x:y::/64 network interconnects the SRv6 routers rt-x with rt-y in
122 # SRv6 routers.
214 # IDs of routers and hosts are initialized during the setup of the testing
216 ROUTERS=''
331 # destroy routers
332 for i in ${ROUTERS}; do
417 # Setup the basic networking for the routers
501 # $3 - compact way to represent a list of SRv6 routers with their operations
[all …]
H A Dsrv6_end_next_csid_l3vpn_test.sh12 # two hosts and four routers. Hosts hs-1 and hs-2 are connected through an
13 # IPv4/IPv6 L3 VPN service, offered by routers rt-1, rt-2, rt-3 and rt-4 using
69 # Every fcf0:0:x:y::/64 network interconnects the SRv6 routers rt-x with rt-y in
93 # of the IPv6 routing tables in the routers.
315 # IDs of routers and hosts are initialized during the setup of the testing
317 ROUTERS=''
432 # destroy routers
433 for i in ${ROUTERS}; do
490 # Setup the basic networking for the routers
651 # $3 - SRv6 routers configured for steering traffic (End behaviors)
[all …]
H A Dsrv6_end_x_next_csid_l3vpn_test.sh13 # two hosts and four routers. Hosts hs-1 and hs-2 are connected through an
14 # IPv4/IPv6 L3 VPN service, offered by routers rt-1, rt-2, rt-3 and rt-4 using
72 # Every fcf0:0:x:y::/64 network interconnects the SRv6 routers rt-x with rt-y in
96 # of the IPv6 routing tables in the routers.
357 # IDs of routers and hosts are initialized during the setup of the testing
359 ROUTERS=''
482 # destroy routers
483 for i in ${ROUTERS}; do
540 # Setup the basic networking for the routers
711 # $3 - SRv6 routers configured for steering traffic (End.X behaviors)
[all …]
H A Dsrv6_end_dx6_netfilter_test.sh15 # Routers rt-1 and rt-2 implement IPv6 L3 VPN services leveraging the SRv6
170 # destroy routers rt-* and hosts hs-*
176 # Setup the basic networking for the routers
311 log_section "SRv6 VPN connectivity test with netfilter enabled in routers"
H A Dsrv6_end_dx4_netfilter_test.sh15 # Routers rt-1 and rt-2 implement IPv4 L3 VPN services leveraging the SRv6
170 # destroy routers rt-* and hosts hs-*
176 # Setup the basic networking for the routers
306 log_section "SRv6 VPN connectivity test with netfilter enabled in routers"
H A Dsrv6_end_dt4_l3vpn_test.sh22 # Routers rt-1 and rt-2 implement IPv4 L3 VPN services leveraging the SRv6
224 # Setup the basic networking for the routers
365 log_test $? 0 "Routers connectivity: rt-${rtsrc} -> rt-${rtdst}"
413 log_section "IPv6 routers connectivity test"
H A Dsrv6_end_dt6_l3vpn_test.sh23 # Routers rt-1 and rt-2 implement IPv6 L3 VPN services leveraging the SRv6
225 # Setup the basic networking for the routers
370 log_test $? 0 "Routers connectivity: rt-${rtsrc} -> rt-${rtdst}"
418 log_section "IPv6 routers connectivity test"
/linux/include/linux/
H A Dpim.h21 * 0 = Hello Multicast to ALL-PIM-ROUTERS
25 * 3 = Join/Prune Multicast to ALL-PIM-ROUTERS
26 * 4 = Bootstrap Multicast to ALL-PIM-ROUTERS
27 * 5 = Assert Multicast to ALL-PIM-ROUTERS
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dseama.yaml11 D-Link routers such as DIR-645, DIR-842, DIR-859, DIR-860L, DIR-885L,
12 DIR890L and DCH-M225, as well as in WD and NEC routers on the ath79
H A Dtplink,safeloader-partitions.yaml10 TP-Link home routers store various data on flash (e.g. bootloader,
H A Dbrcm,bcm947xx-cfe-partitions.yaml11 home routers. Their BCM947xx boards using CFE bootloader have several
/linux/net/atm/
H A DKconfig54 Multi-Protocol Over ATM allows ATM edge devices such as routers,
56 subnetwork boundaries. These shortcut connections bypass routers
/linux/Documentation/netlabel/
H A Ddraft-ietf-cipso-ipsecurity-01.txt281 Routers work most efficiently when processing fixed length fields. To
282 support these routers there is an optimized form of tag type 1. The format
431 gateways, and routers that support multiple sensitivity labels. A CIPSO
452 parameter does not apply to CIPSO gateways or routers. This parameter need
470 not apply to CIPSO gateways or routers. This parameter need not be defined
517 MAY be in CIPSO or local format. Some CIPSO systems, such as routers, may
683 routers.
/linux/arch/arm/mach-bcm/
H A DKconfig77 This is a network SoC line mostly used in home routers and
176 This SoC line is mostly used in home routers and is some cheaper
/linux/drivers/firmware/broadcom/
H A DKconfig6 Broadcom home routers contain flash partition called "nvram" with all
/linux/drivers/leds/blink/
H A DKconfig23 gateways and routers.
/linux/Documentation/devicetree/bindings/dma/
H A Ddma-router.yaml16 DMA routers are transparent IP blocks used to route DMA request
/linux/drivers/thunderbolt/
H A Dlc.c56 * non-USB4 routers with link controller (that's Thunderbolt 2 and
348 * routers only.
367 * for Thunderbolt 3 routers only.
H A Dclx.c67 /* Called for USB4 or Titan Ridge routers only */
339 /* Only support CL2 for v2 routers */ in tb_switch_clx_enable()
H A Dsb_regs.h3 * USB4 port sideband registers found on routers and retimers
H A Dtb.c54 * @remove_work: Work used to remove any unplugged routers after
280 * accuracy of first depth child routers (and the host router) in tb_increase_tmu_accuracy()
284 * If both routers are v2 then we don't need to do anything as in tb_increase_tmu_accuracy()
314 * If both routers at the end of the link are v2 we simply in tb_enable_tmu()
1208 /* Link the routers using both links if available */ in tb_configure_link()
1592 * can just check for the routers at both ends of the tunnels in tb_attach_bandwidth_group()
1841 /* Needs to be on different routers */ in tb_find_dp_out()
1893 * This should bring the routers in the middle active as well in tb_tunnel_one_dp()
2856 * However, USB4 routers support NVM firmware upgrade if they in tb_start()
2860 /* All USB4 routers support runtime PM */ in tb_start()
[all …]
/linux/include/uapi/linux/
H A Dipv6_route.h22 fallback, no routers on link */
/linux/Documentation/driver-api/gpio/
H A Dusing-gpio.rst15 laptops, phones, tablets, routers, and any consumer or office or business goods

1234