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

ip rule + ip route isolate host. Bug? #49

Open
giorgiocanale opened this issue Jan 2, 2017 · 0 comments
Open

ip rule + ip route isolate host. Bug? #49

giorgiocanale opened this issue Jan 2, 2017 · 0 comments

Comments

@giorgiocanale
Copy link

I'm trying to use SSLH in transparent mode. as per the instruction this require some iptables+ ip instructions as follows:

iptables -t mangle -N SSLH
iptables -t mangle -A OUTPUT --protocol tcp --out-interface eth0 --sport 22 --jump SSLH
iptables -t mangle -A OUTPUT --protocol tcp --out-interface eth0 --sport 4443 --jump SSLH
iptables -t mangle -A SSLH --jump MARK --set-mark 1
iptables -t mangle -A SSLH --jump ACCEPT
ip rule add fwmark 1 lookup 100
ip route add local 0.0.0.0/0 dev lo table 100

The problem is that once the last one is given the box became unreachable (tested on several pine64 distro, same result).
The very same instructions works fine with other linux boxes, even with arm processors, and even some kernel older than 3.10.
It seems as if the kernel (or some module) "fwmarks" all the packets instead of just the selected ones, hence disrupting the network connectivity.
Once the instructions are given no traffic from the box to the lan works either.
Could this depend on some quirks on this kernel?

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

1 participant