Hubbry Logo
10BASE210BASE2Main
Open search
10BASE2
Community hub
10BASE2
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
10BASE2
10BASE2
10BASE2
View on Wikipedia
from Wikipedia
10BASE2 cable showing the BNC connector end.
10BASE2 cable with a BNC T-connector.
10BASE2 cable end terminator.
EAD outlet
Different types of T-connectors, with AAUIs (an AUI variant specific to Apple computers)

10BASE2 (also known as cheapernet,[1] thin Ethernet, thinnet, and thinwire) is a variant of Ethernet that uses thin coaxial cable terminated with BNC connectors to build a local area network. During the mid to late 1980s, this was the dominant 10 Mbit/s Ethernet standard.

The use of twisted pair networks competed with 10BASE2's use of a single coaxial cable. In 1988, Ethernet over twisted pair was introduced, running at the same speed of 10 Mbit/s. In 1995, the Fast Ethernet standard upgraded the speed to 100 Mbit/s, and no such speed improvement was ever made for thinnet. By 2001, prices for Fast Ethernet cards had fallen to under $50. By 2003, Wi-Fi networking equipment was widely available and affordable.

Due to the immense demand for high-speed networking, the low cost of Category 5 cable, and the popularity of 802.11 wireless networks, both 10BASE2 and 10BASE5 have become increasingly obsolete, though devices still exist in some locations.[2] As of 2011, IEEE 802.3 has deprecated this standard for new installations.[3]

Name origination

[edit]

The name 10BASE2 is derived from several characteristics of the physical medium. The 10 comes from the transmission speed of 10 Mbit/s. The BASE stands for baseband signaling, and the 2 for a maximum segment length approaching 200 m (the actual maximum length is 185 m).

Signal encoding

[edit]

10 Mbit/s Ethernet uses Manchester coding. A binary zero is indicated by a low-to-high transition in the middle of the bit period and a binary one is indicated by a high-to-low transition in the middle of the bit period. Manchester coding allows the clock to be recovered from the signal. However, the additional transitions associated with it double the signal bandwidth.

Network design

[edit]

10BASE2 coax cables have a maximum length of 185 metres (607 ft). The maximum practical number of nodes that can be connected to a 10BASE2 segment is limited to 30[4] with a minimum distance of 0.5 metres (20 in) between devices.[5] In a 10BASE2 network, each stretch of cable is connected to the transceiver (which is usually built into the network adaptor) using a BNC T-connector,[a] with one stretch connected to each female connector of the T. The T-connector must be plugged directly into the network adaptor with no cable in between.

As is the case with most other high-speed buses, Ethernet segments have to be terminated with a resistor at each end. Each end of the cable has a 50 Ω resistor attached. Typically this resistor is built into a male BNC and attached to the last device on the bus. This is most commonly connected directly to the T-connector on a workstation.[b] If termination is missing, or if there is a break in the cable, the AC signal on the bus is reflected, rather than dissipated, when it reaches the end. This reflected signal is indistinguishable from a collision, so no communication can take place.

Some terminators have a metallic chain attached to them for grounding purposes. The cable should be grounded only at one end. Grounding the terminators at both may produce a ground loop and can cause network outages or data corruption when swells of electricity traverse the coaxial cabling's outer shield.

When wiring a 10BASE2 network, special care has to be taken to ensure that cables are properly connected to all T-connectors. Bad contacts or shorts are especially difficult to diagnose. A failure at any point of the network cabling tends to prevent all communications. For this reason, 10BASE2 networks can be difficult to maintain and were often replaced by 10BASE-T networks, which (provided category 5 cable or better was used) also provided a good upgrade path to 100BASE-TX.

Comparisons to 10BASE-T

[edit]

10BASE2 networks cannot generally be extended without breaking service temporarily for existing users and the presence of many joints in the cable also makes them very vulnerable to accidental or malicious disruption. There were proprietary systems that claimed to avoid these problems (e.g. EAD sockets) but these never became widespread, possibly due to a lack of standardization. 10BASE-T can be extended by making a new connection to a hub. A fault in a one hub connection does not necessarily compromise other connections to the hub.

