Any plans of supporting IPv6? I've already been struck by the first wiki spam bots using IPv6 - and I had to add that IP-range to a local blocklist to get rid of it.
Of course, blacklisting single IPv6-addresses doesn't give as much omph as blacklisting single IPv4-addresses ... but I guess there are viable strategies - i.e. start blocking a single IPv6, if two IPs in the same /64-range is spamming, block the full /64-range, and then continue blocking /56-ranges, /48-ranges etc if the frequency is too big.
Author: H.User2584 (23 Oct 13 9:54am)
Yes, this is needed quite urgently - indeed, if I visit my honeypot from my machine (which is hosted on a dual stack server, as is my desktop) it gives me validation errors.
I kept reinstalling my honeypot until I had a brainwave moment and thought "wait, I'm getting to it over ipv6, maybe it doesn't like that" - indeed, that was the case. Force ipv4 connection and it's happy.
Author: J.Allen15 (31 Mar 15 3:13pm)
I cannot activate using IPv6 and we are moving to an all IPv6 setup soon.
When might there be an IPv6 version.
Author: C.Falconer (27 Apr 15 4:25pm)
I concur - my link is http://criggie.org.nz/cgi-bin/darlingfranchise.cgi which fails over IPv6.
This link fails to verify
However this works perfectly and I can now verify and proceed.
IPv6 cannot be ignored, its not going away. This report is over 2 years old.
Author: C.Brand3 (13 Jul 15 1:49am)
Enter an IP to lookup:
Any plans of supporting IPv6?
Author: S.Holwegner (19 Oct 17 1:30pm)
This isn't going to go away.. I'm sure plenty of things need to be refactored, but I question just how useful my self-hosted honeypots are. I can give you MX records all day long- but if the capture software isn't capable of handling IPv6 requests, it becomes less useful in this day and age.
You may browse the discussion topics, but you must sign in to post. If you do not have an account, you can create one for free.