Search results
Jump to navigation
Jump to search
- ...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
- ...Name System]] (and subarticles), [[anycasting]], [[Internet Protocol]], [[Internet Protocol version 4]], [[Internet Protocol version 6]] (and subarticles)4 KB (593 words) - 14:53, 6 April 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
- {{rpr|Internet Protocol version 4}}11 KB (1,461 words) - 10:46, 7 March 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) - 21:34, 26 May 2024
- ...to the local logical structure. For example, if the logical structure used Internet Protocol version 4 in the private address space <ref name=RFC1918>{{citation10 KB (1,563 words) - 07:32, 18 March 2024
- ...ns and sub-versions of the basic protocol into a historical context; see [[Internet Protocol version 4]] and [[Internet Protocol version 6]] for the details of design. Presented {{seealso|Internet Protocol version 4}}26 KB (4,062 words) - 15:00, 20 March 2024
- ...strative and technical controls on the DHCP server, whether it is DHCP for Internet Protocol version 4 or Internet Protocol version 6. The situation becomes much more complex wh13 KB (2,037 words) - 16:22, 30 March 2024
- Note that [[Internet Protocol version 4]] also exists. [[User:Chris Day|Chris Day]] 03:32, 9 June 2008 (CDT)22 KB (3,613 words) - 12:39, 21 February 2011
- TROJAN SPIRIT internally migrated from [[Asychronous Transfer Mode]] to [[Internet Protocol version 4]] communications with TROJAN SPIRIT II. To evolve the TROJAN SPIRIT II, the7 KB (976 words) - 13:59, 30 May 2024
- ...y be identified by a [[Domain Name Service]] (DNS) name, an address from [[Internet Protocol version 4]] or [[Internet Protocol version 6]], a combination of IP address and [[tra24 KB (3,628 words) - 21:04, 17 April 2014