Closed lukefadedaway closed 1 year ago
The fix is not included to 4.5.2 by mistake, It's available in the master branch though. I have tested it and it work as expected.
The fix is also not present in 4.5.3 Would be great if this could be included in the next release.
This fix will be part of 4.5.4, it's already added to the v4.5.x branch.
This bug is still in INET version: 4.5.2 ( https://github.com/inet-framework/inet/issues/880 )
Apparently this fix wasn't correctly pushed to the releases.
To reproduce this bug, use these two files: (Configuration A-to-B will run without the bug because B is not the first Device in the ini file. B-to-A will show the bug because A is the first device and therefore can't bee addressed) bugtest.ini :
bugtest.ned :
Packet A-to-B going the correct path:
Packet B-to-A not being able to be correctly routed:
Originally posted by @lukefadedaway in https://github.com/inet-framework/inet/issues/880#issuecomment-1753479231