"Samba Server neu starten" destroys IP configuration - don't call 'dhcpstrt'

[andi.b@gmx.net]

Fresh install of 'samba-1-3-0-979.wpi'

"Samba Server neu starten" (Restart samba server?) calls DHCPSTRT. Maybe via b4smb.cmd

OS/2 DHCP client does not work reliable on networks with more than one DHCP server and/or more than one interface. So using dhcpstrt is not recommended these days anyway.

Moreover it is not acceptable that samba destroys an IP configuration with fixed IPs.

After clicking object "Samba Server neu starten" my IP configuration ends up with -

lan0: flags=b863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,BRIDGE,SNAP,LOOPBRD>
        inet 172.16.2.112  netmask 0xffffff00 broadcast 172.16.2.255
lan1: flags=b863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,BRIDGE,SNAP,LOOPBRD>
        inet 10.0.2.112  netmask 0xffffff00 broadcast 10.0.2.255
lan2: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
        inet 192.168.1.61  netmask 0xffffff00 broadcast 192.168.1.255

lan2 has been assigned an IP via DHCP (crappy OS/2 DHCP client). Correct configuration on this machine would be lan1: 10.0.2.112 with alias address 192.168.1.112 (not shown). But of course this would conflict with an IP address assigned in the same net the other interface lan2:.

Correct IP configuration -

lan0: flags=b863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,BRIDGE,SNAP,LOOPBRD>
        inet 172.16.2.112  netmask 0xffffff00 broadcast 172.16.2.255
lan1: flags=b863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,BRIDGE,SNAP,LOOPBRD>
        inet 10.0.2.112  netmask 0xffffff00 broadcast 10.0.2.255

Alias address for lan1: 192.168.1.112. But they are never shown with ifconfig. At least I don't know how. lan2: is used here only with wireless networks which is usually not enabled (and was not enabled until samba messed around with interface configuration).

Bottom line - never use OS/2 dhcp client (DHCPSTRT)!

Never use any dhcp client (including ISC dhclient) with samba objects. Never with systems which are configured with fixed IPs. Moreover this would collide with xwlan/wireless setups which uses ISC dhclient in parallel.

[Herwig Bauernfeind]

This issue has already been fixed in b4smb.cmd in changeset #994.

[andi.b@gmx.net]

Current wpi includes this bug. When will be a fixed package available?