|
Linking with some more log-related problems...
Also, note that the cleanremoteaddr() function seems to clean invalid (private) IPs and incorrect IPs (I guess IPv6 are handled as incorrect).
Ciao changing name of bug to Full IPv6 support - this will require database changes, I am afraid it is not possible to fully fix in 1.9.x - sorry.
hmm, there are several ways how to write ipv6:
ABCD:EF01:2345:6789:ABCD:EF01:2345:6789 - 39chars FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:129.144.152.138 - 45chars and compressed forms I think it should be better to use 45 chars. going to change all install.xml's now.... With the 45 char comment, I think you may be referring to http://www.ietf.org/rfc/rfc3513.txt
There are not as many fields with the bits all set to one as you have listed above. Uncompressed this is what it would look like: ah, right -will wait a bit and discuss it with more ppl, thanks
Petr, I know you have not finished, so you may know this already, but there is the quiz.subnet field, which takes a list of IP addresses, or address ranges, and the address_in_subnet method in moodlelib.php (which has extensive unit tests).
working on subnets right now :-D
ipv6 support should be implemented now, please reopen in case I overlooked something or it does not work as expected
thanks everybody! |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I guess this is caused by the log->ip column in DB accepting only 15cc (IPv4). Can you try manually increasing the column size in your server? What would be a correct length?
I would propose to:
This should be fixed consistently in all reports showing IPs, not only live logs.
Assigning to Mathieu...TIA!
Ciao