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

"with knock" and IPv6 #40

Closed
maleadt opened this issue Oct 17, 2014 · 2 comments
Closed

"with knock" and IPv6 #40

maleadt opened this issue Oct 17, 2014 · 2 comments

Comments

@maleadt
Copy link

maleadt commented Oct 17, 2014

Hi,

Port knocking seems partially broken in firehol 2.0.0 rc2, because of the knock chain not being added for IPv6 traffic. I.e., using server ssh accept with knock admin, I get the following error:

WHAT    : A runtime command failed to execute (returned error 2).
SOURCE  : line 38 of /etc/firehol/firehol.conf
COMMAND : /sbin/ip6tables -t filter -A in_world_ssh_s7 -p tcp --sport 1024:65535 --dport 22 -m conntrack --ctstate NEW\,ESTABLISHED -j knock_admin 
OUTPUT  : 

ip6tables v1.4.14: Couldn't load target `knock_admin':No such file or directory

Try `ip6tables -h' or 'ip6tables --help' for more information.

Which is explained by examining the debug output: firehol only adds the knock_admin chain using iptables, and not using ip6tables

# CONF: 38>>>           server ssh accept with knock admin 


# INFO>>> Preparing for service 'ssh' of type 'server' under interface 'world'

# INFO>>> Creating chain 'in_world_ssh_s7' under 'in_world' in table 'filter'
/sbin/iptables -t filter -N in_world_ssh_s7 
/sbin/ip6tables -t filter -N in_world_ssh_s7 
/sbin/iptables -t filter -A in_world -j in_world_ssh_s7 
/sbin/ip6tables -t filter -A in_world -j in_world_ssh_s7 

# INFO>>> Creating chain 'out_world_ssh_s7' under 'out_world' in table 'filter'
/sbin/iptables -t filter -N out_world_ssh_s7 
/sbin/ip6tables -t filter -N out_world_ssh_s7 
/sbin/iptables -t filter -A out_world -j out_world_ssh_s7 
/sbin/ip6tables -t filter -A out_world -j out_world_ssh_s7 
@philwhineray
Copy link
Member

Hi

Thanks for the report.

Could you try the build from here a go if you have the opportunity? I think this should have gotten fixed at the same time as #38

@maleadt
Copy link
Author

maleadt commented Oct 17, 2014

That build fixes the issue indeed, thanks!

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

No branches or pull requests

2 participants