[lkml]   [2020]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH net-next v2 0/3] Allow more than 255 IPv4 multicast interfaces
Currently it is not possible to use more than 255 multicast interfaces
for IPv4 due to the format of the igmpmsg header which only has 8 bits
available for the VIF ID. There is space available in the igmpmsg
header to store the full VIF ID in the form of an unused byte following
the VIF ID field. There is also enough space for the full VIF ID in
the Netlink cache notifications, however the value is currently taken
directly from the igmpmsg header and has thus already been truncated.

Adding the high byte of the VIF ID into the unused3 byte of igmpmsg
allows use of more than 255 IPv4 multicast interfaces. The full VIF ID
is also available in the Netlink notification by assembling it from
both bytes from the igmpmsg.

Additionally this reveals a deficiency in the Netlink cache report
notifications, they lack any means for differentiating cache reports
relating to different multicast routing tables. This is easily
resolved by adding the multicast route table ID to the cache reports.

changes in v2:
- Added high byte of VIF ID to igmpmsg struct replacing unused3
- Assemble VIF ID in Netlink notification from both bytes in igmpmsg

Paul Davey (3):
ipmr: Add route table ID to netlink cache reports
ipmr: Add high byte of VIF ID to igmpmsg
ipmr: Use full VIF ID in netlink cache reports

include/uapi/linux/mroute.h | 5 +++--
net/ipv4/ipmr.c | 14 ++++++++++----
2 files changed, 13 insertions(+), 6 deletions(-)


 \ /
  Last update: 2020-09-08 00:04    [W:0.060 / U:1.760 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site