CVS update: samba/source/nmbd
Luke Kenneth Casson Leighton
lkcl at switchboard.net
Mon Aug 31 13:10:34 GMT 1998
this has the side-effect of delaying the propagation / removal of old
also, exactly what are you propagating? the only information that needs
to be propagated across multiple workgroups is the list of workgroups
themselves, not the machines _in_ those workgroups.
why? because it is each browse-client's responsibility to find the
1) select network neighbourhood
2) select "ms windows network"
3) select workgroup.
- client does a DMB lookup (workgroup<1b>). if this fails, it does a LMB
lookup (workgroup<1d>). either way, you get an ip address.
- client does a netbios reverse-lookup on in to obtain name SMB server.
- client does a NetServerEnum2 for list of machines in workgroup
therefore, the samba server need not obtain a complete list of machines in
each workgroup, it need only obtain a list of workgroups from each DMB it
knows about (*<1b>).
On Mon, 31 Aug 1998 tridge at samba.anu.edu.au wrote:
> Date: Monday August 31, 1998 @ 16:59
> Author: tridge
> Update of /data/cvs/samba/source/nmbd
> In directory samba:/tmp/cvs-serv19356
> Modified Files:
> nmbd.c nmbd_browsesync.c
> Log Message:
> I realised that my DMB<->DMB sync code has the property that the
> amount of network traffic grows as the square of the number of
> workgroups. It probably wouldn't have caused problems but to be safe I
> changed the code to use random() to decrease the probability of a
> DMB<->DMB sync in proportion to the number of known workgroups. This
> keeps the nice browse connectivity while making the traffic rise only
> linearly with the number of workgroups.
<a href="mailto:lkcl at samba.anu.edu.au" > Luke Kenneth Casson Leighton </a>
<a href="http://mailhost.cb1.com/~lkcl"> Samba and Network Development </a>
<a href="http://www.samba.co.uk" > Samba and Network Consultancy </a>
More information about the samba-technical