[Fli4l_dev] fli4l 4.0-testing 43670 und samba_lpd

[Thomas Bork]

Am 28.12.2015 um 22:11 schrieb Stefan Sauer:

> Laut https://www.samba.org/~tpot/articles/multiple-interfaces.html
> werden der "Variablen" interfaces Gerätenamen wie eth1 oder eth2
> zugewiesen und nicht IP-Adressen samt Subnetzmasken

interfaces (G)

     This option allows you to override the default network interfaces 
list that Samba will use for browsing, name registration and other 
NetBIOS over TCP/IP (NBT) traffic. By default Samba will query the 
kernel for the list of all active interfaces and use any interfaces 
except 127.0.0.1 that are broadcast capable.

     The option takes a list of interface strings. Each string can be in 
any of the following forms:

         a network interface name (such as eth0). This may include 
shell-like wildcards so eth* will match any interface starting with the 
substring "eth"

         an IP address. In this case the netmask is determined from the 
list of interfaces obtained from the kernel

         an IP/mask pair.

         a broadcast/mask pair.

     The "mask" parameters can either be a bit length (such as 24 for a 
C class network) or a full netmask in dotted decimal form.

     The "IP" parameters above can either be a full dotted decimal IP 
address or a hostname which will be looked up via the OS's normal 
hostname resolution mechanisms.

     By default Samba enables all active interfaces that are broadcast 
capable except the loopback adaptor (IP address 127.0.0.1).

     The example below configures three network interfaces corresponding 
to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The 
netmasks of the latter two interfaces would be set to 255.255.255.0.

     Default: interfaces =

     Example: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0


Ich habe das Paket vor langer Zeit so gestrickt, dass in der Variable 
interfaces IPs/Netzmasken stehen. Damals gab es aber auch

SAMBA_BIND_ALL='no'
SAMBA_BIND_IPV4_1='IP_NET_4'
SAMBA_BIND_IPV4_N='1'
SAMBA_BIND_IPV6_N='0'

noch nicht. Vermutlich sitzt da ein Fehler in den (von anderen) 
überarbeiteten Skripten.

-- 
der tom
[eisfair-team]