Please provide a list of protocols using a broadcast address. The table on the "Multicast Address" article is very helpful. Some starters (in an Ethernet environment): PPPoE PADI, ARP, DHCP. Thanks.. — Preceding unsigned comment added by 220.127.116.11 (talk) 21:20, 1 November 2011 (UTC)
|WikiProject Computing / Networking||(Rated Start-class, Low-importance)|
This article is severely misleading and out of date. It still treats Classful IPv4 as default for examples. THis is bad. —Preceding unsigned comment added by 18.104.22.168 (talk) 17:25, 26 January 2009 (UTC)
In the page you state that
"Generally, the broadcast address is found by taking the logical bit complement of the subnet mask and then logically ANDing this with the IP address."
and then give the example:
"This can be found from the subnet mask (255.255.0.0) and the IP address (eg. 172.16.48.196 - the complement of the subnet mask is 0.0.255.255, and 172.16.48.196 && 0.0.255.255 = 172.16.255.255."
For that calculation the last operation schould be OR and not AND.
Please take note.
Definition of broadcast address
Wouldn't it be simpler to say : "The broadcast address is an address which has all host-part bits set to 'one'" ?
Also, at least linux allows using a different broadcast address. Older linux disributions asked as part of the network setup for the broadcast address. Can someone clarify why those broadcast addresses were used/allowed ?
xerces8 --22.214.171.124 14:27, 11 June 2006 (UTC)
Am I missing something here? I thought the subnet mask of the 172.16.0.0 network was 255.240.0.0. That would mean that the broadcast address would be 172.31.255.255, surely? - Tbsdy lives (formerly Ta bu shi da yu) talk 10:19, 12 January 2009 (UTC)
A number of devices still treat the .0 address as a broadcast address (including, surprisingly, the Linux kernel). There should be some mention in the article of the history of this (which I'm not totally sure of, but IIRC both .255 and .0 were broadcast until a number of years ago, when .0 was deprecated - although it's still not recommended even today). 126.96.36.199 (talk) 14:50, 8 May 2009 (UTC)