https://bugs.kde.org/show_bug.cgi?id=418417
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |UPSTREAM
--- Comment #1 from Harald Sitter <sit...@kde.org> ---
Obligatory stop using smb1:
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858
With that out of the way your suggestions isn't entirely unreasonable but KIO
doesn't make the browsing decision, that's libsmbclient. So, I think you'll
want to file a bug in the samba bugzilla to get the behavior changed. I would
think there's a reason they've made it attach to maximum though, so perhaps
there's a good explanation.
On a side note: just because legacy equipment doesn't support wsdiscovery/dnssd
doesn't mean you cannot expose it via those systems.
Any host can act as a publisher for another host, for example any cheapo ARM
board would do the trick by making a bunch of services publishing the relevant
data on wsd/dnssd
e.g. with avahai
> avahi-publish -a blackbox.local 192.168.100.206
> avahi-publish -s -H blackbox.local SMB_ON_BLACKBOX _smb._tcp 445
and/or with https://github.com/christgau/wsdd
> wsdd.py -v -n BLACKBOX # (in this case the name must be the actual
> netbios/llmnr name of the host; or you need to use a literal ip address as
> name)
--
You are receiving this mail because:
You are watching all bug changes.
