On 05/11/2014 08:18 PM, Christian Anton wrote:
Hi!
I am a new user to policyd version 2 and a long term (and happy) user of
policyd v1 which I wanted to migrate away from because of problems with IPv6
addresses in the triplets table in mySQL. In the version I was using, the v6
addresses were represented very strange in the db and policyd itself seemed to
not recognize them. I decided to give policyd v2 a look. I have then found a
screenshot that said that even v2 is not yet v6 capable in the stable version,
so I picked the durrent development release 2.1x.
Still, it seems that v6 addresses are not yet fully supported. I can set up what part of the sender IP
address is taken in account at greylisting, with the "Track" option. This is also used for ipv6
which is bad in my opinion. When /32 stands for "whole ip" in v4, in v6 the record in the database
is something like "SenderIP:2001:0470:0000:0000:0000:0000:0000:0000/32" which is not what I would
like to get. Is it planned to make this configurable for both IPv6 and IPv4 addresses separately?
Thanks in advance for any reply.
This is actually a very good point. We do need different CIDR's for both.
Does anyone else have anything to add, or ideas on how you want it
implemented?
-N
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
