On Tue, Mar 22, 2011 at 02:26:05PM +0100, Marcus M|lb|sch wrote: > Am 22.03.2011 13:57, schrieb Marcus M|lb|sch: > > Duh! > > Now the machine replies with the correct MAC-address: > > >14:19:01.314759 arp who-has 192.168.3.1 tell 192.168.3.205 > >14:19:01.314785 arp reply 192.168.3.1 (01:00:5e:00:01:21) is-at > >01:00:5e:00:01:21 > > I did restart networking again and did restart pf again. However, I > feel that was unrelated, since the pings started to work sometimes > afterwards. > > Now I wonder: > > Did the FW change its virtual MAC-address sometimes today? Maybe > after the last netstart, and I didn't notice at first, since I was > connected via the physical address? > > How could that happen? Will it happen again? > > Which cache did serve the wrong MAC-Address? Was it the switch? > > Is there any way in which I can tell the FW to use a specific > virtual MAC-address when carping? >
Welcome to the wonderful world of switches and their MAC address tables. I bet that the switch still had an old entry for the 01:00:5e:00:01:85 address in the table and it took a while until the entry was cleared. I did not look to closely at carp IP & ARP balancing but I have the feeling that carp is not aggressive enough to promote new MAC addrs it becomes responsible for and therefor switches fail to update their table. -- :wq Claudio
