Quote:
	
	
		| 
					Originally Posted by Kymmy   | 
	
 Giving this a go now.... 

---------- Post added at 22:29 ---------- Previous post was at 22:19 ----------
	Quote:
	
	
		| 
					Originally Posted by Kymmy   | 
	
 I've followed the link, and adjusted what i feel is necessary, so IPTables now looks like this:-
pi@raspbmc:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
ACCEPT     all  --  192.168.0.0/24       anywhere            
DROP       all  --  anywhere             anywhere            
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
pi@raspbmc:~$
---------- Post added at 22:31 ---------- Previous post was at 22:29 ----------
I tried adding this:-
"sudo iptables -A INPUT -p tcp --dport 1979 -m state --state NEW -j ACCEPT"
It accepts the changes, but then disappears after the PI is rebooted....
---------- Post added at 23:03 ---------- Previous post was at 22:31 ----------
	Quote:
	
	
		| 
					Originally Posted by Kymmy  ...and with that simple test you have found that there's nothing wrong with the superhub    
What's in (if it exists)
 
	Code: /etc/network/iptables | 
	
 You my man, are an absolute genius!! 
 
  
Got this working now, thanks a million! Owe you a pint or two! 
