New answers tagged firewall
It's a bit tricky. You can isolate only traffic that passes through your gateway. For instance you can use that rules: iptables -I FORWARD -s 192.168.1.0/24 -d 192.168.2.0/24 -j DROP iptables -I FORWARD -d 192.168.1.0/24 -s 192.168.2.0/24 -j DROP or: iptables -I FORWARD -i eth0.1 -o eth0.2 -j DROP iptables -I FORWARD -o eth0.1 -i eth0.2 -j DROP Both ...
You can try adding the following rules to your iptables firewall: $ sudo iptables -A INPUT -p tcp --dport 80 -s 192.168.0.0/24 -m state \ --state NEW,ESTABLISHED -j ACCEPT $ sudo iptables -A OUTPUT -p tcp --sport 80 -d 192.168.0.0/24 -m state \ --state ESTABLISHED -j ACCEPT
I had posted this question to the TI Forums as well, and got a response. Enabling CONFIG_NETFILTER_XT_MATCH_CONNTRACK in the kernel config solved this issue. I just set CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y in the config, rebuilt with the SDK (instructions here). After installing the new kernel and modules, the -m conntrack command doesn't complain ...
block all pass in on fxp0 proto tcp from any to any port 22 flags S/SA pass out on fxp0 proto tcp from any to any port 22 flags S/SA Please consider you have to change fxp0 to your ethernet according to your operating OS. Reverse of above: pass in on fxp0 proto tcp from any to any port < 22 flags S/SA pass out on fxp0 proto tcp from any to any port ...
Top 50 recent answers are included