Add support for IPv6
There is now no support for IPv6 addresses. This consists of several problems. We have to think if we want to have two separate channels or just one.
We can have one channel and client would keep two ipsets for one channel and depending on address type (probably regular expression match) it would add it to correct ipset.
Second option is to have two channels and two clients running, one for ipv4 one for ipv6. All filtering and logic would be done on server and client would report error if invalid address format would be in set (pretty much state after !9 (merged)).
Considering required filtering:
- IPv4 addresses should be added to IPv6 set as well (IPv6 to IPv4 mapping address range)
- Possibly detected IPv6 addresses mapped to IPv4 should be added to IPv4 set as well (we should probably convert them to IPv4 on server)
- local, broadcast and other invalid addresses should be filtered out (this is optional and covered by turris/sentinel/dynfw#1)
Related to
- turris/sentinel/sentinel#5