Search results
Jump to navigation
Jump to search
Page title matches
- 9 KB (1,543 words) - 16:22, 30 March 2024
- 589 bytes (74 words) - 06:31, 17 March 2024
Page text matches
- {{r|Internet Protocol version 4}}407 bytes (47 words) - 06:31, 17 March 2024
- ...tations, local area networks, servers, and the public [[Internet]] using [[Internet Protocol version 4]], [[Internet Protocol version 6]], or both.287 bytes (35 words) - 14:31, 14 July 2008
- ...Path First]] interior routing protocol, principally to let it carry both [[Internet Protocol version 4]] and [[Internet Protocol version 6]] information, but also to integrate va292 bytes (38 words) - 21:48, 19 October 2008
- The set of challenges and workarounds as the Internet runs out of [[Internet Protocol version 4]] addresses, yet [[Internet Protocol version 6]] is not quite ready for pri214 bytes (30 words) - 11:10, 27 August 2008
- In the [[Domain Name Service]], that function which takes an [[Internet Protocol version 4]] (IPv4) or [[Internet Protocol version 6]] '''address''' and returns the c225 bytes (27 words) - 11:01, 1 September 2008
- A notation for [[Internet Protocol]] addresses, introduced for [[Internet Protocol version 4]] but also adapted to [[Internet Protocol version 6]], in which addresses a362 bytes (51 words) - 10:58, 8 August 2010
- ...reach hosts local to it, not other networks; the concept applies to both [[Internet Protocol version 4]] and [[Internet Protocol version 6]]225 bytes (34 words) - 19:21, 10 January 2010
- {{r|Internet Protocol version 4}} {{r|Internet Protocol version 4}}385 bytes (43 words) - 00:44, 20 July 2008
- {{r|Internet Protocol version 4}}761 bytes (100 words) - 09:48, 22 October 2010
- A set of extensions to the [[OSPF]] version 2 (i.e., for [[Internet Protocol version 4]]) routing protocol, intended to provide information for route computation332 bytes (42 words) - 10:59, 7 September 2008
- {{r|Internet Protocol version 4}}709 bytes (90 words) - 16:07, 11 January 2010
- {{r|Internet Protocol version 4}}350 bytes (43 words) - 14:59, 20 March 2024
- #Redirect [[Internet Protocol version 4]]41 bytes (4 words) - 13:49, 7 August 2008
- #Redirect [[Internet Protocol version 4]]41 bytes (4 words) - 14:04, 7 August 2008
- {{r|Internet Protocol version 4}}361 bytes (42 words) - 23:40, 13 September 2008
- {{r|Internet Protocol version 4}}2 KB (248 words) - 05:56, 17 March 2024
- {{r|Internet Protocol version 4}}907 bytes (117 words) - 14:59, 20 March 2024
- {{r|Internet Protocol version 4}}680 bytes (84 words) - 19:33, 31 July 2008
- ...trative and technical measures dealing with the procedures for assigning [[Internet Protocol version 4]] (IPv4) space.170 bytes (21 words) - 18:55, 23 January 2010
- ...rvice]] (DNS), '''reverse mapping''' is the function that, when given an [[Internet Protocol version 4]] or an [[Internet Protocol version 6]] address, returns an associated '''d757 bytes (110 words) - 06:27, 17 March 2024
- {{r|Internet Protocol version 4}}1,016 bytes (127 words) - 05:56, 17 March 2024
- ...ally, the version used in the Internet, to carry routing information about Internet Protocol version 4 addresses, is '''Integrated IS-IS''', as ISIS was originally developed only2 KB (257 words) - 16:21, 30 March 2024
- {{r|Internet Protocol version 4}}530 bytes (69 words) - 15:51, 11 January 2010
- {{r|Internet Protocol version 4}}626 bytes (79 words) - 16:23, 11 January 2010
- ...s remote assumption''', which means if a destination host is in the same [[Internet Protocol version 4]] subnet as the host that wants to send to that destination,1,016 bytes (160 words) - 16:10, 7 February 2009
- [[Internet Protocol version 4]] and [[Internet Protocol version 6]] packets are datagrams.1 KB (217 words) - 15:19, 28 September 2008
- ...ons '''converge onto''' (i.e., all run over) a common infrastructure using Internet Protocol version 4 or Internet Protocol version 6.3 KB (351 words) - 04:39, 5 April 2024
- ...ocol]] addresses between two different address spaces, most often, in an [[Internet Protocol version 4]] context, the nonroutable "private" address space (see RFC 1918 and RFC 573 KB (507 words) - 20:02, 15 June 2010
- ...</ref> to the '''Open Shortest Path First (OSPF)''' Version 2 (i.e., for [[Internet Protocol version 4]] have been defined to support routes that not only reflect the shortest, c2 KB (351 words) - 18:23, 10 February 2011
- An '''internet service provider''' manages connectivity using [[Internet Protocol version 4]] (IPv4), [[Internet Protocol version 6]] (IPv6), or both. It creates conne3 KB (456 words) - 15:00, 20 March 2024
- ...ention, a default route is shown with a prefix length of zero, as in the [[Internet Protocol version 4]] route <code>0.0.0.0/0.</code> Some routing protocols will generate a def1 KB (203 words) - 01:44, 27 July 2008
- Both in [[Internet Protocol version 4]] and [[Internet Protocol version 6]], the most basic principle of routing3 KB (398 words) - 12:35, 30 March 2024
- ...been planned for such growth. It dealt with the procedures for assigning [[Internet Protocol version 4]] (IPv4) space, working around the limitations of [[routing]] technology of4 KB (587 words) - 14:57, 20 March 2024
- ...ncluding Cisco's Hot Standby Router Protocol. It is widely implemented for Internet Protocol version 4, but the variant for Internet Protocol version 6 is still a draft. ...t also needs the layer 2 address of a router, before it send to it. In the Internet Protocol version 4 version of VRRP, assuming that the local subnet is broadcast multiaccess us4 KB (761 words) - 07:37, 18 March 2024
- ...zations to see if they are using all their space, a scarce resource with [[Internet Protocol version 4]].2 KB (356 words) - 05:49, 8 April 2024
- ...unique on an Internet-wide basis (see [[locality of networks]]), such as [[Internet Protocol version 4]] (IPv4) and now [[Internet Protocol version 6]] (IPv6) '''addresses''', ''5 KB (784 words) - 10:53, 2 April 2024
- In media access control addressing at the data link layer (at layer 2), or in Internet protocol version 4 and Internet protocol version 6, there are various address formats that eit2 KB (331 words) - 16:24, 30 March 2024
- Both Internet Protocol version 4 and Internet Protocol version 6 can run more securely if features of the In5 KB (761 words) - 16:22, 30 March 2024
- ...onger be possible in any well-maintained network, exploited a feature of [[Internet Protocol version 4]] called the [[directed broadcast]]. This feature caused all hosts on a [[s2 KB (255 words) - 05:49, 8 April 2024
- ...they can tolerate. UDP is best because it imposes the least overhead. In Internet Protocol version 4 (IPv4), the UDP checksum covers either the entire packet or nothing at all,5 KB (740 words) - 16:23, 30 March 2024
- ...pair of broadcast-capable stub networks (e.g., Ethernet/IEEE 802.3), with Internet Protocol version 4 addressing, interconnected by a single router. Under the local versus rem3 KB (465 words) - 07:36, 18 March 2024
- ...TF model, the only data transfer protocol is the Internet Protocol (IP), [[Internet Protocol version 4]] for many years, and now [[Internet Protocol version 6]]. There are also l9 KB (1,294 words) - 06:08, 17 March 2024
- ...e site will share a common [[locality of networks#subnet|subnet]]. In an [[Internet Protocol version 4]] environment, the router that connects the site to a service provider is a1 KB (222 words) - 06:05, 31 May 2009
- ...package. Whenever a node does not know how to send the package it sends an Internet Protocol version 4 or Internet Protocol version 6 packet to a router in the local subnet. Sinc6 KB (958 words) - 16:23, 30 March 2024
- After obtaining Internet Protocol version 4 address space, there remain operational issues in effectively managing it.6 KB (982 words) - 07:30, 18 March 2024
- | url = http://www.ietf.org/rfc/rfc5340.txt}}</ref> which can handle both [[Internet Protocol version 4]] and [[Internet Protocol version 6]]. Familiarity with basic [[Open Shorte18 KB (3,085 words) - 15:00, 20 March 2024
- 16 KB (2,394 words) - 07:30, 18 March 2024
- While the first VPNs used [[Internet Protocol version 4]] (IPv4) for connectivity to the CE if the CE was an onsite physical device15 KB (2,421 words) - 05:49, 8 April 2024
- ...the features of this malware was that the basic code randomly generated [[Internet Protocol version 4]] addresses to which it would try to propagate itself, without checking if5 KB (812 words) - 05:48, 8 April 2024
- ...he network, and in 1983 all nodes on the ARPANET changed over at once to [[Internet Protocol version 4]] (IPv4), which is still in use on the internet today. While this is often17 KB (2,484 words) - 17:02, 22 March 2024