On 20/02/16 13:52, Stuart Henderson wrote:
Are the carp interfaces "up" (i.e. master) when you see these messages?
Yes always.
On both firewalls I have net.inet.carp.log=3 and I haven't logged any
carp up/down - MASTER/BACKUP transition messages.
On the other hand, on backup firewall I just noticed relevant? messages
but on different times and no other sign that it became the MASTER.
Feb 9 12:58:54 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 9 16:41:58 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 11 10:16:37 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 11 18:32:21 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 15 10:31:01 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 16 12:06:10 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 17 16:45:06 backup_fw2 dhcrelay: send_packet: Network is unreachable
Feb 18 09:19:11 backup_fw2 dhcrelay: send_packet: Network is unreachable
So it looks it's related to carp because the backup fw shouldn't have
relay the dhcp requests from clients but for some unknown reason it did...
How can I make the warning() to print carp/interface status?
I did the following to print interface name:
diff -u -p -r1.10 bpf.c
--- bpf.c 7 Feb 2016 00:49:28 -0000 1.10
+++ bpf.c 20 Feb 2016 12:53:02 -0000
@@ -299,7 +299,7 @@ send_packet(struct interface_info *inter
result = writev(interface->wfdesc, iov, 2);
done:
if (result == -1)
- warning("send_packet: %m");
+ warning("send_packet: %m on %s", interface->name);
return (result);
}
Thanks!
G
