jesus at omniti
Aug 21, 2002, 12:21 PM
Post #2 of 2
(832 views)
Permalink
|
|
possible bug in assignment of broadcast address in v1.2.0
[In reply to]
|
|
Jay West wrote:
>Interesting... anyone have thoughts on this?
>
>System A
>int fxp0 192.168.75.22 255.255.255.0
>vip 192.168.75.100
>of 192.168.75.100-101
>netmask 255.255.255.255
>
>System B
>int fxp0 192.168.75.23 255.255.255.0
>vip 192.168.75.101
>of 192.168.75.100-101
>netmask 255.255.255.255
>
>If I fail system B, system A correctly takes over the IP address of B and
>all is well. However, if I fail system A, then system B does take over the
>.100 address, but look at this from system B when A is failed...
>
>fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.75.23 netmask 0xffffff00 broadcast 192.168.75.255
> inet 192.168.75.101 netmask 0xffffffff broadcast 192.168.75.255
> inet 192.168.75.100 netmask 0xffffffff broadcast 152.0.5.14
> ether 00:e0:81:22:2b:20
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
>
>Look at that broadcast address!? 152.0.5.14? If I fail system B, then when
>system A takes over the .101 address, the broadcast address is
>192.168.75.255 as it should be. This is reproducable. Any thoughts???
>
>
If this were to be fixed... It would only be fixed in the development
branch. So, please reproduce the error on the latest checkout of
wackamole CVS (HEAD branch) and I will take it from there.
--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
|
