?What addresses are returned with UDPPacket::GetDestinationAddress() and UDPPacket::GetSourceAddress()?
If it was an IPV6 packet it will return the IPV6 LL addresses.
It will print as an IPv6 address.
If it was an IPV4 packet it will return an address that contains the IPV4 address and the member function IIsEmbeddedIPV4()
will return true, and any attempt to print out the address will appear as an IPV4 address, because that is what is is...
If you go to the page on reserved IP Addresses...
https://en.wikipedia.org/wiki/Reserved_ ... esses#IPv6
There are two prefixes dealing with IPV4 transitions
IPV4 Mapped addresses, and IPV4 translated addresses.
IPV4 mapped addresses are a means to store an IPV4 address inside an IPV6 address object.
IPV4 mapped addresses are never meant to be seen on the wire. They are a means to say here is an IP address your supposed to treat any operations on this like its an IPv4 address. When you do IPv4 addresses on the netburner in IPV6 mode they are stored in this format.
This dual mode stack is then smart enough to "Do the right thing" talking to an IPV4 device, send IPv4 packets, talking to an IPV6 deivce using an IPV6 address send IPV6 packets.
This is different than the IPv4 translated addresses, the translated addresses are meant to enable an IPV6 host that HAS NO ipv4 stack to talk to an IPV4 device by translating the address, and expecting the router to translate the address....and packet format.
The NetBurner in IPV6 mode will operate identically to the Netburner in ipv4 mode
IE if all your addresses are Ipv4 then it will send recieve IPv4 packets.
with several very minor differences.
1)Internal storage of IPADDR is now 128 bits, so if you have binary formatted structures of your own design that contain IPaddresses, you need to
change their declaration to be IPADDR4 if you want them backward compatible.
2)The Netburner will do all the normal IPV6 link discovery and prefix discovery stuff in the background.
3)If someone sends you IPV6 formatted packets, Udp, Tcp etc... then the printout of the associated addresses may be larger than you expect.
4)You can choose to send IPV6 TCP and UDP to devices that have IPV6 addresses. Whether or not the address is gotten from DNS or some form of text input it will just do the right thing.