RE: [webmin-l] Webmin Servers, Broadcast/scan

[Jamie C. <jca...@we...>]

On 16/Feb/2006 13:13 Neal Morgan wrote ..
> Jamie:
> 
> Short answer: ethereal shows it still using port 10000 for broadcast.
> 
> Long answer: I first set the UDP port to 6789, ran a netstat to confirm
> a listener was in place there are none existed on 10000, then ran the
> broadcast.

I looked into this some more, and found the cause of this problem - the sending
server isn't properly getting the UDP port to send to from it's own configuration.
The work-around is to add the line 

listen=6789

to the file /etc/webmin/servers/config on the sending system.
 
> On the multihome: the IPs resolve to different hosts and FQDNs.  
> 
> Both servers have 2 NICs:
> 
> 10.X.X.X/255.255.255.0 
> 66.X.X.X/255.255.255.224
> 
> Webmin broadcasts correctly to the expected two network addresses:
> 
> 10.X.X.255 
> 66.X.X.223
> 
> But it also adds in a broadcast to all networks, and a broadcast to the
> 10 net as a class A:
> 
> 255.255.255.255
> 10.255.255.255
> 
> Ethereal shows the 10.255.255.255 ignored (not on my network), the
> 10.x.x.255 received by the first NIC, and the 66.X.X.223 and
> 255.255.255.255 received by the second NIC.
> 
> So - it should receive 3 responses.  Somehow, it is already de-duping
> them and concluding there are 2 new servers to add.  I'm OK with that -
> except it uses the same host name and port for both.  So, there is
> nothing I can see from the edit screen that indicates why it thinks they
> are different.  
> 
> Furthermore, if I broadcast again, I would expect it to either re-add
> both, or add nothing.  Instead, it adds just one of them!  Every new
> broadcast adds one more server with the same name, same config settings.
> 
> 
> Hope that helps and wasn't too much information.

Ok, I see what is going on how - Webmin isn't handling a packet being
received twice from the same address in the same scan. This will be fixed
in the next release though.

 - Jamie