allow the hostname to be configured through setup.ini or gcode #1
Conversation
) OPTIONS / was returning a "DAV: 2" header. This causes davfs2 to reject the attempt: /sbin/mount.davfs: mounting failed; the server does not support WebDAV Setting ignore_dav_header 1 in /etc/davfs2/davfs2.conf allows the mount to continue, but this shouldn't be necessary. Advertising Class 1 capability in addition to Class 2 fixes this problem, while not affecting compatibility with other clients (was still able to mount the device from Windows 10, for instance).
|
Withdrawing for more testing...might have a problem with the last commit. |
|
The patches are good...was having problems with insufficient power to the SD-WiFi when plugged in through a data-and-power USB cable or the SD-card slot in my printer's display. Insufficient power was causing writes to fail. When connected with a power-only USB cable, the device is able to draw sufficient power to operate reliably. davfs2 (http://savannah.nongnu.org/projects/davfs2) still doesn't want to write files. webdavfs (https://github.com/miquels/webdavfs) says upfront when you mount the device that since it's missing PUT range support, it will only mount read-only. cadaver (http://webdav.org/cadaver/) works flawlessly, but it's more like the old command-line FTP client than a network filrsystem implementation. |
|
@salfter Im trying to build your fork, which versions of the dependencies do you use to build? |
|
Any progress with this merge? |
Instead of a fixed hostname, it'd be nice if it could be configured. This would be especially true in a situation where you have more than one SD-WiFi on your network.
This patch enables the hostname to be set, either in setup.ini or with a new
M54gcode.