right with the top of one's raspmc homepage it says :
the firewall that many of us added within the whole unharness will now be enabled and disabled via raspbmc settings.
they actually claim elsewhere the firewall is iptables and therefore the system is debian based mostly, therefore if you really cant notice settings or it doesnt work, look thru the list returned by service --status-all for iptables. if its there, to actually stop it :
service iptables stop
if you need to actually disable it permanently, use :
update-rc. d iptables disable
however
you dont need to fully disable it. you have to be compelled to notice in which the rules are and modification them. there can be a file in /etc referred to as, eg, iptables. rules. optionally, you might want to build a file coming from the current loaded rules with :
iptables-save iptables-rules. txt
now edit that file and add close to the highest, other then after the very first few lines that begin with :input, :forward, :output :
-a input -p tcp --dport 22 -m conntrack --ctstate new -j accept
then iptables-restore iptables-rules. txt. this can open the sshd port. after all, in case the firewall was very blocking it, presumably raspmc isn't running the sshd server in a natural way either, therefore :
service ssh start
to actually automatically begin at boot :
update-rc. d ssh enable
if you are able to not notice the rules file that iptables is using, then youll need to add that iptables-restore command playing with your file towards the finish of /etc/rc. native.
if you need in order to make the aforementioned firewall rule to a little degree stronger, embody a subnet mask limiting the supply ips to actually your ( w )lan like :
-a input -s 192. 168. zero. 0/24 -p tcp --dport 22 -m conntrack --ctstate new -j settle for
Post a Comment