February 26, 200917 yr Ports 80 & 443 are open - only allowing communications to specific subnets. I am able to access unraid administration console by IP, but I can not access the shares. What other ports need to be open for Unraid to communicate with my windows network? 10.0.10.39 is the IP of my unraid //tower is not currently working due to my firewall rules... I see that unraid is trying to communicate with the following every few minutes.... (all currently being blocked) 10.0.10.39.138 > 10.0.10.255.138 udp 213 10.0.10.39.138 > 10.0.10.255.138 udp 183 10.0.10.39.137 > 10.0.10.255.138 udp 50
February 27, 200917 yr I suppose we were waiting for someone more knowledgeable to speak up. I confess I wasn't even aware of the 137 and 138 requests (Samba related?), but then I've thought of unRAID as being locked down to its subnet by default, so haven't worried about any security issues related to this. Do you mind mentioning what tool you used to create that port list? From router logs?
February 27, 200917 yr Ports 80 & 443 are open - only allowing communications to specific subnets. I am able to access unraid administration console by IP, but I can not access the shares. What other ports need to be open for Unraid to communicate with my windows network? Samba requires tcp ports 445 and 139. 10.0.10.39 is the IP of my unraid //tower is not currently working due to my firewall rules... I see that unraid is trying to communicate with the following every few minutes.... (all currently being blocked) 10.0.10.39.138 > 10.0.10.255.138 udp 213 10.0.10.39.138 > 10.0.10.255.138 udp 183 10.0.10.39.137 > 10.0.10.255.138 udp 50 I have no idea what this means... how are you getting this info?
February 27, 200917 yr Uh...nobody here has ever bothered to lock down their NAS? What do you mean by this? By default all access to computers behind an adls router-firewall are blocked. You would need first to make some port forwards before needing anything to be locked up. I hope you haven't. To my understanding UnRAID is not meant to be accessed (management and/or smb) over the internet, only from the internal network. As the default UnRAID installation doesn't contain SSH or firewall you would have to build all this. And there is no easy way to keep the Slackware distro underneath upto date from security point of view. SMB should never be opened directly to internet. To make it clear, never make port forwards for 137, 138 or 445 in your ADSL router.
March 1, 200917 yr Author 10.0.10.39 is the IP of my unraid //tower is not currently working due to my firewall rules... I see that unraid is trying to communicate with the following every few minutes.... (all currently being blocked) 10.0.10.39.138 > 10.0.10.255.138 udp 213 10.0.10.39.138 > 10.0.10.255.138 udp 183 10.0.10.39.137 > 10.0.10.255.138 udp 50 I have no idea what this means... how are you getting this info? That information is from my OpenBSD pf firewall. The output is from a tcpdump on the interface that UNraid is on. I think it means... The first line for example is basically saying 10.0.10.39 port 138 is trying to communicate to 10.0.10.255 port 138 over UDP --- with 213 bytes in the packet the next is the same with 183 bytes the next is trying port 137 to port 138 with 50 bytes in the packet
Archived
This topic is now archived and is closed to further replies.