4

I have ufw set up to allow samba connections, but this does not seem to allow files to be transferred through Ubuntu's "Personal File Sharing" using the Public folder. The share can be seen, but not accessed if the firewall is active. Are there extra ports that need to be opened?

The default ufw profile opens ports 137, 138, 139 and 445. To this, I've added 135 and 80, but so far, no joy. I do see connection attempts coming in on high ports (32K+) but these are blocked.

1
  • 2
    First of all, I think you need to consider if you really need to activate the firewall. If you are behind a router, it is probably already firewalled. If you don't forward the ports from the router to your machine to access your shares or other server from the Internet, then you don't need a firewall. Oct 19, 2010 at 2:31

3 Answers 3

5

Or if you want to do it explicitly:

sudo ufw allow proto tcp to any port 135
sudo ufw allow proto udp to any port 137
sudo ufw allow proto udp to any port 138
sudo ufw allow proto tcp to any port 139
sudo ufw allow proto tcp to any port 445
sudo ufw allow proto udp to any port 5353

The first few five rules are Samba. The last is zeroconf to allow other machines on the network to tell your computer about them (it gets names, available resources, etc)

2
  • I actually already have ufw set up to allow samba. I'm not sure about the set of ports it's allowing, but file transfers don't work. I'll try adding the zero-conf port to the list as well.
    – Nerdfest
    Oct 19, 2010 at 9:47
  • The ufw profile for Samba does not seem to include port 135. I'll try adding that one first when I get a chance.
    – Nerdfest
    Oct 19, 2010 at 12:22
3

To allow samba with ufw you can issue the command sudo ufw allow samba. You can then do sudo ufw status to see what ports it has allowed and other useful information.

Though I agree on an internal network a firewall may be entirely unnecessary.

1
  • 1
    This is for a laptop that is not just internal. I generally firewall all machines on my local network anyway (defense in depth). Regardless, I'm more curious about why it won't work with only samba allowed.
    – Nerdfest
    Oct 19, 2010 at 9:48
0

Personal File Sharing (from the menu option at System → Preferences → Personal File Sharing) uses WebDAV over apache2 instead of Samba AFAIK. It is a different filesharing method from that enabled by the "Sharing Options" menu item found when right-clicking on a folder in Nautilus.

See http://ubuntuforums.org/showthread.php?t=1473760

Since it's WebDAV default port should be 80. Is port 80 open?

5
  • Tried it before, but it didn't seem to work ... I'll try again to be sure. I see hits coming in on port 33709 in the logs, but no port 80. Very strange
    – Nerdfest
    Oct 20, 2010 at 0:01
  • No luck with port 80 ...
    – Nerdfest
    Oct 20, 2010 at 2:09
  • 1
    @Nerdfest Please update your question with the various things you have tried so that the next person who tries to help you with your problem doesn't have to dig though the comments, thanks! Oct 20, 2010 at 2:33
  • @Nerdfest, maybe try running netstat while you attempt a connection to the shared folder. 'netstat -tucp' should work, but if you are not familiar with netstat I strongly recommend you read the manpage.
    – koanhead
    Oct 21, 2010 at 3:25
  • koanhead is right that Personal File Sharing uses WebDAV instead of Samba. But I think it listens on a random port instead of port 80, and which it then advertises using avahi. I'm not sure if the port can be statically configured, which might make adding a rule to ufw quite tricky.
    – user8979
    Mar 5, 2011 at 17:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .