Consider ipv6

[tigerfoot]

With the grow of ipv6 usage it would be cool to have ipv6 support in knock/knockd

See a proposal by debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617369

[mxjeff]

Hi,
Any news concerning ipv6 support?

Cheers

[DuncanRobertson]

I concur with this request, I just added IPV6 to my network and it would be great to use port knocking. At I have the patch from the Debian bug report to apply.

[airwoflgh]

Added this to the TODO list for 0.8.

EDIT - using 0.8.0 for dynamic port knocking functionality. Will be part of a future 0.8.x release.

[schnz]

Is there any chance that PR #53 is to be reviewed/merged anytime soon? Currently, when using the knock client for portknocking, SSH must be forced to connect via IPv4 in order to work.

// Edit: Meanwhile, I created a package in the Arch User Repositories with PR's #52, #53 and #55 being applied: https://aur.archlinux.org/packages/knockd-ipv6/

[TDFKAOlli]

Also created a pull request for OpenWRT Makefile change (milaq/openwrt_knockd#6) including #52, #53 and #55 and build for OpenWrt 18.06.1.

[primeos]

Unfortunately this project seems to be abandoned (last commit at the end of 2015).

[TDFKAOlli]

@primeos & all: I have taken the actual pull requests #52 #53 and #55 and merged them on master in my fork TDFKAOlli/knock. It can be used as repo until @jvinet decides to continue this project here (I don't want to steal or hijack the repo). For me it is easier to continue on an integrated repository, as I want to look into 1. less memory consumption for router usage (OpenWRT) and 2. support for multiple interfaces for the knockd server.
BTW: I didn't merge #59 yet as it conflicted with IPv6 feature and I think the IPv6 feature is more important. (at last I do have a dual stack light, so no proper IPv4 to be reached by the internet).