DOCSLIB.ORG

Ethernet Basics Ethernet Basics

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

2016-09-24 Ethernet Basics based on Chapter 4 of CompTIA Network+ Exam Guide, 4th ed., Mike Meyers Ethernet Basics • History • Ethernet Frames • CSMA/CD • Obsolete versions • 10Mbps versions • Segments • Spanning Tree Protocol 1 2016-09-24 Ethernet – Early History • 1970: ALOHAnet, first wireless packet-switched network - Norman Abramson, Univ. of Hawaii - Basis for Ethernet’s CSMA/CD protocol - 1972: first external network connected to ARPANET • 1973: Ethernet prototype developed at Xerox PARC - (Palo Alto Research Center) - 2.94 Mbps initially • 1976: "Ethernet: Distributed Packet Switching for Local Computer Networks" published in Communications of the ACM. - Bob Metcalfe and David Boggs - sometimes considered “the beginning of Ethernet” Ethernet goes Mainstream • 1979: DEC, Intel, Xerox collaborate on a commercial Ethernet specification - Ethernet II, a.k.a. “DIX” Ethernet - (Digital Equipment Corporation) • 1983: IEEE 802.3 specification formally approved - Differs from Ethernet II in the interpretation of the third header field • 1987: alternatives to coaxial cables - IEEE 802.3d: FOIRL, Fiber Optic Inter-Repeater Link - IEEE 802.3e: 1 Mbps over Twisted Pair wires (whoopee!) • 1990: Twisted-Pair wiring takes over - IEEE 802.3i: 10 Mbps over Twisted-Pair – 10Base-TX, 10Base-T4 2 2016-09-24 the Future is Now (next chapter) (and Now is so Yesteryear…) 1995 – Now: speed and cabling improvements • 1995: 100Mbps varieties • 1999: 1Gbps on twisted-pair • 2003-2006: 10Gbps on optical fiber and UTP • 2010: 40Gbps, 100Gbps (802.3ba) - optical fiber or twinaxial cable - point-to-point physical topology; for backbones • 2016, September: 2.5GBase-T, 5GBase-T ? - who knows? What Is Ethernet? • Protocols, standards for Local Area Networks » Ethernet II, IEEE 802.3 • Specifies Physical-layer components - Cabling, signaling properties, etc. - Numerous variations • Specifies Datalink-layer protocols - Media Access Control (MAC) – lower Datalink sublayer, interfaces to the Physical layer » IEEE 802.3 - Logical Link Control (LLC) – upper Datalink sublayer, common interface to the Network layer » IEEE 802.2 3 2016-09-24 Ethernet (802.3) relation to OSI 802.2 802.3 - The Early Variations 4 2016-09-24 Ethernet and Cabling – the Coaxial Era • 10Base5 (standard IEEE 802.3, 1983) • 10Base2 (standard IEEE 802.3a, 1985) • Physical bus topology required a logical bus topology • CSMA/CD protocol used in the Collision Domain 10Base5 • 1983: IEEE 802.3 - The original form • “Thick coax” cable - RG-8/U or RG-11 specified - half-inch diameter • “Vampire tap” connection punctures insulation to make electrical connections • “10Base5”: - 10 Mbps - Baseband signaling - 500 meters maximum length 5 2016-09-24 10Base2 • 1985: IEEE 802.3a - Physical update for cheaper cabling • “Thin coax” cable - RG-58a/u - 5mm diameter - electrically compatible with thick coax • BNC connectors allow easy disconnection, reconnection • “10Base2”: - 10 Mbps - Baseband signaling - 200 meters maximum length (actually 185m) Out of the Coaxial Era - Twisted Pair takes over • 10Base-T (IEEE 802.3i, 1990) - Twisted-Pair cables » Cheaper, easier to use than coax - 100m maximum length • 100Base-T (IEEE 802.3u, 1995) - “Fast Ethernet” - 100Base-T4: Cat3, 4 pairs used - 100Base-TX: Cat5, 2 pairs used • Full Duplex (IEEE 802.3x, 1997) - Applies to 100BaseT and later • Physical star, but Ethernet is still a bus-oriented protocol 6 2016-09-24 Ethernet on Optical Fiber • Alternate, longer-distance media extend Ethernet's reach • 10Base-FL (IEEE 802.3j, 1993) - 10Mbps, multimode optical fiber - 2000m maximum length - Not common • 100Base-FX (IEEE 802.3u, 1995) - “Fast Ethernet” - 100Base-FX: multimode optical fiber • Point-to-point physical topology Specialized Media • Twinax - heavily shielded cable - used for short, high- speed applications • Backplane - intra-chassis connections - high speed – 40 Gbps 7 2016-09-24 Common to All Variations Frame format, Behavior the Ethernet frame format Preamble: Dest. Src. MAC Type / Payload Padding? FCS IFG: 10101010 MAC length 96 bit- .. 46..0 0..1500 4 times 10101011 6 octets 6 octets 2 octets octets octets octets • Ethernet II header contains: • Physical frame starts with an - 6 octets: destination MAC address 8-octet preamble consisting of - 6 octets: source MAC address 1010…10101011 - 2 octets: payload-type field - 10Mbs versions only • 802.3 differs in the third field: • Maximum frame length is 1518 - payload length instead of type octets • 0-1500 octets: Payload, - including the FCS supplied by a higher protocol layer - excluding the preamble - Could be 802.2 - could be layer 3 • Minimum length is 64 octets - 46-0 octets: Padding w/ 0-bytes to insure - assures collision detection minimum frame length • Physical frame is followed by an IFG, • 4 octets: Ethernet footer contains InterFrame Gap FCS (Frame Check Sequence) - no signal transitions - a CRC checksum - 96 bit-times in duration 8 2016-09-24 Ethernet Addresses • Also called MAC addresses, • Written as 6 pairs of hardware or physical hexadecimal digits addresses, or Layer 2 - separated by colon or dash addresses • Examples: • 6 octets long - 00:1a:6b:4e:3f:1b - an “octet” refers to a » Linux “byte” and is used in - 40-A8-F0-A2-DD-CE networking » Windows • First three octets refer to the manufacturer or • Broadcast address: vendor ff:ff:ff:ff:ff:ff - As a destination, this • Last three octets must be means “send to all unique within a mfr/vendor available nodes” wireshark activity • start wireshark • Display filter eth.type - Any types other than 0x0800? - What layer-3 protocol(s)? • Display filter: eth.len - Observe layer-2 protocol(s) - What payload(s)? • Display filter: eth.addr==<your MAC address> - What traffic is coming from, going to your machine? 9 2016-09-24 Ethernet II versus 802.3 with 802.2 Ethernet II 802.3 type > 1500 length < 1500 • left: an Ethernet II frame specifies a type, and leaves the next layer to find the data’s end - all types are values greater than 1500 (0x0600) » viz., IP is type 0x0800 • right: an 802.3 frame specifies the payload length, and includes 802.2 headers - length is always 1500 or less Ethernet II frame 2016- 09-24 10 2016-09-24 802.3 frame, with 802.2 headers • This frame shows 802.3 and 802.2 headers. • This also shows the FCS (checksum) field, which Wireshark thinks is incorrect. 2016- 09-24 So, how does the NIC determine where a frame ends? • Ethernet II frame doesn’t specify its overall length • 10Base5, 10Base2 standards: - NIC detects end of signal - absence of current • 10Base-T: - NIC listens for a special TP_IDL signal on the wire, followed by InterFrame Gap • 100Base-T, GigE, 10GigE: - 4B/5B encoded “start-of-frame signals” and “end-of- frame signals” replace preamble and TP_IDL 11 2016-09-24 10BaseT: The FCS and TP_IDL signal CSMA / CD • Carrier-Sense Multiple Access with Collision Detection • Multiple Access: more than one node can transmit on the shared medium • Carrier-Sense: a NIC that wants to transmit must first listen for an active transmission - if it doesn’t hear an idle “carrier signal” it backs off and waits before trying again • Collision Detection: if a NIC hears interference while it is transmitting, it knows that a collision with another transmission has occurred • Colliding nodes attempt to re-transmit using an “Exponential Backoff” approach 12 2016-09-24 Collisions and Exponential Backoff • When a NIC detects a collision, it: - transmits at least 64 bytes, then stops - waits a fixed amount of time - repeats the CSMA/CD attempt • If a second collision occurs, it waits twice as long • If a third collision, wait twice as long again • This gives exponentially-increasing wait times - After 10 collisions the wait remains constant - After 16 collisions, the attempt is abandoned What Exponential Backoff looks like • X-axis: number of collisions • Y-axis: relative waiting time 13 2016-09-24 Segments and Collision Domains • All the nodes sharing a cable form a segment • The segment defines a collision domain - Frames on a segment can collide with each other… These two segments form separate collision domains Extended Collision Domains • A repeater, such as this one, connects two segments into a single collision domain - Frames on either segment can collide with others. • Hubs (a.k.a. multi-port repeaters) do the same thing, with multiple segments • Switches don't – they keep collision domains separate 14 2016-09-24 (other definitions of “segment”) • "Segment" may have other meanings… • Related meanings in Ethernet: - "Segment" and "Collision Domain" are sometimes used interchangeably. - A "Segment" can refer to a "Broadcast Domain". • Unrelated meanings in the TCP/IP world: - "Segment" refers to a "protocol data unit" at the Transport layer of the OSI or TCP/IP stack. » versus "frame" which refers to a protocol data unit at the Datalink and Physical layers – viz., Ethernet frame - "Segment" can mean an IP subnetwork. Hubs and Extended Collision Domains • A repeater (or hub) joins two (or more) segments • These segments share a common collision domain - The hub will broadcast all frames, as if the two segments were one 15 2016-09-24 The (Obsolete) 5-4-3 Rule • The “5-4-3” rule (or “5-4-3-2-1” rule) - ≤ 5 segments (cables) - connected by ≤ 4 repeaters - ≤ 3 active segments (i.e., with transmitting nodes) - 2 passive segments • Single Collision Domain • (Not important in switched networks…) 2016- 09-24 how big can a collision domain be? • 5-4-3 rule limits amount of cable in use • How far apart could two computers be, using 10Base5
Recommended publications
  • Mikrodenetleyicili Endüstriyel Seri Protokol Çözümleyici Sisteminin Programi

    Mikrodenetleyicili Endüstriyel Seri Protokol Çözümleyici Sisteminin Programi

    YILDIZ TEKNİK ÜNİVERSİTESİ FEN BİLİMLERİ ENSTİTÜSÜ MİKRODENETLEYİCİLİ ENDÜSTRİYEL SERİ PROTOKOL ÇÖZÜMLEYİCİ SİSTEMİNİN PROGRAMI Elektronik ve Haberleşme Müh. Kemal GÜNSAY FBE Elektronik ve Haberleşme Anabilim Dalı Elektronik Programında Hazırlanan YÜKSEK LİSANS TEZİ Tez Danışmanı : Yrd. Doç. Dr. Tuncay UZUN (YTÜ) İSTANBUL, 2009 YILDIZ TEKNİK ÜNİVERSİTESİ FEN BİLİMLERİ ENSTİTÜSÜ MİKRODENETLEYİCİLİ ENDÜSTRİYEL SERİ PROTOKOL ÇÖZÜMLEYİCİ SİSTEMİNİN PROGRAMI Elektronik ve Haberleşme Müh. Kemal GÜNSAY FBE Elektronik ve Haberleşme Anabilim Dalı Elektronik Programında Hazırlanan YÜKSEK LİSANS TEZİ Tez Danışmanı : Yrd. Doç. Dr. Tuncay UZUN (YTÜ) İSTANBUL, 2009 İÇİNDEKİLER Sayfa KISALTMA LİSTESİ ................................................................................................................ v ŞEKİL LİSTESİ ...................................................................................................................... viii ÇİZELGE LİSTESİ .................................................................................................................... x ÖNSÖZ ...................................................................................................................................... xi ÖZET ........................................................................................................................................ xii ABSTRACT ............................................................................................................................ xiii 1. GİRİŞ ......................................................................................................................
  • Gigabit Ethernet - CH 3 - Ethernet, Fast Ethernet, and Gigabit Ethern

    Gigabit Ethernet - CH 3 - Ethernet, Fast Ethernet, and Gigabit Ethern

    Switched, Fast, and Gigabit Ethernet - CH 3 - Ethernet, Fast Ethernet, and Gigabit Ethern.. Page 1 of 36 [Figures are not included in this sample chapter] Switched, Fast, and Gigabit Ethernet - 3 - Ethernet, Fast Ethernet, and Gigabit Ethernet Standards This chapter discusses the theory and standards of the three versions of Ethernet around today: regular 10Mbps Ethernet, 100Mbps Fast Ethernet, and 1000Mbps Gigabit Ethernet. The goal of this chapter is to educate you as a LAN manager or IT professional about essential differences between shared 10Mbps Ethernet and these newer technologies. This chapter focuses on aspects of Fast Ethernet and Gigabit Ethernet that are relevant to you and doesn’t get into too much technical detail. Read this chapter and the following two (Chapter 4, "Layer 2 Ethernet Switching," and Chapter 5, "VLANs and Layer 3 Switching") together. This chapter focuses on the different Ethernet MAC and PHY standards, as well as repeaters, also known as hubs. Chapter 4 examines Ethernet bridging, also known as Layer 2 switching. Chapter 5 discusses VLANs, some basics of routing, and Layer 3 switching. These three chapters serve as a precursor to the second half of this book, namely the hands-on implementation in Chapters 8 through 12. After you understand the key differences between yesterday’s shared Ethernet and today’s Switched, Fast, and Gigabit Ethernet, evaluating products and building a network with these products should be relatively straightforward. The chapter is split into seven sections: l "Ethernet and the OSI Reference Model" discusses the OSI Reference Model and how Ethernet relates to the physical (PHY) and Media Access Control (MAC) layers of the OSI model.
  • Data Link Layer

    Data Link Layer

    Data link layer Goals: ❒ Principles behind data link layer services ❍ Error detection, correction ❍ Sharing a broadcast channel: Multiple access ❍ Link layer addressing ❍ Reliable data transfer, flow control: Done! ❒ Example link layer technology: Ethernet Link layer services Framing and link access ❍ Encapsulate datagram: Frame adds header, trailer ❍ Channel access – if shared medium ❍ Frame headers use ‘physical addresses’ = “MAC” to identify source and destination • Different from IP address! Reliable delivery (between adjacent nodes) ❍ Seldom used on low bit error links (fiber optic, co-axial cable and some twisted pairs) ❍ Sometimes used on high error rate links (e.g., wireless links) Link layer services (2.) Flow Control ❍ Pacing between sending and receiving nodes Error Detection ❍ Errors are caused by signal attenuation and noise. ❍ Receiver detects presence of errors signals sender for retrans. or drops frame Error Correction ❍ Receiver identifies and corrects bit error(s) without resorting to retransmission Half-duplex and full-duplex ❍ With half duplex, nodes at both ends of link can transmit, but not at same time Multiple access links / protocols Two types of “links”: ❒ Point-to-point ❍ PPP for dial-up access ❍ Point-to-point link between Ethernet switch and host ❒ Broadcast (shared wire or medium) ❍ Traditional Ethernet ❍ Upstream HFC ❍ 802.11 wireless LAN MAC protocols: Three broad classes ❒ Channel Partitioning ❍ Divide channel into smaller “pieces” (time slots, frequency) ❍ Allocate piece to node for exclusive use ❒ Random
  • MAC Protocols for IEEE 802.11Ax: Avoiding Collisions on Dense Networks Rafael A

    MAC Protocols for IEEE 802.11Ax: Avoiding Collisions on Dense Networks Rafael A

    MAC Protocols for IEEE 802.11ax: Avoiding Collisions on Dense Networks Rafael A. da Silva1 and Michele Nogueira1;2 1Department of Informatics, Federal University of Parana,´ Curitiba, PR, Brazil 2Electrical and Computer Engineering, Carnegie Mellon University, Pittsburgh, PA, USA E-mails: [email protected] and [email protected] Wireless networks have become the main form of Internet access. Statistics show that the global mobile Internet penetration should exceed 70% until 2019. Wi-Fi is an important player in this change. Founded on IEEE 802.11, this technology has a crucial impact in how we share broadband access both in domestic and corporate networks. However, recent works have indicated performance issues in Wi-Fi networks, mainly when they have been deployed without planning and under high user density. Hence, different collision avoidance techniques and Medium Access Control protocols have been designed in order to improve Wi-Fi performance. Analyzing the collision problem, this work strengthens the claims found in the literature about the low Wi-Fi performance under dense scenarios. Then, in particular, this article overviews the MAC protocols used in the IEEE 802.11 standard and discusses solutions to mitigate collisions. Finally, it contributes presenting future trends arXiv:1611.06609v1 [cs.NI] 20 Nov 2016 in MAC protocols. This assists in foreseeing expected improvements for the next generation of Wi-Fi devices. I. INTRODUCTION Statistics show that wireless networks have become the main form of Internet access with an expected global mobile Internet penetration exceeding 70% until 2019 [1]. Wi-Fi Notice: This work has been submitted to the IEEE for possible publication.
  • Understanding Linux Internetworking

    Understanding Linux Internetworking

    White Paper by David Davis, ActualTech Media Understanding Linux Internetworking In this Paper Introduction Layer 2 vs. Layer 3 Internetworking................ 2 The Internet: the largest internetwork ever created. In fact, the Layer 2 Internetworking on term Internet (with a capital I) is just a shortened version of the Linux Systems ............................................... 3 term internetwork, which means multiple networks connected Bridging ......................................................... 3 together. Most companies create some form of internetwork when they connect their local-area network (LAN) to a wide area Spanning Tree ............................................... 4 network (WAN). For IP packets to be delivered from one Layer 3 Internetworking View on network to another network, IP routing is used — typically in Linux Systems ............................................... 5 conjunction with dynamic routing protocols such as OSPF or BGP. You c an e as i l y use Linux as an internetworking device and Neighbor Table .............................................. 5 connect hosts together on local networks and connect local IP Routing ..................................................... 6 networks together and to the Internet. Virtual LANs (VLANs) ..................................... 7 Here’s what you’ll learn in this paper: Overlay Networks with VXLAN ....................... 9 • The differences between layer 2 and layer 3 internetworking In Summary ................................................. 10 • How to configure IP routing and bridging in Linux Appendix A: The Basics of TCP/IP Addresses ....................................... 11 • How to configure advanced Linux internetworking, such as VLANs, VXLAN, and network packet filtering Appendix B: The OSI Model......................... 12 To create an internetwork, you need to understand layer 2 and layer 3 internetworking, MAC addresses, bridging, routing, ACLs, VLANs, and VXLAN. We’ve got a lot to cover, so let’s get started! Understanding Linux Internetworking 1 Layer 2 vs.
  • Migrating Backoff to the Frequency Domain

    Migrating Backoff to the Frequency Domain

    No Time to Countdown: Migrating Backoff to the Frequency Domain Souvik Sen Romit Roy Choudhury Srihari Nelakuditi Duke University Duke University University of South Carolina Durham, NC, USA Durham, NC, USA Columbia, SC, USA [email protected] [email protected] [email protected] ABSTRACT 1. INTRODUCTION Conventional WiFi networks perform channel contention in Access control strategies are designed to arbitrate how mul- time domain. This is known to be wasteful because the chan- tiple entities access a shared resource. Several distributed nel is forced to remain idle while all contending nodes are protocols embrace randomization to achieve arbitration. In backing off for multiple time slots. This paper proposes to WiFi networks, for example, each participating node picks a break away from convention and recreate the backing off op- random number from a specified range and begins counting eration in the frequency domain. Our basic idea leverages the down. The node that finishes first, say N1, wins channel con- observation that OFDM subcarriers can be treated as integer tention and begins transmission. The other nodes freeze their numbers. Thus, instead of picking a random backoff duration countdown temporarily, and revive it only after N1’s trans- in time, a contending node can signal on a randomly cho- mission is complete. Since every node counts down at the sen subcarrier. By employing a second antenna to listen to same pace, this scheme produces an implicit ordering among all the subcarriers, each node can determine whether its cho- nodes. Put differently, the node that picks the smallest ran- sen integer (or subcarrier) is the smallest among all others.
  • Collision Detection

    Collision Detection

    Computer Networking Michaelmas/Lent Term M/W/F 11:00-12:00 LT1 in Gates Building Slide Set 3 Evangelia Kalyvianaki [email protected] 2017-2018 1 Topic 3: The Data Link Layer Our goals: • understand principles behind data link layer services: (these are methods & mechanisms in your networking toolbox) – error detection, correction – sharing a broadcast channel: multiple access – link layer addressing – reliable data transfer, flow control • instantiation and implementation of various link layer technologies – Wired Ethernet (aka 802.3) – Wireless Ethernet (aka 802.11 WiFi) • Algorithms – Binary Exponential Backoff – Spanning Tree 2 Link Layer: Introduction Some terminology: • hosts and routers are nodes • communication channels that connect adjacent nodes along communication path are links – wired links – wireless links – LANs • layer-2 packet is a frame, encapsulates datagram data-link layer has responsibility of transferring datagram from one node to adjacent node over a link 3 Link Layer (Channel) Services • framing, physical addressing: – encapsulate datagram into frame, adding header, trailer – channel access if shared medium – “MAC” addresses used in frame headers to identify source, dest • different from IP address! • reliable delivery between adjacent nodes – we see some of this again in the Transport Topic – seldom used on low bit-error link (fiber, some twisted pair) – wireless links: high error rates 4 Link Layer (Channel) Services - 2 • flow control: – pacing between adjacent sending and receiving nodes • error control: – error
  • Fact Sheet: Single-Pair Ethernet Trade Article

    Fact Sheet: Single-Pair Ethernet Trade Article

    Fact sheet Single Pair Ethernet Matthias Fritsche – product manager device connectivity & Jonas Diekmann – technical editor HARTING Technology group – October 2016– November 2016 Wireless technology and optical cable have already been often heralded as the future transmission technology. However, simple twisted pair cable based on plain old copper, often pronounced dead, is the most common transmission medium. Simple, robust, and perhaps with 100GBASE T1 soon to be also incredibly fast. From the beginnings of Ethernet in the 1970s, then via diverse multi-pair Ethernet developments with multiple parallel transmission paths, now apparently we are taking a step back. Back to single twisted-pair. With a new protocol and new PHYs transmission rates of up to 10 Gbit/s and PoDL capacities of up to 60 W are no longer a problem. Ultimately one pair is enough. When the team surrounding David Boggs and Robert Metcalf in the 1970s developed Ethernet at the Xerox Palo Alto Research Center (PARC), no one could foresee that this transmission method would develop so dynamically and dominate data transmission worldwide to this day. The original 10BASE5 Ethernet still used coax cable as the common medium. Today, next to wireless and optical cables, twisted-pair cable, often pronounced dead, is the most frequently used transmission medium. Starting in 1990 with 10BASE-T, the data transmission rate of the IEEE standards increased by a factor of 10 approximately every 5 years over 100BASE-TX and 1000BASE-T up to 10GBASE-T. This series could not be continued for the jump to 100GBASE-T, instead however four new IEEE standards were finalized in 2016.
  • Ethernet Coax Transceiver Interface 1CY7B8392 Functional Description

    Ethernet Coax Transceiver Interface 1CY7B8392 Functional Description

    CY7B8392 Ethernet Coax Transceiver Interface 1CY7B8392 Functional Description Features The CY7B8392 is a low power coaxial transceiver for Ethernet 10BASE5 and 10BASE2 applications. The device contains all • Compliant with IEEE802.3 10BASE5 and 10BASE2 the circuits required to perform transmit, receive, collision de- • Pin compatible with the popular 8392 tection, heartbeat generation, jabber timer and attachment • Internal squelch circuit to eliminate input noise unit interface (AUI) functions. In addition, the CY7B8392 fea- • Hybrid mode collision detect for extended distance tures an advanced hybrid collision detection. • Automatic AUI port isolation when coaxial connector is The transmitter output is connected directly to a double termi- not present nated 50Ω cable. • Low power BiCMOS design The CY7B8392 is fabricated with an advanced low power • 16-Pin DIP or 28-Pin PLCC BiCMOS process. Typical standby current during idle is 25 mA. Logic Block Diagram RX+ HIGH PASS AUI CCM EQUALIZATION DRIVER RX– RXI LOW PASS FILTER CD+ AUI GND – CARRIER DRIVER LOW PASS SENSE CD– FILTER + TX+ TX– – COLLISION CDS LOW PASS + RCV FILTER TXO WAVEFORM + DC/AC SHAPING SQUELCH – VEE 10 MHz CLK WATCHDOG JABBER RESET OSC TIMER26 ms TIMER0.4 sec RR+ REFERENCE 1K CIRCUIT TRANSMIT RECEIVE RR– STATE STATE MACHINE MACHINE HBE 8392–1 Pin Configurations PLCC DIP Top View Top View – RX+ CD CD+ CDS NC RXI TXO CD+ 1 16 CDS 432 1 28 2726 CD– 2 15 TXO VEE (NC) 5 25 VEE (NC) RX+ 3 14 RXI VEE (NC) 6 24 VEE V VEE 7 23 VEE (NC) EE 4 13 VEE 7B8392 7B8392 VEE 8 22 VEE (NC) VEE 5 12 RR– VEE (NC) 9 21 VEE RX– 6 11 RR+ VEE (NC) 10 20 VEE (NC) TX+ 7 10 GND VEE (NC) 11 121314 15 16 1718 RR– TX– 8 9 HBE – – TX+ TX RX 8392–3 RR+ HBE GND GND 8392–2 Cypress Semiconductor Corporation • 3901 North First Street • San Jose • CA 95134 • 408-943-2600 Document #: 38-02016 Rev.
  • Automotive Ethernet Kirsten Matheus , Thomas Königseder Frontmatter More Information

    Automotive Ethernet Kirsten Matheus , Thomas Königseder Frontmatter More Information

    Cambridge University Press 978-1-108-84195-5 — Automotive Ethernet Kirsten Matheus , Thomas Königseder Frontmatter More Information Automotive Ethernet Third Edition Learn about the latest developments in Automotive Ethernet technology and imple- mentation with this fully revised third edition. Including 20% new material and greater technical depth, coverage is expanded to include Detailed explanations of the new PHY technologies 10BASE-T1S (including multi- drop) and 2.5, 5, and 10GBASE-T1 Discussion of EMC interference models Descriptions of the new TSN standards for automotive use More on security concepts An overview of power saving possibilities with Automotive Ethernet Explanation of functional safety in the context of Automotive Ethernet An overview of test strategies The main lessons learned Industry pioneers share the technical and non-technical decisions that have led to the success of Automotive Ethernet, covering everything from electromagnetic require- ments and physical layer technologies, QoS, and the use of VLANs, IP, and service discovery, to network architecture and testing. The guide for engineers, technical managers, and researchers designing components for in-car electronics, and those interested in the strategy of introducing a new technology. Kirsten Matheus is a communications engineer who is responsible for the in-vehicle networking strategy at BMW and who has established Ethernet-based communication as a standard technology within the automotive industry. She has previously worked for Volkswagen, NXP, and Ericsson. In 2019 she was awarded the IEEE-SA Standards Medallion “For vision, leadership, and contributions to developing auto- motive Ethernet networking.” Thomas Königseder is CTO at Technica Engineering, supporting the smooth introduc- tion of Ethernet-based systems for automotive customers.
  • The Essential Guide to Audio Over IP for Broadcasters 2 5

    The Essential Guide to Audio Over IP for Broadcasters 2 5

    The Essential Guide To Audio OverIP FOR BROADCASTERS Powerful Performance | Powerful Control | Powerful Savings i 1. Why IP for Broadcast Audio? Reasons to Migrate to Audio over IP ..........................................................................................................8 1. Flexibility ..................................................................................................................................................................................8 2. Cost ...........................................................................................................................................................................................8 3. Scalability ................................................................................................................................................................................9 4. Reliability (yes really!) .........................................................................................................................................................9 5. Availability ..............................................................................................................................................................................9 6. Control and Monitoring .....................................................................................................................................................9 7. Network Consolidation ......................................................................................................................................................9
  • Linux Networking Cookbook.Pdf

    Linux Networking Cookbook.Pdf

    Linux Networking Cookbook ™ Carla Schroder Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Linux Networking Cookbook™ by Carla Schroder Copyright © 2008 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Indexer: John Bickelhaupt Production Editor: Sumita Mukherji Cover Designer: Karen Montgomery Copyeditor: Derek Di Matteo Interior Designer: David Futato Proofreader: Sumita Mukherji Illustrator: Jessamyn Read Printing History: November 2007: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. The Cookbook series designations, Linux Networking Cookbook, the image of a female blacksmith, and related trade dress are trademarks of O’Reilly Media, Inc. Java™ is a trademark of Sun Microsystems, Inc. .NET is a registered trademark of Microsoft Corporation. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.