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
Below is a fix for this problem below. Together with other fixes I have reported recently, the fix below made the (high quality) program I tried to run with DCE actually work. The fix only applies to IPv4. I think the same problem exists for IPv6 and can be fixed in the same way though some additions to ipv6-packet-info-tag.cc in NS3 would be needed.
First, this patch for ns-3.26 is needed. It sets the source and destination (local) addresses in the Ipv4PacketInfoTag in the ForwardUp method. Actually, only the destination address is needed to solve this particular problem but it seems like a bug the other one is not set.
Second, this patch for DCE 1.9 is needed. It uses the information set by NS-3 above and also includes an extra memset to avoid passing undefined values to the user:
Below is a fix for this problem below. Together with other fixes I have reported recently, the fix below made the (high quality) program I tried to run with DCE actually work. The fix only applies to IPv4. I think the same problem exists for IPv6 and can be fixed in the same way though some additions to ipv6-packet-info-tag.cc in NS3 would be needed.
First, this patch for ns-3.26 is needed. It sets the source and destination (local) addresses in the Ipv4PacketInfoTag in the ForwardUp method. Actually, only the destination address is needed to solve this particular problem but it seems like a bug the other one is not set.
Second, this patch for DCE 1.9 is needed. It uses the information set by NS-3 above and also includes an extra memset to avoid passing undefined values to the user:
The text was updated successfully, but these errors were encountered: