![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Are there any official logos for the various versions and types of ethernet, like there are for Firewire and USB? Or did nobody think of things like that in the 1970's? —Preceding unsigned comment added by Bizzybody ( talk • contribs) 07:05, August 27, 2007 (UTC)
The ACM classics page appears to no longer list the original ethernet paper. —Preceding unsigned comment added by 130.217.250.13 ( talk) 01:21, 25 September 2007 (UTC)
The first part of this section "CSMA/CD shared medium Ethernet" cofuses me. It begins "Ethernet originally used a shared coaxial cable... (CSMA/CD) governed the way the computers shared the channel..." and then carries on in the past tense (apart from the final paragraph oddly enough).
It implies that the CSMA/CD method is no longer used and then provides no information on the currently used method of dealing with multiple users :/
Is it just bad wording?
Thanks in advance.
Cre8tor 20:35, 28 October 2007 (UTC)
"When a twisted pair or fiber link segment is used and neither end is connected to a hub, full-duplex" is nonsense. A hub is like a PC with multiple NICs in crossover mode and set to forward packets. Half duplex is required on coax, not with separate receive and transmit twisted pairs. Some older NIC chips were too slow or not enough ram or bad drivers, ran half duplex. Again, the TX/RX wires don't touch, collisions are actually handled in Hub firmware.
Shjacks45 ( talk) 17:27, 9 December 2007 (UTC)
Actually 100Base-VGAnylan was a Hewlett-Packard token passing protocol. Wiki on IEEE 802.12:"100BaseVG-AnyLAN technology developed by Hewlett Packard, which uses the demand priority access method." 'Overview of IEEE 802.12 Demand Priority'
Shjacks45 ( talk) 17:59, 9 December 2007 (UTC)
win31/win95 to print to HP JetDirect Card network printers directly you had to install HP Jetadmin printing client and "DLC" protocol. ref MS KB Q117629 Q119068 Q94084 Q96623 but most 9x and w31 stuff deleted. If you've an old CD, the (Q146238)Admin.doc file included with Microsoft
Windows 95 Service Pack 1 (has IE 2.0): "Microsoft 32-Bit DLC Protocol
for Windows 95", about access to IBM SNA stuff. IBM incuded it with OS/2. Also listed by HP as DLC/LLC.
DLC is seminal in that it is a MAC address to MAC address protocol. Frustrating that documentation for old software disappears. However in setting SNA connectivity up on a reinstall, some NIC cards worked (like 3com) and some (ne2000 clones) didn't until Microsoft Netbeui was added. TID and MS docs said it was missing functionality in NIC firmware.
Shjacks45 ( talk) 21:32, 9 December 2007 (UTC)
I removed the link to "Wireless Ethernet"(aka 802.11 aka WiFi) in the "Related Standards" section. It stated that 802.11 uses the Ethernet headers(which is false) and that 802.11 is interoperable with Ethernet(which is ridiculous -- how can a standard for wired communication with interoperable with a standard for wireless communication?)-- Ryan Stone 18:13, 25 Nov 2004 (UTC)
The article originally stated that the preamble is 7 octets of 01010101 and the SFD is 11010101. The correct preamble is 7 octets of 10101010 and the SFD is 10101011. I have modified the article to reflect this. http://docs.hp.com/en/98194-90053/ch02s04.html confirms this. —Preceding unsigned comment added by Blutrot ( talk • contribs) 05:58, 2 January 2008 (UTC)
0x0000: ffff ffff ffff 1234 5678 9abc 0000 1083 .......4Vx...... 0x0010: 4567 6767 6767 6767 6767 6767 6767 6767 Eggggggggggggggg 0x0020: 6767 6767 6767 6767 6767 6767 6767 6767 gggggggggggggggg 0x0030: 6767 6767 6767 6767 6767 6767 c948 5581 gggggggggggg.HU.
0x0000: 4567 6767 6767 6767 6767 6767 6767 6767 Eggggggggggggggg 0x0010: 6767 6767 6767 6767 6767 6767 6767 6767 gggggggggggggggg 0x0020: 6767 6767 6767 6767 6767 6767 467a 1c70 ggggggggggggFz.p
Paul!
Electron9 ( talk) 17:53, 22 February 2008 (UTC)
Ethernet#Autonegotiation_and_duplex_mismatch and Ethernet_over_twisted_pair#Autonegotiation_and_duplex_mismatch contain a lot of duplicated text and should be merged. JonathanWakely ( talk) 14:34, 6 March 2008 (UTC)
I have deployed some Extreme Networks equipment that allows deploying 802.3ad (or any aggregation) over multiple physical switches in a stack. We utilize this redundancy to great effect. I don't know where I would find a citation for this, though, since their documentation isn't public and doesn't explicitly claim that it works anyways. I've heard that Ciscos do the same thing, although I haven't found any documentation of it. —Preceding unsigned comment added by Kagato ( talk • contribs) 21:55, 19 August 2008 (UTC)
The picture at the top of the article is labelled "A standard RJ45 Ethernet cable". However the connector is more correctly a 8P8C modular connector. The Physical layer section confirms this "...used twisted pair connected to Ethernet hubs with 8P8C modular connectors (not to be confused with FCC's RJ45).".
I thought I'd mention it here rather than just go ahead and change it. —Preceding unsigned comment added by Mdt3k ( talk • contribs) 13:45, 26 September 2008 (UTC)
"Ten-gigabit Ethernet is still an emerging technology, and it remains to be seen which of the standards will gain commercial acceptance."
It's been installed in my local datacentre for 2 years now. It was probably first commercially available a year or so before that. It's a mainstream technology, soon to be superceded, or at least supplemented by 40G or 100G technologies. Yes, things do move that fast in the technology world.
If the author means to say that the volume of 10G ethernet ports installed is still very low, when measured as a percentage of the total installed bease of Ethernet technologies, then that's a different point. "Emerging" suggests experimental, bleeding-edge (untested, unstable), or special-purpose.
Fgtbell ( talk) 08:57, 22 December 2008 (UTC)
Does the CRC field only check the header, or also the data? My guess would be only the header, but someone should verify this and add it to the article. Aphexer ( talk) 10:58, 7 January 2009 (UTC)
There's no such thing as "Ethernet" cable or "Ethernet hubs" even though many manufacturers label their equipment this way. Ethernet may define the necessary hardware standards, but it does not define the hardware itself. Ethernet can be used on any layer 1 device that supports the necessary signal carry; hubs/repeaters and cables do not read the addresses. Thus, the misnomer. Layer 2, however (such as a switch), is another story as this equipment does read addresses. —Preceding unsigned comment added by 173.18.21.137 ( talk) 02:40, 25 February 2009 (UTC)
The LXI instrumentation platform combines Ethernet-enabled instrumentation with the virtually universal availability of World Wide Web access and applies them to test and measurement applications. The LXI Standard, which is maintained and promoted by the LXI Consortium, an industry consortium that works to ensures the interoperability of LXI compliant instrumentation. The standard defines modular instruments using low-cost, open-standard LAN (Ethernet) as the system backbone. LXI supports synthetic instruments and peer-to-peer networking, enabling some unique capabilities not presently available to the test engineer in any other format. LXI’s flexible packaging, high-speed I/O, and standardized use of LAN connectivity address a broad range of commercial, industrial, aerospace, and military applications. LXI modules can have no front panel or display, using the host PC and Ethernet connections to present setup and results.
The LXI Standard is continuously evolving to take advantage of evolving LAN capabilities. Version 1.3 (released October 30, 2008) incorporates the 2008 version of IEEE 1588 for synchronizing time among instruments, so systems using LXI Class A and Class B devices will synchronize with each other based on the 1588-2008 Precision Time Protocol (PTP) standard. The Consortium also offers information on System Tests for LXI Devices implementing IEEE 1588-2008.
</nowiki>
Nuβiατεch Talk 03:03, 19 May 2009 (UTC)
Why is this graded a Start Class article ? I am under the impression that is is good enough to be a B... Rkr1991 ( Wanna chat?) 12:59, 10 November 2009 (UTC)
in the section Physical layer the preamble is represented as 7 times 10101010, but doesn't the preamble also include the Start-of-Frame-Delimiter and thus is 8 bytes big?
my reference is the book Computer networking, a top down approach section 5.5.1 the structure of an Ethernetframe -- OCELOT525 ( talk) 22:26, 23 December 2009 (UTC)
Significant overlap exists with the Ethernet over twisted pair article and to a lesser extent with the Fast Ethernet and Gigabit Ethernet articles. I've recently cited these as main articles from here. I think this works reasonably well. I do propose merging Ethernet over twisted pair into this ( Ethernet) article. Discussion on this proposal and the more general topic of organizing Ethernet-related articles is solicited. -- Kvng ( talk) 01:06, 21 March 2010 (UTC)
I discovered that Ethernet physical layer had a copy of this whole section. I merged information from the section into Ethernet physical layer and jacked a bit of the intro from that article for the new body of this section. Ethernet over twisted pair advocates please note that Ethernet physical layer references Ethernet over twisted pair with Template:Main. We now have two Template:Main references to Ethernet physical layer. That's a blemish that I'll have to remove another day. -- Kvng ( talk) 16:08, 23 April 2010 (UTC)
![]() | Text and/or other creative content from Full-duplex Ethernet was copied or moved into Ethernet with this edit. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists. |
I know Ethernet was getting big enough, but that article really deserved a merge in a big way. Publicly Visible ( talk) 02:05, 28 March 2010 (UTC)
I am a bit perplexed by the recent deletions of the single mentions of 10base5 and 10base2 versions of Ethernet. Kbrose ( talk) 06:39, 31 July 2010 (UTC)
![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Are there any official logos for the various versions and types of ethernet, like there are for Firewire and USB? Or did nobody think of things like that in the 1970's? —Preceding unsigned comment added by Bizzybody ( talk • contribs) 07:05, August 27, 2007 (UTC)
The ACM classics page appears to no longer list the original ethernet paper. —Preceding unsigned comment added by 130.217.250.13 ( talk) 01:21, 25 September 2007 (UTC)
The first part of this section "CSMA/CD shared medium Ethernet" cofuses me. It begins "Ethernet originally used a shared coaxial cable... (CSMA/CD) governed the way the computers shared the channel..." and then carries on in the past tense (apart from the final paragraph oddly enough).
It implies that the CSMA/CD method is no longer used and then provides no information on the currently used method of dealing with multiple users :/
Is it just bad wording?
Thanks in advance.
Cre8tor 20:35, 28 October 2007 (UTC)
"When a twisted pair or fiber link segment is used and neither end is connected to a hub, full-duplex" is nonsense. A hub is like a PC with multiple NICs in crossover mode and set to forward packets. Half duplex is required on coax, not with separate receive and transmit twisted pairs. Some older NIC chips were too slow or not enough ram or bad drivers, ran half duplex. Again, the TX/RX wires don't touch, collisions are actually handled in Hub firmware.
Shjacks45 ( talk) 17:27, 9 December 2007 (UTC)
Actually 100Base-VGAnylan was a Hewlett-Packard token passing protocol. Wiki on IEEE 802.12:"100BaseVG-AnyLAN technology developed by Hewlett Packard, which uses the demand priority access method." 'Overview of IEEE 802.12 Demand Priority'
Shjacks45 ( talk) 17:59, 9 December 2007 (UTC)
win31/win95 to print to HP JetDirect Card network printers directly you had to install HP Jetadmin printing client and "DLC" protocol. ref MS KB Q117629 Q119068 Q94084 Q96623 but most 9x and w31 stuff deleted. If you've an old CD, the (Q146238)Admin.doc file included with Microsoft
Windows 95 Service Pack 1 (has IE 2.0): "Microsoft 32-Bit DLC Protocol
for Windows 95", about access to IBM SNA stuff. IBM incuded it with OS/2. Also listed by HP as DLC/LLC.
DLC is seminal in that it is a MAC address to MAC address protocol. Frustrating that documentation for old software disappears. However in setting SNA connectivity up on a reinstall, some NIC cards worked (like 3com) and some (ne2000 clones) didn't until Microsoft Netbeui was added. TID and MS docs said it was missing functionality in NIC firmware.
Shjacks45 ( talk) 21:32, 9 December 2007 (UTC)
I removed the link to "Wireless Ethernet"(aka 802.11 aka WiFi) in the "Related Standards" section. It stated that 802.11 uses the Ethernet headers(which is false) and that 802.11 is interoperable with Ethernet(which is ridiculous -- how can a standard for wired communication with interoperable with a standard for wireless communication?)-- Ryan Stone 18:13, 25 Nov 2004 (UTC)
The article originally stated that the preamble is 7 octets of 01010101 and the SFD is 11010101. The correct preamble is 7 octets of 10101010 and the SFD is 10101011. I have modified the article to reflect this. http://docs.hp.com/en/98194-90053/ch02s04.html confirms this. —Preceding unsigned comment added by Blutrot ( talk • contribs) 05:58, 2 January 2008 (UTC)
0x0000: ffff ffff ffff 1234 5678 9abc 0000 1083 .......4Vx...... 0x0010: 4567 6767 6767 6767 6767 6767 6767 6767 Eggggggggggggggg 0x0020: 6767 6767 6767 6767 6767 6767 6767 6767 gggggggggggggggg 0x0030: 6767 6767 6767 6767 6767 6767 c948 5581 gggggggggggg.HU.
0x0000: 4567 6767 6767 6767 6767 6767 6767 6767 Eggggggggggggggg 0x0010: 6767 6767 6767 6767 6767 6767 6767 6767 gggggggggggggggg 0x0020: 6767 6767 6767 6767 6767 6767 467a 1c70 ggggggggggggFz.p
Paul!
Electron9 ( talk) 17:53, 22 February 2008 (UTC)
Ethernet#Autonegotiation_and_duplex_mismatch and Ethernet_over_twisted_pair#Autonegotiation_and_duplex_mismatch contain a lot of duplicated text and should be merged. JonathanWakely ( talk) 14:34, 6 March 2008 (UTC)
I have deployed some Extreme Networks equipment that allows deploying 802.3ad (or any aggregation) over multiple physical switches in a stack. We utilize this redundancy to great effect. I don't know where I would find a citation for this, though, since their documentation isn't public and doesn't explicitly claim that it works anyways. I've heard that Ciscos do the same thing, although I haven't found any documentation of it. —Preceding unsigned comment added by Kagato ( talk • contribs) 21:55, 19 August 2008 (UTC)
The picture at the top of the article is labelled "A standard RJ45 Ethernet cable". However the connector is more correctly a 8P8C modular connector. The Physical layer section confirms this "...used twisted pair connected to Ethernet hubs with 8P8C modular connectors (not to be confused with FCC's RJ45).".
I thought I'd mention it here rather than just go ahead and change it. —Preceding unsigned comment added by Mdt3k ( talk • contribs) 13:45, 26 September 2008 (UTC)
"Ten-gigabit Ethernet is still an emerging technology, and it remains to be seen which of the standards will gain commercial acceptance."
It's been installed in my local datacentre for 2 years now. It was probably first commercially available a year or so before that. It's a mainstream technology, soon to be superceded, or at least supplemented by 40G or 100G technologies. Yes, things do move that fast in the technology world.
If the author means to say that the volume of 10G ethernet ports installed is still very low, when measured as a percentage of the total installed bease of Ethernet technologies, then that's a different point. "Emerging" suggests experimental, bleeding-edge (untested, unstable), or special-purpose.
Fgtbell ( talk) 08:57, 22 December 2008 (UTC)
Does the CRC field only check the header, or also the data? My guess would be only the header, but someone should verify this and add it to the article. Aphexer ( talk) 10:58, 7 January 2009 (UTC)
There's no such thing as "Ethernet" cable or "Ethernet hubs" even though many manufacturers label their equipment this way. Ethernet may define the necessary hardware standards, but it does not define the hardware itself. Ethernet can be used on any layer 1 device that supports the necessary signal carry; hubs/repeaters and cables do not read the addresses. Thus, the misnomer. Layer 2, however (such as a switch), is another story as this equipment does read addresses. —Preceding unsigned comment added by 173.18.21.137 ( talk) 02:40, 25 February 2009 (UTC)
The LXI instrumentation platform combines Ethernet-enabled instrumentation with the virtually universal availability of World Wide Web access and applies them to test and measurement applications. The LXI Standard, which is maintained and promoted by the LXI Consortium, an industry consortium that works to ensures the interoperability of LXI compliant instrumentation. The standard defines modular instruments using low-cost, open-standard LAN (Ethernet) as the system backbone. LXI supports synthetic instruments and peer-to-peer networking, enabling some unique capabilities not presently available to the test engineer in any other format. LXI’s flexible packaging, high-speed I/O, and standardized use of LAN connectivity address a broad range of commercial, industrial, aerospace, and military applications. LXI modules can have no front panel or display, using the host PC and Ethernet connections to present setup and results.
The LXI Standard is continuously evolving to take advantage of evolving LAN capabilities. Version 1.3 (released October 30, 2008) incorporates the 2008 version of IEEE 1588 for synchronizing time among instruments, so systems using LXI Class A and Class B devices will synchronize with each other based on the 1588-2008 Precision Time Protocol (PTP) standard. The Consortium also offers information on System Tests for LXI Devices implementing IEEE 1588-2008.
</nowiki>
Nuβiατεch Talk 03:03, 19 May 2009 (UTC)
Why is this graded a Start Class article ? I am under the impression that is is good enough to be a B... Rkr1991 ( Wanna chat?) 12:59, 10 November 2009 (UTC)
in the section Physical layer the preamble is represented as 7 times 10101010, but doesn't the preamble also include the Start-of-Frame-Delimiter and thus is 8 bytes big?
my reference is the book Computer networking, a top down approach section 5.5.1 the structure of an Ethernetframe -- OCELOT525 ( talk) 22:26, 23 December 2009 (UTC)
Significant overlap exists with the Ethernet over twisted pair article and to a lesser extent with the Fast Ethernet and Gigabit Ethernet articles. I've recently cited these as main articles from here. I think this works reasonably well. I do propose merging Ethernet over twisted pair into this ( Ethernet) article. Discussion on this proposal and the more general topic of organizing Ethernet-related articles is solicited. -- Kvng ( talk) 01:06, 21 March 2010 (UTC)
I discovered that Ethernet physical layer had a copy of this whole section. I merged information from the section into Ethernet physical layer and jacked a bit of the intro from that article for the new body of this section. Ethernet over twisted pair advocates please note that Ethernet physical layer references Ethernet over twisted pair with Template:Main. We now have two Template:Main references to Ethernet physical layer. That's a blemish that I'll have to remove another day. -- Kvng ( talk) 16:08, 23 April 2010 (UTC)
![]() | Text and/or other creative content from Full-duplex Ethernet was copied or moved into Ethernet with this edit. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists. |
I know Ethernet was getting big enough, but that article really deserved a merge in a big way. Publicly Visible ( talk) 02:05, 28 March 2010 (UTC)
I am a bit perplexed by the recent deletions of the single mentions of 10base5 and 10base2 versions of Ethernet. Kbrose ( talk) 06:39, 31 July 2010 (UTC)