bugfixes; passed along to the netkit maintainer, but meanwhile heres a diff. * cosmetic (looked like a short instead as like a byte): unpatched prints wrong data byte #0 should be 0xc1 but was 0xbfbf 8a f8 3d 5 4e d 0 better to make it: wrong data byte #0 should be 0x96 but was 0x94 94 a7 f8 3d df ad e 0 * real the origin of above message is this seq: send 16 recv 16 send 17 (1 idle sec) send 18 recv 17 (ping goes nuts) send 19 recv 18 send 1a recv 19 given the name of the function, it should merely compare payload data and not timevals, or maintain a list of pending id+timeval tuples.
Created attachment 6435 [details] netkit-base-0.17-r7.ebuild (Update)
Created attachment 6436 [details, diff] cosmetic fix and payload comparision fix should not compare timeval, UDP does not warrant in-order packets
I will review this. Please let me know if you get any response from the netkit people...
Will do. I'm not expecting anything, tho.
I was contemplating making a comment about how getting a response from the netkit (team?) would probably be highly unlikely... I see that your sentiments are the same.
I have added your ebuild to portage. It is currently marked unstable.
I have updated the ebuild to use epatch. It is still marked unstable. Please mark this bug VERIFIED if you have no further problems and REOPEN if changes need to be made.
