-
Notifications
You must be signed in to change notification settings - Fork 34
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
Only first knock recognised #2
Comments
Same problem here. I think I found the reason for this problem. According to the logfiles of my server every knock will be sent twice. |
I managed to have the plugin work flawlessly by using pauses between knocks. |
I have the same issue - that individual "knocks" are sent twice (so only the first once is recognised as valid, but the second knock on the first port invalidates the sequence). I had to rewrite my iptables based knocking to see double knocks as allowed behaviour. |
I have the same issue |
Same issue here. Only the first knock is seen. Occasionally the second knock will be seen but pauses do not help me either. Using Debian Jessie and knockd on the server side. Edit: I can now confirm that I see a double knock as well. |
I did also experience the double knock bug. My workaround: Use UDP packets instead. |
Greetings. |
Switching from TCP packets to UDP packets resolved this issue for me. |
Same as well. UDP did the trick ! |
Duplicated tcp packet also for me. |
@gioalex my guess is because while the app makes the devs money, the plugins do not, so they don't support them. Kind of sucks because you expect such a good app to have good support for all of its features. |
Same problem here. TCP packets are sent twice.. using only UDP worked |
Using knockd on server side (both debian wheezy and ubuntu trusty), I set a sequence of knocks like:
sequence = 20xx,30yy,20xx
and while I can have the sequence correctly processed with latest Kitty ssh client, using this plugin only the knocks on the first port are received, ie a port knocking sequence configured as above results in the following on the syslog:
Sep 11 10:01:49 mynas knockd: aa.bb.cc.dd: SSH: Stage 1
Sep 11 10:01:52 mynas knockd: aa.bb.cc.dd: SSH: Stage 1
The text was updated successfully, but these errors were encountered: