Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62194 - [sshfs] mounts can trigger network connection lost
Attached to Project:
Arch Linux
Opened by Sebastian Martin Dicke (sdicke) - Saturday, 30 March 2019, 18:51 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 03:29 GMT
Opened by Sebastian Martin Dicke (sdicke) - Saturday, 30 March 2019, 18:51 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 03:29 GMT
|
DetailsDescription:
I observed a problem regarding the combination of a Intel 802.11 card (respectively its firmware), the kernel driver communicating with it, sshfs and (maybe) a particular SFTP server (primitive ftpd (version 5.14), running on an Android smartphone). Such problems do not occur with OpenSSH servers with me. Additional info: Software: * sshfs 3.5.1-2 * fuse3 3.4.2-1 * linux 5.0.5.arch1-1 * linux-firmware 20190313.efd2c1c-1 Hardware: * Wireless 8260 version 3a * Platform: x86_64 Steps to reproduce: 1. Mount a remote SFTP server on a non-standard port via WLAN. 2. Operate on the mounted directory (navigate through the directory hierarchy). 3. Any time later the WLAN connection get lost, after one minute or a half minute after beginning of the navigation the the directory hierarchy, maybe. 4. When the connection is reestablished, it get lost within seconds. 5. Dismounting of the previously mounted directory from the SFTP server ends the connection lost problems. 
log
(32.5 KiB)
|
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 29 May 2023, 03:29 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
Monday, 29 May 2023, 03:29 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
Comment by Giancarlo Razzolini (grazzolini) -
Friday, 17 January 2020, 14:40 GMT
Is this still happening with latest versions?