aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorDimitri Staessens <dimitri@ouroboros.rocks>2021-04-02 13:50:19 +0200
committerDimitri Staessens <dimitri@ouroboros.rocks>2021-04-02 13:50:19 +0200
commit6ceeac4c1389870602e1f421fd3f784dce89fea4 (patch)
tree472abe60f2197b1b5bb51589674b1bcff9fb7c73 /content
parent24f1040ec08ed39a4be6be29a21de47544793e74 (diff)
downloadwebsite-6ceeac4c1389870602e1f421fd3f784dce89fea4.tar.gz
website-6ceeac4c1389870602e1f421fd3f784dce89fea4.zip
blog: Fix in multicast post
Diffstat (limited to 'content')
-rw-r--r--content/en/blog/20210402-multicast.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/en/blog/20210402-multicast.md b/content/en/blog/20210402-multicast.md
index cc868a2..b363794 100644
--- a/content/en/blog/20210402-multicast.md
+++ b/content/en/blog/20210402-multicast.md
@@ -177,7 +177,7 @@ VLAN. Quite nice, no objections _your honor_!
The semantics of IP broadcast are related to the scope of the
underlying _layer 2_ network. An IP broadcast address is the last "IP
-address" in a _subnet_. So, for instance, in the 192.168.0.0/255
+address" in a _subnet_. So, for instance, in the 192.168.0.0/24
subnet, the IP broadcast address is 192.168.0.255. When sending a
datagram to that IP broadcast destination, the Ethernet layer will be
sending it to FF:FF:FF:FF:FF:FF, and every node _on that Ethernet_