Quote:
Originally Posted by Konda
Seems more of a Nats issue than Netbilling. Many applications don't support IPV6 yet. If Netbilling doesn't support IPV6 yet, Nats shouldn't sent the IPV6 address.
You (Nats) should just send the surfer's IPV4 address to Netbilling instead of their IPV6 address and there won't be any issue?
Everyone that has an IPV6 address also has a IPV4 address as fallback
Edit. or just ask your host to only use their IPV4 address and ignore the IPV6 address
Edit 2. I do agree that Netbilling is pretty outdated and should support it, but at this time there is no reason to not send the IPV4 address instead of the IPV6 address, and your host and can easily fix that, just ignore the ipv6 and use the ipv4 instead
|
NetBilling support themselves comfirmed that they do not support ipv6.
We are looking at the sales stats, and 50% of our Netbilling MIDs are not coming thru (Hard Decline). Our secondary prodessor Vendo is picking them up.