Invalid IPv6 ip addresses in remote_ip field of order object

in Development
Hi,
When retrieving an IP address using the remote_ip field of an order object we obtain invalid IPv6 addresses. From my observations it seems like every ipv6 address gets cut off at 15 chars, the max length of a ipv4 address. When a customer places the order using ipv4 everything works as expected, the field will contain a XXX.XXX.XXX.XXX ip address. When using ipv6 however the field contains data like XXXX:XXX:XXXX:X or XXXX:XXXX:XXXX: instead of the complete XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX address.
Am I using the wrong field to obtain a IP or is the a bug on lightspeeds end?
Tags:
2 comments
Hi @lars,
Thank you for reaching out to us.
What you're saying is exactly what is happening. But our devs are saying this isn't a bug since this was never in the system. They also are saying that they're not building this because this will require a huge database migration and downtime.
I hope you'll understand.
Actually, I don't understand why this will not be done.
You can't deny that everyone is now changing to ipv6, and there comes a time you need to migrate.