10BASE2 systems did have a number of advantages over 10BASE-T. No hub is required as with 10BASE-T, so the hardware cost was minimal, and wiring was particularly easy since only a single wire run is needed, which could be sourced from the nearest computer. These characteristics made 10BASE2 ideal for a small network of two or three machines, perhaps in a home where easily concealed wiring was an advantage. For a larger complex office network, the difficulties of tracing poor connections made it impractical. Unfortunately for 10BASE2, by the time multiple home computer networks became common, the format had already been practically superseded by 10BASE-T.

Comparisons to 10BASE5, use of AUI

[edit]

10BASE2 uses RG-58A/U cable or similar for a maximum segment length of 185 m as opposed to the thicker RG-8-like cable used in 10BASE5 networks with a maximum length of 500 m. The RG-58 type wire used by 10BASE2 was inexpensive, smaller and much more flexible than the specialized RG-8 variant. 10BASE2 can also use RG-59 cable.[6][7]

An Ethernet network interface controller (NIC) may include the 10BASE2 transceivers and thus directly provide a 10BASE2 BNC connector (that the T-connector plugs into), or it may offer an AUI connector that external transceivers (see Medium Attachment Unit) can connect to. These can be transceivers for 10BASE2, but also for 10BASE5 or 10BASE-T. Some NICs offer both BNC and AUI connectors, or other combinations including BNC and 10BASE-T. With multiple connections, only one connector is designed to be used at the same time.

See also

[edit]
Wikimedia Commons has media related to 10BASE2.

Notes

