Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uninitialized variable causes TCP message flooding #50

Closed
lohrentzo opened this issue Dec 7, 2018 · 0 comments · Fixed by #51
Closed

Uninitialized variable causes TCP message flooding #50

lohrentzo opened this issue Dec 7, 2018 · 0 comments · Fixed by #51

Comments

@lohrentzo
Copy link

Hello, I just wanted to highlight that when the protocol is TCP the variable int rawsock; is never initialized and running the program from a daemonized script (nohup + background) causes the "received ICMP message" to be displayed then returning the uninitialized value and causing a message flooding because of an infinite loop in the shoot() function.

Putting int rawsock = -1; (transport.c:104) is enough to fix the issue.
Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant