David Goldsmith <dgoldsmith <at> sans.org> writes:
> I believe the "inet" option is missing a 3rd component. After the
> CARP IP and the netmask, you also need the 'last' IP for the subnet,
> in your case it would be 213.133.66.71 (on both servers).
>
> On our servers, we have something like:
>
> inet 10.3.2.1 255.255.255.0 10.3.2.255
I have never needed to manually configure the broadcast address before
on unix. Indeed according to
ifconfig vlan119 it has correctly worked it out:
carp119: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6>
mtu 1500
lladdr 00:00:5e:00:01:77
priority: 0
carp: MASTER carpdev vlan119 vhid 119 advbase 1 advskew 10
groups: carp
status: master
inet 213.133.66.67 netmask 0xfffffff8 broadcast 213.133.66.71
I have now removed the trunking to see if that affected it, but no
joy. So I now have:
bnx0: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu
1500
lladdr 00:10:18:d2:d3:ec
priority: 0
media: Ethernet autoselect (1000baseT full-duplex)
status: active
vlan119:
flags=28943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,NOINET6>
mtu 1500
lladdr 00:10:18:d2:d3:ec
description: Scottles Server
priority: 0
vlan: 119 priority: 0 parent interface: bnx0
groups: vlan
status: active
inet 213.133.66.65 netmask 0xfffffff8 broadcast 213.133.66.71
carp119: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6>
mtu 1500
lladdr 00:00:5e:00:01:77
priority: 0
carp: MASTER carpdev vlan119 vhid 119 advbase 1 advskew 10
groups: carp
status: master
inet 213.133.66.67 netmask 0xfffffff8 broadcast 213.133.66.71
I still see the number of IPv4 packets sent increasing according to
netstat -s -p carp, but according to
both tcpdump and netstat there are no packets being transmitted on the
vlan119 or bnx0 interfaces.
If I remove the vlan part and just have the carp interface on top of
bnx0 then I see carp packets on bnx0
with tcpdump as I'd expect. So clearly there is a serious bug
somewhere about sending carp packets over
vlan interfaces. :(
-Matt