[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

10BASE2

View on Grokipedia
from Grokipedia
10BASE2 is a specification within the Ethernet standard for 10 Mbps operation using thin , typically with 50-ohm impedance, supporting connections via BNC T-connectors and allowing up to 30 stations per segment with a maximum length of 185 meters. Defined in Clause 10 of IEEE Std 802.3 and specifically standardized as IEEE 802.3a, it employs encoding, half-duplex CSMA/CD access method, and requires 50-ohm terminators at segment ends to prevent signal reflections. Also known as Thinnet, Cheapernet, or Thinwire, this variant was designed for cost-effective, simple daisy-chain installations compared to thicker alternatives. Introduced as an of early Ethernet to reduce and expense, 10BASE2 was approved by the IEEE on November 15, 1985, and published as IEEE Std 802.3a-1988, with ANSI approval in 1987 under the chaired by Alan Flatman. It addressed limitations of the original by using thinner, more flexible cable that could be directly attached to network interface cards via integrated transceivers or external Medium Attachment Units (MAUs), minimizing the need for bulky vampire taps and enabling easier routing in office environments. Key operational parameters include a maximum of 8.5 dB at 10 MHz, propagation delay of up to 950 ns per segment, and a slot time of 512 bit times (51.2 µs) for , ensuring reliable half-duplex communication within a supporting up to 1024 nodes across multiple segments. In practice, 10BASE2 networks could extend to 925 meters using up to five segments interconnected by four repeaters, with a minimum inter-station spacing of 0.5 meters to mitigate reflections, and incorporated features like jabber protection to isolate faulty transmitters. Though widely adopted in the late 1980s and early 1990s for its affordability—earning the "Cheapernet" moniker—it was declared obsolete for new designs in IEEE Std 802.3-2011 and fully deprecated by 2012, superseded by twisted-pair standards like 10BASE-T due to easier installation, better scalability, and reduced susceptibility to interference. Today, it remains a historical benchmark in networking evolution, illustrating early trade-offs in media access and physical layer design.

Overview

Naming and standards

The nomenclature "10BASE2" encapsulates the essential attributes of this Ethernet variant. The "10" signifies the nominal data signaling rate of 10 megabits per second, while "BASE" indicates signaling, where the entire bandwidth of the medium is used to transmit a single . The "2" approximates the maximum length of a at 200 meters, though the precise electrical limit is 185 meters to ensure signal integrity. 10BASE2 was standardized as part of the family of specifications for local area networks, specifically through the supplement IEEE 802.3a, approved on November 15, 1985, which added Clause 10 defining the for thin media. This amendment positioned 10BASE2 as a cost-effective evolution of the original thick Ethernet, maintaining full compatibility with the Ethernet II frame format developed by , , and DEC. At its core, 10BASE2 relies on the with (CSMA/CD) protocol, which governs shared-medium contention and collision resolution across the network, as outlined in the foundational standard.

Key specifications

10BASE2 operates at a data rate of 10 megabits per second (Mbps) in half-duplex mode, utilizing signaling for transmission. Each supports a maximum of 185 meters, using 50-ohm with specified attenuation limits to maintain , ensuring a maximum of 8.5 dB loss at 10 MHz over the full segment distance. The standard limits the number of stations to a maximum of 30 per segment to minimize collision probability and manage loading. Under the , a 10BASE2 network can incorporate up to five segments connected by four , with only three segments populated by nodes, resulting in a maximum total cable length of 925 meters across the . Transceivers for 10BASE2 are powered either through the Attachment Unit Interface (AUI) cable from the or via external power supplies, with typical consumption around 200 mA at 12 VDC.
SpecificationValueNotes
Data rate10 MbpsHalf-duplex,
Segment length185 m maxPer segment
Nodes per segment30 maxIncluding minimum 0.5 m spacing
Network extent925 m totalUp to 5 segments via 4 ()
Cable impedance50 ohms
Transceiver power~200 mA @ 12 VDCVia AUI or external supply

Cabling and connectors

10BASE2 networks utilize RG-58/U or RG-58A/U type 50-ohm coaxial cable as the physical medium, characterized by a flexible construction with an outer diameter of approximately 0.195 inches (5 mm) and double shielding to minimize electromagnetic interference. This cable exhibits a characteristic impedance of 50 Ω and a capacitance of roughly 100 pF/m, enabling reliable baseband transmission while supporting the standard's requirements for signal integrity over shared bus segments. The primary connectors for 10BASE2 are Bayonet Neill-Concelman (BNC) types, which provide a secure, twist-lock interface for attachments. Barrel connectors join cable segments end-to-end, while T-connectors (or tee connectors) allow individual nodes to tap into the bus without interrupting the main cable run. All BNC connectors and T-connectors must be fully insulated to prevent ground loops and short circuits, as specified in IEEE 802.3a. At each end of a cable segment, a 50-ohm terminator is required to absorb signals and prevent reflections, with one terminator grounded to earth at a single point to maintain electrical stability. Unlike thicker Ethernet variants such as , 10BASE2 integrates the transceiver (Media Access Unit or MAU) directly into the network interface card (NIC), featuring a built-in BNC for straightforward cable attachment without external transceivers. This design simplifies deployment but demands precise cable preparation to avoid performance issues. Proper cable preparation involves cutting the cable to the desired length, stripping the outer jacket to expose the braided and center conductor, and crimping BNC connectors using specialized tools to ensure a gas-tight connection that maintains the 50-ohm impedance. The must be folded back over the jacket before inserting the center pin into the connector, followed by crimping the to secure the assembly. Grounding is critical during installation; the cable's connects to ground at exactly one point—typically via the grounded terminator—to eliminate potential differences that could cause or damage. Improper crimping or ungrounded segments can lead to signal reflections, emphasizing the need for adherence to these procedures.

Signal encoding and transmission

10BASE2 employs Manchester encoding to represent bits on the physical medium, ensuring self-clocking for reliable and maintaining DC balance to prevent baseline wander. In this biphase encoding scheme, a logical "1" bit is represented by a high-to-low transition during the bit period, while a logical "0" bit is represented by a low-to-high transition, with each bit cell featuring a mid-bit transition for . The encoding operates at a 10 Mbps rate, corresponding to a 10 MHz signaling frequency where transitions occur at up to 10 MHz, though sustained patterns may exhibit a of 5 MHz. The for 10BASE2 is , where data is sent as a single modulated signal without . Access to the shared medium is managed through with (CSMA/CD), allowing stations to transmit when the medium is idle and to detect collisions by monitoring during transmission. This protocol ensures fair medium access while accommodating the shared bus nature of the segment. Signal levels on the are specified to maintain compatibility and minimize reflections, with a peak-to-peak voltage of approximately 2.0 for the transmitted . The signal voltage levels relative to range from -1.5 to +1.5 , corresponding to a peak-to-peak of 1 V to 3 V, while rise and fall times are controlled at 25 ns ± 5 ns to match the 50 Ω cable impedance and support over the maximum segment length. These parameters ensure adequate signal strength for detection at receiver thresholds while limiting . Upon detecting a collision, each involved station terminates transmission and issues a jam signal consisting of a minimum of 32 bits of a fixed , typically a continuous Manchester-encoded sequence, to propagate the collision notice across . This jam signal guarantees that all stations on the segment recognize the collision event, enabling them to invoke the algorithm for retransmission attempts and preserving the minimum frame size requirement for reliable detection.

Network topology and design

Topology rules

10BASE2 networks utilize a bus topology, consisting of a linear daisy-chain configuration where all nodes connect directly to a single shared coaxial cable segment, enabling collision detection across the medium as defined in the IEEE 802.3 standard. This shared-medium approach ensures that every transmission is visible to all attached devices, facilitating the carrier-sense multiple access with collision detection (CSMA/CD) protocol for medium arbitration. To extend the network beyond a single segment while adhering to propagation delay limits, IEEE 802.3 specifies a maximum of five segments interconnected by up to four repeaters, governed by the 5-4-3 rule: no more than five total segments, four repeaters, and only three of those segments may be populated with nodes to avoid excessive round-trip times that could impair collision detection. Each individual segment is limited to 30 nodes, with a minimum spacing of 0.5 meters between connections, to minimize signal attenuation and reduce the likelihood of excessive collisions in the shared domain. This node restriction, often referred to as the "pop count," corresponds to the maximum number of T-connectors (or "pops") per segment, preserving the coaxial cable's impedance and overall network performance. Proper termination is essential for in 10BASE2 bus ; each segment must have 50-ohm terminators installed at both physical ends to match the of the and absorb transmitted signals, thereby preventing reflections that could cause data errors or network instability. Failure to terminate correctly can lead to signal bounce, increasing error rates and potentially rendering the segment unusable. Nodes attach to the bus via BNC T-connectors, which branch the main cable without introducing significant discontinuities when spaced appropriately.

Installation and configuration

The installation of a 10BASE2 network begins with the assembly of coaxial cable segments using RG-58A/U or equivalent 50-ohm cable, ensuring the total length per segment does not exceed 185 meters to prevent signal attenuation. Cable lengths must be measured precisely, with a minimum separation of 0.5 meters between transceivers or T-connectors to avoid signal interference. At each network interface card (NIC) equipped with a BNC connector, a BNC T-connector is attached directly to the NIC's port, providing three connection points: one for the incoming cable, one for the outgoing cable, and one left open or capped if at the segment end. Segments are joined by inserting BNC barrel connectors (also known as couplers) between the ends of adjacent coaxial cables, which screw onto the BNC plugs crimped or soldered to the cable ends. At the physical ends of the bus topology, 50-ohm BNC terminators must be installed on the open leg of the end T-connectors to absorb signals and prevent reflections. Common issues during installation often stem from improper termination or cabling practices, leading to network instability. Mismatched terminators, such as using 75-ohm instead of 50-ohm resistors, can cause impedance discontinuities that generate signal reflections, resulting in data errors and reduced throughput. Unterminated cable ends produce "signal ghosts" or echoes, where reflected signals interfere with legitimate transmissions, manifesting as CRC errors or late collisions observable via network diagnostics. Excessive cable length beyond the 185-meter limit attenuates the 10 Mbps signal, causing and increased collision rates, particularly in multi-node setups. Damaged T-connectors, such as those with cracks, or poorly crimped BNC plugs can introduce or intermittent connectivity, exacerbating these problems. Testing a 10BASE2 installation involves verifying physical and electrical to ensure reliable operation. Cable testers are used to check continuity, , and shorts across the coaxial segments, confirming that all connections meet 50-ohm specifications without breaks. For fault localization, time-domain reflectometry (TDR) tools send pulses down the cable and measure reflections to identify unterminated ends, impedance mismatches, or breaks, providing distance estimates to the fault in meters. Visual inspection of LEDs on transceivers or NICs—typically green for power, yellow for activity, and red for collisions—offers initial confirmation of basic functionality, while enabling signal quality error (SQE) testing on compatible devices helps detect ongoing issues like excessive noise. Configuration tips emphasize maintaining a linear bus without loops, as any closed circuits would cause infinite signal circulation and constant collisions. Proper grounding of all components to a common reference is essential to minimize electromagnetic noise pickup, following industrial wiring guidelines to shield the braid effectively. For larger networks, segments can be isolated and extended using IEEE 802.3-compliant , which regenerate signals but must adhere to limits like the to avoid amplifying latency or collisions across the domain.

With 10BASE5

10BASE2 represents a refinement of the original Ethernet standard, utilizing thinner cabling to simplify deployment while maintaining the core 10 Mbps signaling shared by both variants. Specifically, 10BASE2 employs with an approximate outer diameter of 0.195 inches (5 mm), in contrast to the thicker RG-8 used in , which measures about 0.405 inches (10.3 mm). This reduction in cable thickness facilitates easier handling and installation, as the more flexible can be routed through walls and conduits with less effort than the rigid RG-8. However, the thinner cable introduces higher signal , limiting maximum segment lengths to 185 meters for 10BASE2 compared to 500 meters for . Attachment methods further highlight the design trade-offs between the two standards. In 10BASE5 networks, stations connect via external s attached through vampire taps that pierce the RG-8 cable's outer jacket, with the transceiver linking to the network interface card (NIC) over an Attachment Unit Interface (AUI) cable. This approach allows for precise tap placement but adds and potential points of due to the additional hardware. Conversely, 10BASE2 integrates the transceiver directly into the NIC, enabling straightforward connections using BNC T-connectors that pierce the RG-58 cable without external components. This direct attachment reduces setup time and eliminates the need for AUI cables, making 10BASE2 more accessible for smaller-scale implementations. From a cost and scalability perspective, 10BASE2 offers advantages in per-meter pricing and initial deployment for modest networks, as RG-58 cable is less expensive than RG-8, and the simplified connectors lower overall material costs. Yet, the shorter segment length in 10BASE2 necessitates more frequent use of repeaters or bridges to span larger areas, potentially increasing complexity and maintenance in expansive setups compared to the longer-reach 10BASE5. These characteristics positioned 10BASE2 as ideal for small office environments requiring up to 30 stations per 185 m segment (compared to up to 100 stations per 500 m segment for 10BASE5), while 10BASE5 suited backbone roles in larger enterprise networks where extended cable runs justified the added installation rigor.

With 10BASE-T

10BASE2 and 10BASE-T both provide Ethernet connectivity at 10 Mbps, but they differ fundamentally in their physical media and network architectures. 10BASE2 relies on a shared bus operating in half-duplex mode, where all devices connect to a single, continuous cable segment up to 185 meters long, enabling across the entire network. In contrast, 10BASE-T uses unshielded twisted-pair (UTP) Category 3 cabling in a point-to-point configuration, forming a star topology with individual segments limited to 100 meters, which supports dedicated links between each device and a central hub. The connector and infrastructure requirements further highlight these shifts. 10BASE2 employs BNC T-connectors for daisy-chaining devices directly onto the bus, creating a linear, shared medium without a central device. 10BASE-T, however, utilizes RJ-45 connectors for each twisted-pair link, connecting to a central multiport hub or that manages traffic and effectively segments the physical wiring, though the entire hub remains a single . This hub-centric approach simplifies cable management compared to the bus's rigid chaining. Reliability improvements in 10BASE-T stem from its , isolating faults to individual rather than the entire network. In 10BASE2, damage to the —such as a cut or improper termination—can cause signal reflections and disrupt all connected devices due to the shared bus nature. Conversely, 10BASE-T's star design confines failures to a single node or cable segment, allowing the rest of the to continue operating while the issue is isolated and repaired. This fault isolation enhances overall uptime in larger deployments. Deployment flexibility also favors 10BASE-T over 10BASE2's constraints. The bus in 10BASE2 limits expansion to linear segments with strict termination rules, making additions or reconfigurations labor-intensive and prone to errors like impedance mismatches. 10BASE-T's use of readily available UTP wiring and modular hub connections enables scalable, star-based growth, often leveraging existing infrastructure for easier installation and maintenance.

History and legacy

Development and adoption

10BASE2, also known as thin Ethernet or Cheapernet, emerged in the early as an amendment to the standard, aimed at overcoming the cumbersome installation and high costs associated with the original thick system. Developed by the working group, it utilized a thinner that was more flexible and easier to handle, allowing for simpler daisy-chaining of devices with BNC connectors. This amendment, designated IEEE 802.3a, was officially ratified in November 1985, providing a standardized specification for 10 Mbit/s transmission over segments up to 185 meters. The development of 10BASE2 was significantly driven by major networking vendors seeking to make Ethernet accessible for small business and departmental LANs. Companies like , founded by Ethernet co-inventor , and (DEC), one of the original Ethernet collaborators with and , played key roles in advocating for and implementing cost-reduced Ethernet variants. These efforts focused on enabling affordable connectivity for the growing market, where 10BASE5's rigid cabling and requirements proved impractical for office environments. Following ratification, 10BASE2 rapidly gained traction in the late as a practical solution for PC-based networks in offices and educational institutions, benefiting from the availability of inexpensive network interface cards (NICs) and pre-made cabling kits. Its popularity peaked in the early , becoming the dominant Ethernet cabling medium until the rise of twisted-pair alternatives, due to its balance of performance and low deployment costs compared to earlier standards. This widespread adoption facilitated the expansion of Ethernet into smaller-scale settings, democratizing local area networking beyond large enterprise installations.

Decline and modern relevance

The introduction of the 10BASE-T standard in 1990, defined by IEEE 802.3i, marked a pivotal shift away from 10BASE2 by utilizing unshielded twisted-pair (UTP) cabling in a star topology, which simplified installation and reduced maintenance challenges associated with coaxial bus networks. This change addressed key limitations of 10BASE2, such as the fragility of its shared medium where cable breaks could disrupt the entire segment. By the mid-1990s, the ratification of under IEEE 802.3u in 1995 further accelerated 10BASE2's decline, as it delivered 100 Mbps speeds over UTP or , making 10 Mbps systems inadequate for growing bandwidth demands in enterprise and commercial settings. UTP cabling proved cheaper to deploy and more reliable than alternatives, driving widespread adoption and rendering 10BASE2 largely obsolete in new installations by the early . 10BASE2 was declared obsolete for new designs in IEEE Std 802.3-2011 and fully deprecated in 2012. Although phased out from mainstream use, 10BASE2 persists in rare legacy applications, including certain industrial control systems and isolated older networks where compatibility issues necessitate adapters for integration with contemporary switches. In modern contexts, 10BASE2's primary relevance lies in its educational role, providing insights into Ethernet's foundational principles, the transition from bus to star topologies, and the progression from shared-media to switched networks; it is frequently emulated in simulations for academic and purposes. It also maintains niche relevance in the retro computing community, where enthusiasts discover and share 10BASE2 BNC connectors and NICs for vintage systems like the NEC PC-98, as evidenced by recent online discussions in late 2025. No substantive developments or standards updates for 10BASE2 have emerged since the , underscoring its status as a historical artifact in networking evolution.

References

  1. https://www.my-wire.de/schnittstellenbeschreibung/ethernet.pdf
  2. https://www.firewall.cx/networking/network-cabling/network-cabling-10base-t.html
  3. https://www.telecomabc.com/numbers/10base2.html
  4. https://telecomtraining.net/kb/what-is-thinnet--t2964-4.html
  5. https://grouper.ieee.org/groups/802/misc-docs/GlobeCom2009/IEEE_802d3_Law.pdf
  6. https://buy.advantech.com/CMS/CmsDetail.aspx?CMSID=0BB4321F-A05D-4514-886A-0883EDC37EAA&CMSType=White_Papers
  7. http://csc.columbusstate.edu/summers/notes/cs557/3mc/Ethernet/tsld011.htm
  8. https://standards.ieee.org/ieee/802.3/10422/
  9. https://standards.ieee.org/beyond-standards/ethernet-50th-anniversary/
  10. https://ieeexplore.ieee.org/document/26520
  11. https://standards.ieee.org/ieee/802.3/1057/
  12. https://www.ieee802.org/3/da/public/0923/SPMD_Potterf_UnitLoadConcept_2023-09-07.pdf
  13. https://www.vskills.in/certification/certified-basic-network-support-professional-10base2-and-10base5
  14. https://docs.rs-online.com/7266/0900766b8002b26a.pdf
  15. https://www.idc-online.com/technical_references/pdfs/data_communications/RG_58.pdf
  16. https://techbooksforfree.com/intro_to_data_com/page119.html
  17. https://cdn.lantronix.com/wp-content/uploads/pdf/33339.C_user-guide.pdf
  18. https://documents.mrosupply.com/product_documents/57/21/5721428/1785-in058_-en-p_cI8YvAU.pdf
  19. https://www.stonewallcable.com/network/thinnet-10base2
  20. https://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html
  21. https://www.advantech.com/ru-ru/resources/white-papers/0bb4321f-a05d-4514-886a-0883edc37eaa
  22. https://www.awcwire.com/rg-catalog/rg58-coax-cable
  23. https://www.awcwire.com/rg-catalog/rg8-coax-cable
  24. https://objects.eanixter.com/PD344399.PDF
  25. https://literature.rockwellautomation.com/idc/groups/literature/documents/in/1785-in057_-en-p.pdf
  26. http://zaielacademic.net/networking/ethernet.htm
  27. https://www.farnell.com/datasheets/28379.pdf
  28. https://ieeexplore.ieee.org/document/7508548
  29. https://us.profinet.com/switched-ethernet-networks-profinet-determinism/
  30. https://standards.ieee.org/ieee/802.3i/1068/
  31. https://www.nakivo.com/blog/types-of-network-topology-explained/
  32. https://www.sciencedirect.com/topics/mathematics/star-topology
  33. https://www.cs.csustan.edu/~john/Classes/Previous_Semesters/CS3000_Communication_Networks/2008_01_Winter/Notes/chap10.html
  34. https://www.techtarget.com/searchnetworking/feature/Understanding-the-evolution-of-Ethernet
  35. https://www.globalspec.com/reference/70448/203279/phase-two-xerox-and-dec
  36. https://www.iol.unh.edu/sites/default/files/knowledgebase/ethernet/ethernet_evolution.pdf
  37. https://www.historyofinformation.com/detail.php?id=1245
  38. https://ethw.org/Milestones:Ethernet_Local_Area_Network_%28LAN%29%2C_1973-1985
  39. https://ieeemilestones.ethw.org/Milestone-Proposal:Manchester_Code
  40. https://standards.ieee.org/ieee/802.3u/1079/
  41. https://www.extremenetworks.com/resources/blogs/wired-for-success-how-did-ethernet-become-the-backbone-of-modern-connectivity
  42. https://simcona.com/blog/data-communication-cable-types
  43. https://intronetworks.cs.luc.edu/current1/mob2/ethernet.html
  44. https://x.com/shingo_aoi20/status/1994653931746799871
  45. https://www.reddit.com/r/vintagecomputing/comments/191fzn5/help_identify_dec_lan_card/
Add your contribution
Related Hubs
User Avatar
No comments yet.