If you just want to have no blocking rules, remove the last drop line and remove the $netmask from the first accept line. Iptables -A INPUT -p tcp -dport 8888 -j ACCEPT Iptables -A INPUT -p tcp -dport 9091 -j ACCEPT Iptables -A INPUT -p tcp -dport 5050 -j ACCEPT Iptables -A INPUT -s $NETMASK -i $IFACE -j ACCEPT
This for example is my file, it has a few ports open: if then That's why there is a file, that raspbmc executes at every boot: /etc/network/if-up.d/secure-rmcĮdit it with nano: sudo nano /etc/network/if-up.d/secure-rmcĪt the very end of the file you could indeed remove the drop line, or if you want to open up certain ports, you could also do that by adding lines. You can add rules or drop rules, however, when you reboot, the iptables rules are always reset. You can view your current set of rules with the command: iptables -L -n The firewall in linux is implemented via iptables. If you want to make the aforementioned firewall rule a little stronger, include a subnet mask limiting the source ips to your (W)LAN such as: -A INPUT -s 192.168.0.0/24 -p tcp -dport 22 -m conntrack -ctstate NEW -j ACCEPT If you could not find the rules file that iptables is using, then you'll have to add that iptables-restore command using your file to the end of /etc/rc.local. To automatically start at boot: update-rc.d ssh enable Of course, if the firewall was really blocking it, presumably raspmc is not running the sshd server by default either, so: service ssh start Then iptables-restore < iptables-rules.txt. Now edit that file and add near the top, but after the first few lines that begin with :INPUT, :FORWARD, :OUTPUT: -A INPUT -p tcp -dport 22 -m conntrack -ctstate NEW -j ACCEPT Optionally, you can create a file from the current loaded rules with: iptables-save > iptables-rules.txt There could be a file in /etc called, eg, "les". You need to find where the rules are and change them. If you want to disable it permanently, use: update-rc.d iptables disable If it's there, to stop it: service iptables stop They claim elsewhere the firewall is iptables and the system is debian based, so if you can't find Settings or it doesn't work, look thru the list returned by service -status-all for "iptables". The firewall configuration, especially if youre a beginner in Linux, may seem tricky and difficult to. The firewall that we added in the release can now be enabled and Raspberry Pi: iptables (Security - Part II). No traffic is passing through the firewall.Īnd my /etc/config/network looks like this config interface 'loopback'Ĭould somebody give me a hint what is wrong in my configuration.Right at the top of the raspmc homepage it says: I have Problems with the configuration since my configuration does not work. I want to use Openwrt on a Raspberry Pi 3 as a Firewall between to router.
0 kommentar(er)
