On Sun, 2006-02-05 at 17:09 +0100, Bart Couvreur wrote:
(1) So why isn't this working?
root@PuteA Sat Feb 04 16:52:31 [240] ~ $ iptables -I INPUT -s 192.168.1.0/24 --dport 9000 -j ACCEPT iptables v1.3.0: Unknown arg `--dport'
Sorry forgot something in the line there, it should be: # iptables -I INPUT -s 192.168.0.0/24 -p tcp --dport 9000 -j ACCEPT
Don't quite rember if slimserver needs UDP aswell, if so also enter: # iptables -I INPUT -s 192.168.0.0/24 -p udp --dport 9000 -j ACCEP
OK Bart, I'm almost there...
root@PuteA Mon Feb 06 16:06:57 [267] /home/magnusg $ iptables -I INPUT -s 192.168.1.0/24 -p tcp --dport 9000 -j ACCEPT
root@PuteA Mon Feb 06 16:11:48 [268] /home/magnusg $ iptables -I INPUT -s 192.168.1.0/24 -p udp --dport 9000 -j ACCEPT
root@PuteA Mon Feb 06 16:12:02 [269] /home/magnusg $ iptables -L Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere
Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- 192.168.1.0/24 anywhere udp dpt:9000 ACCEPT tcp -- 192.168.1.0/24 anywhere tcp dpt:9000 RH-Firewall-1-INPUT all -- anywhere anywhere (etc.)
At this point I'm able to access slimserver remotely, either via the browser (http://192.168.1.11:9000) or via an audio player like xmms (http://192.168.1.11:9000/stream.mp3). But when I reboot, the iptables configuration goes back to what it was before. So I need to save these changes somehow.
Entering "iptables-save" before rebooting doesn't work; "iptables-save -c" as it says in the "Red Hat Linux Bible" doesn't work either. What's the right command here, in FC4?
Thanks again for the help. Jerry