On Thursday 2023-08-03 14:57, Phil Sutter wrote: >> > >> >It is not entirely clear what the fixed commit was trying to establish, >> >but the save output is certainly not correct (especially since print >> >callback gets things right). >> >> v1.2.7a-35-gfc9237da missed touching *libip6t_icmp6.c*, so >> it was never updated with the same "bug".[...] > >One could extend icmp6 match (in kernel and user space) to support this >"any" type, though it seems not guaranteed the value 255 won't be used >for a real message at some point. So a proper solution was to support type >ranges like ebtables does. Then "any" type is 0:255/0:255. > >Apart from the above, the three patches of this series should be fine, >right? Yeah.
