On Tue, Aug 16, 2005 at 11:00:11AM -0700, Jon Simola wrote:
My thinking (and I read through the dhcpd/carp code to try and verify
this) is that the carp interface doesn't receive all broadcast packets
(except arp), so the dhcp would have to be listening on the vlan
device. I did some tcpdump'ing on various interfaces to check that
out, and the dhcp requests were visible on the physical em1 and
vlan130 interfaces, but not the carp130 device.
This is exactly the behaviour I saw.
After further experimentation, the following seems to work:
/etc/hostname.vlan100
vlan 100 vlandev em1
inet 10.1.100.2 0xffffff00
/etc/hostname.carp100
vhid 100 pass editted carpdev vlan100
inet 10.1.100.1 0xffffffff
(with the hostname.vlan100 address changed on the other machine)
provided I run dhcpd on the vlan interfaces, not on the carp ones.
In other words, I moved the /24 subnet from the carp to the vlan, and
the single address from the vlan to the carp. I could then get an
address via dhcpd and slogin to the carp address just fine.
--
Christopher Vance
