Page 1 of 1

TC LAn plugin and LLMNR name resolution. Please add.

Posted: 2021-09-25, 21:20 UTC
by cpservicespb
There is LLMNR (Link-Local Multicast Name Resolution) name resolution way wihin Windows, Linux (via systemd-resolved) as substitution of NetBios name resolution for Smb2/Smb3 protocols.
It utilizes 5355 port (not 5353) and resolve names without dedicated DNS server for IPv4 and Ipv6.
Please add such functional to the plugin with checkbox "Use LLMNR for name resolution"

Re: TC LAn plugin and LLMNR name resolution. Please add.

Posted: 2021-09-26, 07:30 UTC
by ghisler(Author)
I have never heared of LLMNR, but a quick Google search seems to reveal that Windows indeed seems to support it as a client. But what kind of server do I need to get the names resolved? Does it need an active directory?

Re: TC LAn plugin and LLMNR name resolution. Please add.

Posted: 2021-09-26, 11:38 UTC
by cpservicespb
Link-Local Multicast Name Resolution is intended for name resolution using DNS formatted multicast packets via 5355 port on network even without dedicated DNS server.
As you could know at least Windows 10 don' t use smb1 as well as NetBios name resoultion way.
Instead of it it uses LLMNR.
And there is no need any servers for it.
It looks like NetBios which can work without WINS server also.
Let's image, there are some of Windows client OSes (WIndows 10) and Linux client OSes (Ubuntu 18.04) without any servers.
And all of them is able to access to it by short name, without domain part as at old kind times when NetBios used for.

Re: TC LAn plugin and LLMNR name resolution. Please add.

Posted: 2021-09-28, 13:35 UTC
by ghisler(Author)
So you meant that I can call the LLMNR name resolution functions without the need to configure anything?

Re: TC LAn plugin and LLMNR name resolution. Please add.

Posted: 2021-11-26, 17:37 UTC
by ghisler(Author)
I have added LLMNR name resolution for testing now. Please try it:
https://www.totalcommander.ch/beta/tcandroidlan330b2.apk

The plugin will use IPv4 lookup if the device has an IPv4 address (or is dual stack), and IPv6 lookup if it only has an IPv6 address only.

The new version also supports SMB3 and encrypted transfers on Android 4.4 and newer by using the latest smbj library.

By default, encrypted transfers are disabled because they take about 1.5 times the time as unencrypted transfers. Therefore the plugin will use encrypted transfers only if the server enforces it, or if you check the option to use them.