In the experimental 0.4.17-3 version of piranha, you added a feature to
allow a network mask along with the virtual server IP, instead of assuming
a classfull mask, which is a much needed feature. However, it still
calculates the broadcast address according to the classful mask, which
really doesn't seem to cause a problem, as the LVS router itself, in a
direct routing or NAT setup, should never try to reply to a packet from
that address. It could possibly cause problems in a tunneling setup,
I would have thought ifconfig defaulted to the netmask settings for broadcast.
We'll check into it...
That's what I thought too, but when I tested ifconfig yesterday, if you don't
specify a broadcast address, it assumes a classful netmask when calculating the
broadcast. So it's really a glitch in ifconfig, but you can work around it.
I'm in the process of adding the extra code to calculate the broadcast address
broadcast = ( VIP & netmask) | ~netmask ;
I didn't spot ifconfig not calculating the broadcast for itself because I was
using a 255.255.255.0
0.4.17-4 should be out tonight or tomorrow (depending on how god/bad the offsite
company meeting goes.
This issue is now resolved with piranha-0.4.17-4
which you can pick up out of the HA download area