[PATCH net-next v2 3/3] ipmr: Use full VIF ID in netlink cache reports

2020-09-07 Thread Paul Davey
Insert the full 16 bit VIF ID into ipmr Netlink cache reports. The VIF_ID attribute has 32 bits of space so can store the full VIF ID extracted from the high and low byte fields in the igmpmsg. Signed-off-by: Paul Davey --- net/ipv4/ipmr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[PATCH net-next v2 1/3] ipmr: Add route table ID to netlink cache reports

2020-09-07 Thread Paul Davey
Insert the multicast route table ID as a Netlink attribute to Netlink cache report notifications. When multiple route tables are in use it is necessary to have a way to determine which route table a given cache report belongs to when receiving the cache report. Signed-off-by: Paul Davey

[PATCH net-next v2 2/3] ipmr: Add high byte of VIF ID to igmpmsg

2020-09-07 Thread Paul Davey
in the igmpmsg header. Adding the high 8 bits of the 16 bit VIF ID in the unused byte allows use of more than 255 IPv4 multicast interfaces. Signed-off-by: Paul Davey --- include/uapi/linux/mroute.h | 4 ++-- net/ipv4/ipmr.c | 8 ++-- 2 files changed, 8 insertions(+), 4 deletions

[PATCH net-next v2 0/3] Allow more than 255 IPv4 multicast interfaces

2020-09-07 Thread Paul Davey
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 member. - Assemble VIF ID in Netlink notification from both bytes in igmpmsg header. Paul Davey (3): ipmr

[PATCH net-next 2/2] ipmr: Use full VIF ID in netlink cache reports

2020-09-01 Thread Paul Davey
. The VIF_ID attribute has 32 bits of space however so can store the full VIF ID. Signed-off-by: Paul Davey --- net/ipv4/ipmr.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/net/ipv4/ipmr.c b/net/ipv4/ipmr.c index 19b2f586319b..26cd4ec450f4 100644 --- a/net/ipv4

[PATCH net-next 1/2] ipmr: Add route table ID to netlink cache reports

2020-09-01 Thread Paul Davey
Insert the multicast route table ID as a Netlink attribute to Netlink cache report notifications. When multiple route tables are in use it is necessary to have a way to determine which route table a given cache report belongs to when receiving the cache report. Signed-off-by: Paul Davey

[PATCH net-next 0/2] Allow more than 255 IPv4 multicast interfaces

2020-09-01 Thread Paul Davey
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. Paul Davey (2): ipmr: Add route table ID to netlink cache