/dports/editors/calligra/calligra-3.2.1/plugins/stencilsdocker/stencils/Cisco/ |
H A D | wan.desktop | 2 Name=WAN 3 Name[bg]=WAN 4 Name[bs]=WAN 5 Name[ca]=WAN 7 Name[cs]=WAN 8 Name[da]=WAN 9 Name[de]=WAN 10 Name[el]=WAN 12 Name[es]=WAN 13 Name[et]=WAN [all …]
|
/dports/editors/calligra/calligra-3.2.1/plugins/stencilsdocker/stencils/Network/ |
H A D | flash.desktop | 2 Name=WAN Connection 3 Name[bg]=Връзка WAN 4 Name[bs]=WAN konekcija 5 Name[ca]=Connexió WAN 7 Name[cs]=WAN připojení 10 Name[el]=Σύνδεση WAN 12 Name[es]=Conexión WAN 13 Name[et]=WAN-ühendus 14 Name[eu]=WAN konexioa 15 Name[fi]=WAN-yhteys [all …]
|
/dports/net-mgmt/librenms/librenms-21.5.1/mibs/peplink/ |
H A D | WAN | 2 WAN DEFINITIONS ::= BEGIN 30 "MIB module for WAN." 66 "Number of WAN network." 77 "WAN Table" 112 "WAN ID." 120 "WAN Name." 138 "WAN status." 168 "WAN cell id. 202 "WAN Network IP Table" 231 "WAN network IP id." [all …]
|
/dports/net-mgmt/observium/observium/mibs/peplink/ |
H A D | WAN | 2 WAN DEFINITIONS ::= BEGIN 30 "MIB module for WAN." 66 "Number of WAN network." 77 "WAN Table" 112 "WAN ID." 120 "WAN Name." 137 "WAN status." 167 "WAN cell id. 201 "WAN Network IP Table" 230 "WAN network IP id." [all …]
|
/dports/net-mgmt/librenms/librenms-21.5.1/tests/snmpsim/ |
H A D | pepwave.snmprec | 8 1.3.6.1.2.1.2.2.1.2.2|4|WAN 1 9 1.3.6.1.2.1.2.2.1.2.3|4|WAN 2 264 1.3.6.1.2.1.31.1.1.1.1.2|4|WAN 1 265 1.3.6.1.2.1.31.1.1.1.1.3|4|WAN 2 408 1.3.6.1.4.1.23695.2.1.2.1.2.0|4|WAN 1 409 1.3.6.1.4.1.23695.2.1.2.1.2.1|4|WAN 2 415 1.3.6.1.4.1.23695.2.1.2.1.2.7|4|Wi-Fi WAN 416 1.3.6.1.4.1.23695.2.1.2.1.2.8|4|LAN 1 as WAN 417 1.3.6.1.4.1.23695.2.1.2.1.2.9|4|LAN 2 as WAN 418 1.3.6.1.4.1.23695.2.1.2.1.2.10|4|LAN 3 as WAN
|
H A D | hpe-ilo_4.snmprec | 37 1.3.6.1.2.1.2.2.1.2.2|4|WAN Miniport (L2TP) 38 1.3.6.1.2.1.2.2.1.2.3|4|WAN Miniport (SSTP) 39 1.3.6.1.2.1.2.2.1.2.4|4|WAN Miniport (IKEv2) 40 1.3.6.1.2.1.2.2.1.2.5|4|WAN Miniport (PPTP) 41 1.3.6.1.2.1.2.2.1.2.6|4|WAN Miniport (PPPOE) 42 1.3.6.1.2.1.2.2.1.2.7|4|WAN Miniport (IP) 43 1.3.6.1.2.1.2.2.1.2.8|4|WAN Miniport (IPv6) 44 1.3.6.1.2.1.2.2.1.2.9|4|WAN Miniport (Network Monitor) 54 1.3.6.1.2.1.2.2.1.2.19|4|WAN Miniport (IP)-QoS Packet Scheduler-0000 58 1.3.6.1.2.1.2.2.1.2.23|4|WAN Miniport (IPv6)-QoS Packet Scheduler-0000 [all …]
|
/dports/net-mgmt/observium/observium/mibs/bdcom/ |
H A D | NMS-WAN-MIB | 2 -- NMS-WAN-MIB.my: NMS WAN MIB 11 NMS-WAN-MIB DEFINITIONS ::= BEGIN 31 "NMS WAN interface table." 39 "NMS WAN interface table entry." 67 "NMS WAN interface connection type. This type is temporarily unknown" 75 … "NMS WAN interface IP address, the same value as ipAdEntAddr in ipAddrTable." 83 … "NMS WAN interface mask, the same value as ipAdEntNetMask in ipAddrTable." 91 "NMS WAN interface default gateway." 99 "NMS WAN interface master DNS address." 107 "NMS WAN interface slave DNS address." [all …]
|
/dports/net-mgmt/librenms/librenms-21.5.1/includes/definitions/discovery/ |
H A D | netscaler-sdwan.yaml | 1 mib: CITRIX-NetScaler-SD-WAN-MIB 4 hardware: CITRIX-NetScaler-SD-WAN-MIB::sdWANStatsApplianceName 5 serial: CITRIX-NetScaler-SD-WAN-MIB::sdWANStatsApplianceSerialNumber 7 - CITRIX-NetScaler-SD-WAN-MIB::sdWANStatsApplianceOSVersion 8 - CITRIX-NetScaler-SD-WAN-MIB::sdWANStatsApplianceSoftwareVersion 9 …n_template: 'OS: {{ CITRIX-NetScaler-SD-WAN-MIB::sdWANStatsApplianceOSVersion }}, SW: {{ CITRIX-Ne…
|
H A D | icotera.yaml | 9 descr: "WAN port transceiver" 16 descr: "WAN port transceiver" 24 descr: "WAN port Rx Power" 31 descr: "WAN port Tx Power" 39 descr: "WAN port transceiver"
|
/dports/www/grafana8/grafana-8.3.6/vendor/github.com/hashicorp/consul/website/content/docs/k8s/installation/multi-cluster/ |
H A D | index.mdx | 20 ## Traditional WAN Federation vs. WAN Federation Via Mesh Gateways 22 Consul provides two mechanisms for WAN (Wide Area Network) federation: 24 1. Traditional WAN Federation 25 1. WAN Federation Via Mesh Gateways (newly available in Consul 1.8.0) 27 ### Traditional WAN Federation 29 With traditional WAN federation, all Consul servers must be exposed on the wide area 40 ![Traditional WAN Federation](/img/traditional-wan-federation.png 'Traditional WAN Federation') 42 ### WAN Federation Via Mesh Gateways 44 To solve the problems that occurred with traditional WAN federation, 45 Consul 1.8.0 now supports WAN federation **via mesh gateways**. This mechanism [all …]
|
/dports/sysutils/consul/consul-1.10.3/website/content/docs/k8s/installation/multi-cluster/ |
H A D | index.mdx | 20 ## Traditional WAN Federation vs. WAN Federation Via Mesh Gateways 22 Consul provides two mechanisms for WAN (Wide Area Network) federation: 24 1. Traditional WAN Federation 25 1. WAN Federation Via Mesh Gateways (newly available in Consul 1.8.0) 27 ### Traditional WAN Federation 29 With traditional WAN federation, all Consul servers must be exposed on the wide area 40 ![Traditional WAN Federation](/img/traditional-wan-federation.png 'Traditional WAN Federation') 42 ### WAN Federation Via Mesh Gateways 44 To solve the problems that occurred with traditional WAN federation, 45 Consul 1.8.0 now supports WAN federation **via mesh gateways**. This mechanism [all …]
|
/dports/net-mgmt/prometheus2/prometheus-2.30.3/vendor/github.com/hashicorp/consul/website/content/docs/k8s/installation/multi-cluster/ |
H A D | index.mdx | 20 ## Traditional WAN Federation vs. WAN Federation Via Mesh Gateways 22 Consul provides two mechanisms for WAN (Wide Area Network) federation: 24 1. Traditional WAN Federation 25 1. WAN Federation Via Mesh Gateways (newly available in Consul 1.8.0) 27 ### Traditional WAN Federation 29 With traditional WAN federation, all Consul servers must be exposed on the wide area 40 ![Traditional WAN Federation](/img/traditional-wan-federation.png 'Traditional WAN Federation') 42 ### WAN Federation Via Mesh Gateways 44 To solve the problems that occurred with traditional WAN federation, 45 Consul 1.8.0 now supports WAN federation **via mesh gateways**. This mechanism [all …]
|
/dports/net-im/dendrite/dendrite-0.5.1/vendor/github.com/libp2p/go-libp2p-kad-dht/dual/ |
H A D | dual.go | 29 WAN *dht.IpfsDHT member 145 return combineErrors(dht.WAN.Close(), dht.LAN.Close()) 150 return dht.WAN.RoutingTable().Size() > 0 156 return dht.WAN.Provide(ctx, key, announce) 164 return dht.WAN.GetRoutingTableDiversityStats() 241 wanInfo, wanErr = dht.WAN.FindPeer(ctx, pid) 301 erra := dht.WAN.Bootstrap(ctx) 309 return dht.WAN.PutValue(ctx, key, val, opts...) 330 wanVal, wanErr := d.WAN.GetValue(ctx, key, opts...) 346 p := helper.Parallel{Routers: []routing.Routing{dht.WAN, dht.LAN}, Validator: dht.WAN.Validator} [all …]
|
/dports/net-mgmt/observium/observium/mibs/juniper/ |
H A D | JUNIPER-WX-GLOBAL-REG | 148 WAN Acceleration Model 50" 154 WAN Acceleration Model 55" 160 WAN Acceleration Model 20" 166 WAN Acceleration Model 80" 172 WAN Acceleration Model 100" 184 WAN Acceleration Model 15" 196 WAN Acceleration Model 60" 208 WAN Acceleration Model ISM200" 214 WAN Acceleration Model 1800" 220 WAN Acceleration Model 2600" [all …]
|
/dports/net-mgmt/observium/observium/mibs/exinda/ |
H A D | EXINDA-MIB | 817 DESCRIPTION "WAN Memory TX bytes in" 824 DESCRIPTION "WAN Memory TX bytes out" 838 DESCRIPTION "WAN Memory RX bytes in" 845 DESCRIPTION "WAN Memory RX bytes out" 859 DESCRIPTION "List of WAN Memory peers" 907 DESCRIPTION "Status of WAN Memory peer" 1039 DESCRIPTION "WAN Memory TX bytes in" 1046 DESCRIPTION "WAN Memory TX bytes out" 1060 DESCRIPTION "WAN Memory RX bytes in" 1067 DESCRIPTION "WAN Memory RX bytes out" [all …]
|
/dports/net-mgmt/observium/observium/mibs/paradyne/ |
H A D | HOTWIRE-MSDSL-INTERFACE-MIB | 1397 -- WAN interface to any Network interface, and/or from any WAN interface 1404 -- WAN interfaces. 1413 -- 4) And/Or assign all of one WAN interface to another WAN interface. 1414 -- (e.g. WAN Port-7 to WAN Port-8) (DS1 Cross-connect mode).(REL 2) 1422 -- (e.g. WAN Port 1 TS-1, TS-2 to WAN Port 3 TS-23, TS-24). (REL 2) 1463 -- Network interface mapping. WAN to WAN mapping will be available 1677 WAN port 1 >>> DSL Port 1 1678 WAN port 2 >>> DSL Port 2 1679 WAN port 3 >>> DSL Port 3 1680 WAN port 4 >>> DSL Port 4 [all …]
|
/dports/security/vault/vault-1.8.2/vendor/github.com/hashicorp/consul/website/source/docs/guides/ |
H A D | datacenters.html.md | 3 page_title: "Multiple Datacenters - Basic Federation with the WAN Gossip Pool" 10 # Multiple Datacenters: Basic Federation with the WAN Gossip 19 ## The WAN Gossip Pool 22 WAN gossip pool, interconnecting all Consul servers. 35 To query the known WAN nodes, we use the [`members`](/docs/commands/members.html) 42 This will provide a list of all known members in the WAN gossip pool. In 47 so they do not participate in WAN gossip. Client requests are forwarded by local 59 we are attempting to join a server in the WAN gossip pool. As with LAN gossip, you only 63 flooding, so if one Consul server in a datacenter joins the WAN, it will automatically 80 used to verify that all server nodes gossiping over WAN. [all …]
|
/dports/security/vault/vault-1.8.2/vendor/github.com/hashicorp/vic/tests/manual-test-cases/Group5-Functional-Tests/ |
H A D | 5-28-VICAdmin-Isolated.robot | 18 Suite Teardown Teardown VCH With No WAN 23 Setup VC With No WAN 24 Deploy VCH With No WAN 26 Setup VC With No WAN 39 Deploy VCH With No WAN 40 ${out}= Deploy VCH With No WAN Secret 44 Deploy VCH With No WAN Secret 49 Teardown VCH With No WAN 59 WAN Status Should Fail
|
/dports/net-mgmt/thanos/thanos-0.11.0/vendor/github.com/hashicorp/consul/website/source/docs/guides/ |
H A D | datacenters.html.md | 3 page_title: "Multiple Datacenters - Basic Federation with the WAN Gossip Pool" 10 ## Basic Federation with the WAN Gossip Pool 29 WAN gossip pool, interconnecting all Consul servers. 41 To query the known WAN nodes, we use the [`members`](/docs/commands/members.html) 49 This will provide a list of all known members in the WAN gossip pool. This should 51 so they do not participate in WAN gossip. Client requests are forwarded by local 62 we are attempting to join a server in the WAN gossip pool. As with LAN gossip, you only 65 will only know about itself and must be added to the cluster. Consul 0.8.0 added WAN join 66 flooding, so if one Consul server in a datacenter joins the WAN, it will automatically 70 used to verify that all server nodes gossiping over WAN. [all …]
|
/dports/www/fabio/fabio-1.5.14/vendor/github.com/hashicorp/consul/consul-1.4.2/website/source/docs/guides/ |
H A D | datacenters.html.md | 3 page_title: "Multiple Datacenters - Basic Federation with the WAN Gossip Pool" 10 ## Basic Federation with the WAN Gossip Pool 29 WAN gossip pool, interconnecting all Consul servers. 41 To query the known WAN nodes, we use the [`members`](/docs/commands/members.html) 49 This will provide a list of all known members in the WAN gossip pool. This should 51 so they do not participate in WAN gossip. Client requests are forwarded by local 62 we are attempting to join a server in the WAN gossip pool. As with LAN gossip, you only 65 will only know about itself and must be added to the cluster. Consul 0.8.0 added WAN join 66 flooding, so if one Consul server in a datacenter joins the WAN, it will automatically 70 used to verify that all server nodes gossiping over WAN. [all …]
|
/dports/sysutils/istio/istio-1.6.7/vendor/github.com/hashicorp/consul/website/source/docs/guides/ |
H A D | datacenters.html.md | 3 page_title: "Multiple Datacenters - Basic Federation with the WAN Gossip Pool" 10 ## Basic Federation with the WAN Gossip Pool 29 WAN gossip pool, interconnecting all Consul servers. 41 To query the known WAN nodes, we use the [`members`](/docs/commands/members.html) 49 This will provide a list of all known members in the WAN gossip pool. This should 51 so they do not participate in WAN gossip. Client requests are forwarded by local 62 we are attempting to join a server in the WAN gossip pool. As with LAN gossip, you only 65 will only know about itself and must be added to the cluster. Consul 0.8.0 added WAN join 66 flooding, so if one Consul server in a datacenter joins the WAN, it will automatically 70 used to verify that all server nodes gossiping over WAN. [all …]
|
/dports/net-mgmt/netdisco-mibs/netdisco-mibs-4.010/EXTRAS/indexes/cache/ |
H A D | cisco | 847 CISCO-WAN-3G-MIB CISCO-WAN-3G-MIB.my 866 CISCO-WAN-FEEDER-MIB CISCO-WAN-FEEDER-MIB.my 872 CISCO-WAN-FR-X21-MIB CISCO-WAN-FR-X21-MIB.my 875 CISCO-WAN-MG-MIB CISCO-WAN-MG-MIB.my 876 CISCO-WAN-MODULE-MIB CISCO-WAN-MODULE-MIB.my 877 CISCO-WAN-NCDP-MIB CISCO-WAN-NCDP-MIB.my 879 CISCO-WAN-PAR-MIB CISCO-WAN-PAR-MIB.my 886 CISCO-WAN-SONET-MIB CISCO-WAN-SONET-MIB.my 887 CISCO-WAN-SRCP-MIB CISCO-WAN-SRCP-MIB.my 889 CISCO-WAN-SRM-MIB CISCO-WAN-SRM-MIB.my [all …]
|
/dports/www/grafana8/grafana-8.3.6/vendor/github.com/hashicorp/consul/website/content/docs/install/ |
H A D | ports.mdx | 26 | Wan Serf: The Serf WAN port (TCP and UDP) … 50 **Serf WAN** This is used by servers to gossip over the WAN, to 51 other servers. As of Consul 0.8 the WAN join flooding feature requires 52 the Serf WAN port (TCP/UDP) to be listening on both WAN and LAN interfaces. See also:
|
/dports/sysutils/consul/consul-1.10.3/website/content/docs/install/ |
H A D | ports.mdx | 26 | Wan Serf: The Serf WAN port (TCP and UDP) … 50 **Serf WAN** This is used by servers to gossip over the WAN, to 51 other servers. As of Consul 0.8 the WAN join flooding feature requires 52 the Serf WAN port (TCP/UDP) to be listening on both WAN and LAN interfaces. See also:
|
/dports/sysutils/gomplate/gomplate-3.9.0/vendor/github.com/hashicorp/consul/website/pages/docs/install/ |
H A D | ports.mdx | 27 | Wan Serf: The Serf WAN port (TCP and UDP) … 51 **Serf WAN** This is used by servers to gossip over the WAN, to 52 other servers. As of Consul 0.8 the WAN join flooding feature requires 53 the Serf WAN port (TCP/UDP) to be listening on both WAN and LAN interfaces. See also:
|