freevrrpd

Fri Mar 5 02:03:04 PST 2004

And can you please apply this patch and resend me the logs ?

---> CUT <---

--- ../../../freevrrpd/src/vrrp_network.c       Tue Feb 24 11:56:01 2004
+++ vrrp_network.c      Fri Mar  5 10:25:09 2004
@@ -137,7 +137,7 @@
        vrrp_thread_mutex_unlock_bpf();
        if (octets < 0) {
                if (log)
-                       syslog(LOG_ERR, "can't write to bpf socket descriptor 
(pseudo_device bpf not activated in kernel ?)");
+                       syslog(LOG_ERR, "can't write to bpf socket descriptor: 
%s", strerror(errno));
                return -1;
        }
---> CUT <---

Regards,
Sebastien.
-- 
spe at selectbourse.net

On Thursday 04 March 2004 22:42, Brady Klick wrote:
> Here is a log file from my machine. I am running FreeBSD 4.9 and I
> downloaded the latest freevrrpd code from the cvs site. I have dual Intel
> Pro1000 NIC cards so I made the recommended change to the vrrp_moncircuit.c
> file, recompiled and reinstalled. I am still getting the following error. I
> have created 10 bpf devices (in both the kernel and using MAKEDEV). If I
> only have 2 VRIDs setup I don't get any errors. If I have all three I get
> the bpf error after the machine has been up about 4-5 minutes. I thought it
> might be an issue with not enough BPF devices; however, I read that .8.7
> and later uses a single bpf device for all VRIDs. Do you have any
> suggestions?
>
>
> Mar  2 18:29:59 EDIFW1 freevrrpd[141]: initializing threads and all VRID
> Mar  2 18:29:59 EDIFW1 freevrrpd[141]: reading configuration file
> /usr/local/etc/freevrrpd.conf Mar  2 18:30:00 EDIFW1 freevrrpd[141]: send
> ip = 216.250.78.114, eth = 0:4:23:9f:1:26 Mar  2 18:30:00 EDIFW1
> freevrrpd[141]: server state vrid 1: backup Mar  2 18:30:02 EDIFW1
> freevrrpd[141]: send ip = 192.168.50.2, eth = 0:4:23:9f:1:27 Mar  2
> 18:30:02 EDIFW1 freevrrpd[141]: send ip = 192.168.50.1, eth =
> 0:4:23:9f:1:27 Mar  2 18:30:02 EDIFW1 freevrrpd[141]: server state vrid 2:
> backup Mar  2 18:30:03 EDIFW1 freevrrpd[141]: send ip = 192.168.100.2, eth
> = 0:4:23:78:61:64 Mar  2 18:30:03 EDIFW1 freevrrpd[141]: send ip =
> 192.168.100.1, eth = 0:4:23:78:61:64 Mar  2 18:30:03 EDIFW1 freevrrpd[141]:
> server state vrid 3: backup Mar  2 18:30:05 EDIFW1 freevrrpd[141]: send ip
> = 216.250.78.114, eth = 0:0:5e:0:1:1 Mar  2 18:30:05 EDIFW1 freevrrpd[141]:
> send ip = 216.250.78.116, eth = 0:0:5e:0:1:1 Mar  2 18:30:05 EDIFW1
> freevrrpd[141]: server state vrid 1: master Mar  2 18:30:06 EDIFW1
> freevrrpd[141]: send ip = 192.168.50.2, eth = 0:0:5e:0:1:2 Mar  2 18:30:06
> EDIFW1 freevrrpd[141]: send ip = 192.168.50.1, eth = 0:0:5e:0:1:2 Mar  2
> 18:30:06 EDIFW1 freevrrpd[141]: server state vrid 2: master Mar  2 18:30:08
> EDIFW1 freevrrpd[141]: send ip = 192.168.100.2, eth = 0:0:5e:0:1:3 Mar  2
> 18:30:08 EDIFW1 freevrrpd[141]: send ip = 192.168.100.1, eth = 0:0:5e:0:1:3
> Mar  2 18:30:08 EDIFW1 freevrrpd[141]: server state vrid 3: master Mar  2
> 18:34:24 EDIFW1 freevrrpd[141]: can't write to bpf socket descriptor
> (pseudo_device bpf not activated in kernel ?)
>
> Mar  2 18:34:24 EDIFW1 freevrrpd[141]: There is a big problem here !
> Mar  2 18:34:27 EDIFW1 freevrrpd[141]: send ip = 192.168.100.2, eth =
> 0:4:23:78:61:64 Mar  2 18:34:27 EDIFW1 freevrrpd[141]: send ip =
> 192.168.100.1, eth = 0:4:23:78:61:64 Mar  2 18:34:27 EDIFW1 freevrrpd[141]:
> server state vrid 3: backup
>
>
>
> Thanks,
>
> Brady



Les informations contenues dans ce message sont confidentielles et peuvent constituer des informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies, et d en avertir immediatement l expediteur par message de retour....
Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter.
--- ----------------------------------------------------- ---
The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail.
E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result.

