samba - Jul 2024 - share enumeration, samba-dcerpcd, variable %i

hi, samba team and other,

client software calls samba and samba reads /etc/samba/smb.conf where 
some parameter contains variable %i (client ip address), but when samba 
calls samba-dcerpcd, it again reads /etc/samba/smb.conf where some 
parameter contains variable %i and at that moment %i is not client ip 
address, it is equal 0.0.0.0

for example I need client ip1 and client ip2 to get different shares 
lists (include = /etc/samba/shares-%i.conf), I can't do that because the 
folder list is received via samba-dcerpcd

best regards,
Valery

Am 29.07.24 um 13:20 schrieb Zhuchenko Valery via samba:
> hi, samba team and other,
> 
> client software calls samba and samba reads /etc/samba/smb.conf where 
> some parameter contains variable %i (client ip address), but when samba 
> calls samba-dcerpcd, it again reads /etc/samba/smb.conf where some 
> parameter contains variable %i and at that moment %i is not client ip 
> address, it is equal 0.0.0.0
> 
> for example I need client ip1 and client ip2 to get different shares 
> lists (include = /etc/samba/shares-%i.conf), I can't do that because
the
> folder list is received via samba-dcerpcd

How about using the "hosts allow" parameter? It can be specified per
share.

Regards

Christian

Am 2024-07-29 um 13:20 schrieb Zhuchenko Valery via
samba:
> hi, samba team and other,
> 
> client software calls samba and samba reads /etc/samba/smb.conf where 
> some parameter contains variable %i (client ip address), but when samba 
> calls samba-dcerpcd, it again reads /etc/samba/smb.conf where some 
> parameter contains variable %i and at that moment %i is not client ip 
> address, it is equal 0.0.0.0
> 
> for example I need client ip1 and client ip2 to get different shares 
> lists (include = /etc/samba/shares-%i.conf), I can't do that because
the
> folder list is received via samba-dcerpcd
Hi,

this is likely another variation of 
https://bugzilla.samba.org/show_bug.cgi?id=15488 .
According to Volker's comment fixing this seems to be non-trivial.
Probably because the communication between the processes is not very 
well documented and not many people are familiar with this part of the 
samba sources.

regards,
Franz