Hot answers tagged iptables
The problem is now at least partly solved (I'm fine with this). I was testing the network with Windows clients in the beginning, and both PCs had got the Windows 10 upgrade lately. The problem itself was really stupid: Windows didn't response to pings since there is some new security enabled by default in Windows 10. When I added one Linux laptop to the ...
First, your default policy in the FORWARD chain is ACCEPT, so you're not actually denying any traffic. This explains why the 20 -> 50 forwarding works. You can fix this with iptables -P FORWARD DROP. As far as the other pings, notice that in your log entries, the TTL is either 127 or 63, indicating the firewall has already made its routing decision and ...
It seems that: iptables -A PREROUTING -t mangle -i eth0 -m cluster --cluster-total-nodes 2 --cluster-local-node 1 --cluster-hash-seed 0xdeadbeef -j MARK --set-mark 0xffff iptables -A PREROUTING -t mangle -i enp1s0 -m cluster --cluster-total-nodes 2 --cluster-local-node 1 --cluster-hash-seed 0xdeadbeef -j MARK --set-mark 0xffff helped to get it running.
Following the suggestion of user228273 i could find configuration that solved the problem: First I created a tap interface named tap0, and I brought it up: ip tuntap add mode tap tap0 ip link set tap0 up if one of the previous command fails, it is probably because you already have a tap0 interface. Use the command ip link show to assess the situation, ...
Only top voted, non community-wiki answers of a minimum length are eligible