Searched refs:vpn (Results 1 – 12 of 12) sorted by relevance
/freebsd/share/examples/ppp/ |
H A D | ppp.linkup.span-isp | 7 !bg ppp -background vpn1 vpn 10 !bg ppp -background vpn2 vpn 13 !bg ppp -background vpnN vpn 15 vpn: 16 set server /var/run/ppp/vpn "" 0177
|
H A D | ppp.linkup.span-isp.working | 7 !bg ppp -background vpn1 vpn 10 !bg ppp -background vpn2 vpn 13 !bg ppp -background vpn3 vpn 15 vpn: 16 set server /var/run/ppp/vpn "" 0177
|
H A D | ppp.linkdown.span-isp.working | 7 !bg pppctl /var/run/ppp/vpn link 1 close 10 !bg pppctl /var/run/ppp/vpn link 2 close 13 !bg pppctl /var/run/ppp/vpn link 3 close 15 vpn:
|
H A D | ppp.linkdown.span-isp | 7 !bg pppctl /var/run/ppp/vpn link 1 close 10 !bg pppctl /var/run/ppp/vpn link 2 close 13 !bg pppctl /var/run/ppp/vpn link N close 15 vpn:
|
H A D | ppp.conf.span-isp.working | 24 # If you connect to the vpn-in diagnostic socket with ``pppctl 25 # /var/run/ppp/vpn-in'' and do a ``show links'', only a single link shows up. 26 # If you connect to the vpn diagnostic socket (which is created in 64 vpn: 88 vpn-in: 96 set server /var/run/ppp/vpn-in "" 0177
|
H A D | ppp.conf.span-isp | 63 # ppp dgram udp wait root /usr/sbin/ppp ppp -direct vpn-in 76 # resulting in the vpn* profiles being called from ppp.linkup.span-isp. 82 # then start ppp using the vpn-nic label. 134 # Our MP version of ppp. vpn is a generic label used by each of the 135 # other vpn invocations by envoking ppp with both labels (see 141 vpn: 165 vpn-nic: 166 load vpn 186 vpn-in:
|
H A D | ppp.conf.sample | 591 vpn-client: 601 vpn-server:
|
/freebsd/sys/powerpc/aim/ |
H A D | moea64_native.c | 157 TLBIE(uint64_t vpn, uint64_t oldptehi) in TLBIE() argument 168 vpn <<= ADDR_PIDX_SHFT; in TLBIE() 176 vpn &= ~(0xffffULL << 48); in TLBIE() 179 __asm __volatile("tlbie %0, 1" :: "r"(vpn) : in TLBIE() 182 __asm __volatile("tlbie %0, 0" :: "r"(vpn) : in TLBIE() 198 vpn |= AP_16M; in TLBIE() 210 __asm __volatile("li 0, 0 \n tlbie %0, 0" :: "r"(vpn) : "r0", "memory"); in TLBIE() 215 vpn_hi = (uint32_t)(vpn >> 32); in TLBIE() 216 vpn_lo = (uint32_t)vpn; in TLBIE() 385 moea64_pte_unset_locked(volatile struct lpte *pt, uint64_t vpn) in moea64_pte_unset_locked() argument [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/marvell/ |
H A D | armada-3720-gl-mv1000.dts | 60 led-vpn { 61 label = "green:vpn";
|
/freebsd/crypto/openssl/test/ |
H A D | params_api_test.c | 477 void *vp, *vpn = NULL, *vp2; in test_param_construct() local 591 if (!TEST_true(OSSL_PARAM_get_octet_string(cp, &vpn, 0, &s)) in test_param_construct() 593 || !TEST_mem_eq(vpn, sizeof("abcdefghi"), in test_param_construct() 631 OPENSSL_free(vpn); in test_param_construct()
|
/freebsd/contrib/unbound/doc/ |
H A D | README.ipset.md | 4 …ome reason. VPN is a solution. But the internet too slow whether all traffics pass through the vpn.
|
/freebsd/share/doc/IPv6/ |
H A D | IMPLEMENTATION | 79 4.8.2 draft-touch-ipsec-vpn approach 2090 in draft-touch-ipsec-vpn-01.txt. However, if you really define pseudo 2093 really mix RFC2401-based interpretation and draft-touch-ipsec-vpn-01.txt 2099 - draft-touch-ipsec-vpn approach (4.8.2) 2110 draft-touch-ipsec-vpn (transportmode + Pseudo-interface) approach 2125 - use draft-touch-ipsec-vpn if you have the control over the other end. 2172 4.8.2 draft-touch-ipsec-vpn approach 2192 the other end is using draft-touch-ipsec-vpn approach too. Since racoon(8)
|