Closed PherricOxide closed 11 years ago
I believe this was a side effect of using the 'default' profile with a TCP reset action set. Honeyd was attempting to reply to broadcast packets and couldn't figure out what interface to use when trying to send something to 255.255.255.255. Hasn't been seen again since we changed the usage of the default profile.
I'm going to close this and call it fixed unless we're able to see it again. Looks to be fixed.
Honeyd seems to segfault if you create a node with a static IP address and then spoof udp packets using FAST with the source IP set to the same as the honeydpot IP. Stack trace follows,