samba - Feb 2019 - How to identify the operating system of a client?

On 11.02.19 11:37, Udo Kaune via samba wrote:
> Am 11.02.19 um 11:30 schrieb Ralph Böhme via samba:
>> On Mon, Feb 11, 2019 at 10:26:31AM +0100, Stephan Roth via samba wrote:
>>> Let me rephrase the question in hope for an answer:
>>>
>>> Is it at all feasible to identify the operating system of a client?
>>
>> no, not really. We try to match by the list of supported SMB dialects 
>> in the SMB1 negprot, but that is really just guesswork.
>>
>> -slow
>>
> Maybe some means of translation table would come in handy
> https://www.adminsub.net/mac-address-finder/apple
> 
> br
Thanks for the idea, but that's not an option, as USB ethernet dongles 
from non-Apple vendors are used with Macs in the network I'm working with.

Stephan

Am 11.02.19 um 12:00 schrieb Stephan Roth via samba:
> On 11.02.19 11:37, Udo Kaune via samba wrote:
>> Am 11.02.19 um 11:30 schrieb Ralph Böhme via samba:
>>> On Mon, Feb 11, 2019 at 10:26:31AM +0100, Stephan Roth via samba
wrote:
>>>> Let me rephrase the question in hope for an answer:
>>>>
>>>> Is it at all feasible to identify the operating system of a
client?
>>>
>>> no, not really. We try to match by the list of supported SMB 
>>> dialects in the SMB1 negprot, but that is really just guesswork.
>>>
>> Maybe some means of translation table would come in handy
>> https://www.adminsub.net/mac-address-finder/apple
>>
> Thanks for the idea, but that's not an option, as USB ethernet dongles 
> from non-Apple vendors are used with Macs in the network I'm working 
> with.
>
Could you use DHCP option 60 to resolve to a separated IP range for you 
Mac clients? (excerpt from a Samsung TV)

Frame 54169: 347 bytes on wire (2776 bits), 347 bytes captured (2776 
bits) on interface 0
User Datagram Protocol, Src Port: 68, Dst Port: 67
Bootstrap Protocol (Discover)
     Option: (60) Vendor class identifier
         Length: 37
         Vendor class identifier: 1.18.1-VD Linux VDLinux.1.2.1.x

br

On 13.02.19 10:41, Udo Kaune via samba wrote:
> Am 11.02.19 um 12:00 schrieb Stephan Roth via samba:
>> On 11.02.19 11:37, Udo Kaune via samba wrote:
>>> Am 11.02.19 um 11:30 schrieb Ralph Böhme via samba:
>>>> On Mon, Feb 11, 2019 at 10:26:31AM +0100, Stephan Roth via
samba wrote:
>>>>> Let me rephrase the question in hope for an answer:
>>>>>
>>>>> Is it at all feasible to identify the operating system of a
client?
>>>>
>>>> no, not really. We try to match by the list of supported SMB 
>>>> dialects in the SMB1 negprot, but that is really just
guesswork.
>>>>
>>> Maybe some means of translation table would come in handy
>>> https://www.adminsub.net/mac-address-finder/apple
>>>
>> Thanks for the idea, but that's not an option, as USB ethernet
dongles
>> from non-Apple vendors are used with Macs in the network I'm
working
>> with.
>>
> 
> Could you use DHCP option 60 to resolve to a separated IP range for you 
> Mac clients? (excerpt from a Samsung TV)
> 
> Frame 54169: 347 bytes on wire (2776 bits), 347 bytes captured (2776 
> bits) on interface 0
> User Datagram Protocol, Src Port: 68, Dst Port: 67
> Bootstrap Protocol (Discover)
>      Option: (60) Vendor class identifier
>          Length: 37
>          Vendor class identifier: 1.18.1-VD Linux VDLinux.1.2.1.x
> 
> br
> 
Again, thanks for the idea. The DHCP service is managed outside of my 
area of responsibility, I can't change or access anything.

I got a suggestion to use nmap with the smb-os-discovery plugin. I'll 
give it a try when I have time and report back with my findings.

- Stephan