You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
py-ipv8 does not seem to support IPv6 for some unknown reason. It also appears to be quite hardcoded into it [1].
Suggested solution
My suggestion is to use a special reserved IPv4 address to indicate that the program should look for the ipv6 address later in the payload, as it will clearly not fit in the currently allocated space for IP address. The benefit of using a reserved ipv4 address for this purpose as opposed to a flag bit is that so the flag bits could be used for other purposes down the line.
Remarks
As everyone gets their own IPv6 address NAT hole puncturing should not be necessary for connecting clients together if they can use IPv6.
I would suggest implementing protocol detection procedure based on magic numbers (community numbers, etc) instead. Please, describe possible packet exchange scenarios in this issue, so we can discuss it thoroughly.
Do you realize that you now have the opportunity not only to reimplement the protocol but to redesign it properly?
The problem
py-ipv8 does not seem to support IPv6 for some unknown reason. It also appears to be quite hardcoded into it [1].
Suggested solution
My suggestion is to use a special reserved IPv4 address to indicate that the program should look for the ipv6 address later in the payload, as it will clearly not fit in the currently allocated space for IP address. The benefit of using a reserved ipv4 address for this purpose as opposed to a flag bit is that so the flag bits could be used for other purposes down the line.
Remarks
As everyone gets their own IPv6 address NAT hole puncturing should not be necessary for connecting clients together if they can use IPv6.
Copied from #10
The text was updated successfully, but these errors were encountered: