Gary Winiger wrote: >> IPv6 NAT for IP Filter >> >> Overview >> ======== >> This change request aims to provide IPv6 NAT capabilities for IP Filter. >> The requested release binding is micro/patch. > >> Customer impact >> =============== >> A customer which uses ioctl SIOCGNATL and SIOCSTPUT to access IPv4 NAT >> sessions in kernel needs to rebuild their program due to the changes of >> structure "nat_t" and "natlookup_t" in /usr/include/netinet/ip_nat.h. > > What is the taxonomy of these ioctls. If it is above Volatile, > how is the incompatible change mitagated for the requested > release binding?
I was wondering if someone would notice this... There are a few things going on here... 1) management isn't interested in investing in a non-ioctl API unless there is significant interest outside of engineering (there is some interest), meaning that internal changes that get reflected in changes to the ioctls either cost engineers a whole bunch of extra work or cause customers a bunch of pain/work; 2) the changes to support ipv6 NAT, in the external code base are being made as part of the next major release (4.x -> 5.x) but we're not doing that here... Feel free to accost said mangler when he returns O:-) Darren
