Project

General

Profile

Feature #7766

webdav bind ip address configuration setting missing

Added by Seth Russell almost 5 years ago. Updated about 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
Nice to have
Assignee:
-
Category:
OS
Target version:
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

I am using freenas for a file share for several people. I've enabled webdav, but the URL isn't very easy to remember (https://hostname:portnumber/sharename). What I'd like to do is setup a second IP address that will then listen on a normal port, so users don't need to remember a port number - so something like https://webdavserver/sharename.

I am able to add an additional IP address just fine, but webdav doesn't have a configuration setting that allows it to bind to a specific IP address and to listen on specific ports on just that IP. This capability already exists for CIFS, NFS, AFP, etc.

Please add a feature to allow webdav to bind to a specific IP address.

History

#1 Updated by Jordan Hubbard almost 5 years ago

  • Category set to 131
  • Assignee set to Suraj Ravichandran

Not sure about this feature request - over to Suraj to decide if it's worth doing or not. Binding to multiple IPs from a single box, jails notwithstanding, can lead to some weird network confusion where 1 box is claiming n IPs and network administrators want to kill you because you're also not DHCP'ing for the extra IPs and may well screw up other services on the network (I understand that while in a home sharing scenario, this is not likely, FreeNAS also gets deployed to a variety of other environments).

#2 Updated by Suraj Ravichandran almost 5 years ago

  • Status changed from Unscreened to Screened

#3 Updated by Seth Russell almost 5 years ago

I understand that the FreeNAS system stores its configuration settings in some sort of database rather than relying on direct edits to the standard files used by Apache HTTPD. I don't know how the web UI and configuration works, but to make webdav listen on a specific IP and port should be something as simple as adding an IP address specification to the Listen and VirtualHost directives.

here's an example showing the diff between the FreeNAS web UI file and my tmp version:

[root@vmfreenas /etc/local/apache24/Includes]# diff ./webdav.conf /tmp/webdav.conf
1,2c1,2
< Listen 8080
< <VirtualHost *:8080>
---

Listen 10.234.32.199:80
<VirtualHost 10.234.32.199:80>

39c39
< </VirtualHost>
\ No newline at end of file
---

</VirtualHost>

Hope this helps

#4 Updated by Suraj Ravichandran about 4 years ago

  • Project changed from FreeNAS to 9
  • Category changed from 131 to 164

#5 Updated by Suraj Ravichandran about 4 years ago

  • Category changed from 164 to 197
  • Target version set to 237

Moving this over to 10

#6 Updated by Suraj Ravichandran over 3 years ago

  • Project changed from 9 to FreeNAS
  • Category changed from 197 to 131
  • Status changed from Screened to Unscreened
  • Target version changed from 237 to 9.10.1-U2

Exchanging tickets with Deepika, giving her this one instead of 14723, while also moving this to FreeNAS9 (since 10's WebDAV will be a rewrite for release anyways)

#7 Updated by Anonymous over 3 years ago

  • Project changed from FreeNAS to 9
  • Category deleted (131)
  • Status changed from Unscreened to Screened
  • Assignee changed from Suraj Ravichandran to Anonymous
  • Target version deleted (9.10.1-U2)

#8 Updated by Anonymous over 3 years ago

  • Category set to 368
  • Target version set to 377

#9 Updated by Anonymous over 3 years ago

  • Project changed from 9 to FreeNAS
  • Category changed from 368 to 131
  • Target version changed from 377 to 9.10.1-U2

#10 Updated by Anonymous over 3 years ago

@Suraj: I have added a new multiselect field in settings of WebDAV which will allow user to bind IP with WebDAV.
Should I push the changes or is there anything else required?

#11 Updated by Anonymous over 3 years ago

  • Status changed from Screened to Fix In Progress

#12 Updated by Anonymous about 3 years ago

I have created a pull request at https://github.com/freenas/freenas/pull/195

#13 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from 9.10.1-U2 to 9.10.1-U3

#14 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from 9.10.1-U3 to 9.10.2

#15 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Status changed from Fix In Progress to Closed: Not To Be Fixed

Closing this request, the 10 implementation will be different, this isn't a priority for 9.x right now.

Also available in: Atom PDF