PfSense conflict with Efa Project (Email Filter Appliance)?



  • Hi,

    I was wondering if anyone knows if there is a known issue with running PfSense and EFA (Email Filter Appliance) - https://efa-project.org/.

    I am finding that when we have EFA running our gateway connection in PfSense goes offline, as soon as we turn the vm that has EFA running off the gateway connection comes back online.

    We would like to use EFA as our Email spam filter.'

    Thanks,
    Sunny


  • Netgate Administrator

    Nothing I'm aware of. Sounds like you have an IP conflict. Check the pfSense logs.

    Steve



  • @stephenw10

    Hi in the gateway logs I only see the following errors:

    Mar 4 11:44:28	dpinger		WAN_DHCP 99.242.198.1: Clear latency 17729us stddev 46794us loss 5%
    Mar 4 11:44:29	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 15501us stddev 3485us loss 6%
    Mar 4 11:44:59	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 14347us stddev 12576us loss 22%
    Mar 4 11:44:59	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 15723us stddev 4567us loss 22%
    Mar 4 11:45:16	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 6247349us stddev 11415999us loss 34%
    Mar 4 11:45:16	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 7814713us stddev 11641832us loss 27%
    Mar 4 11:46:03	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 26342us stddev 81432us loss 20%
    Mar 4 11:46:08	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 16712us stddev 6352us loss 15%
    Mar 4 11:46:12	dpinger		WAN_DHCP 99.242.198.1: Clear latency 18392us stddev 46320us loss 7%
    Mar 4 11:46:14	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 16623us stddev 6140us loss 5%
    Mar 4 11:46:43	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 16784us stddev 7267us loss 21%
    Mar 4 11:46:44	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 21354us stddev 67226us loss 21%
    Mar 4 11:47:01	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 6653285us stddev 11558143us loss 32%
    Mar 4 11:47:02	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 8006668us stddev 11820620us loss 28%
    Mar 4 11:47:49	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 19493us stddev 50887us loss 20%
    Mar 4 11:47:53	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 15868us stddev 5562us loss 15%
    Mar 4 11:47:59	dpinger		WAN_DHCP 99.242.198.1: Clear latency 18662us stddev 46827us loss 5%
    Mar 4 11:47:59	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 15898us stddev 5684us loss 5%
    Mar 4 11:48:29	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 15524us stddev 4200us loss 21%
    Mar 4 11:48:30	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 22125us stddev 67376us loss 21%
    Mar 4 11:48:45	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 5385741us stddev 10447759us loss 31%
    Mar 4 11:48:45	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 7471539us stddev 11008594us loss 23%
    Mar 4 11:49:34	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 82815us stddev 185956us loss 67%
    Mar 4 11:49:48	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 8806504us stddev 10563517us loss 8%
    Mar 4 11:50:19	dpinger		WAN_DHCP 99.242.198.1: Clear latency 18880us stddev 45081us loss 5%
    Mar 4 11:50:23	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 16982us stddev 8742us loss 0%
    Mar 4 11:50:49	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 16014us stddev 4392us loss 21%
    Mar 4 11:50:49	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 21781us stddev 67816us loss 22%
    Mar 4 11:51:06	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 6599282us stddev 11663636us loss 33%
    Mar 4 11:51:07	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 8530636us stddev 11852054us loss 25%
    Mar 4 11:51:55	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 18049us stddev 43596us loss 20%
    Mar 4 11:52:00	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 15357us stddev 3927us loss 12%
    Mar 4 11:52:04	dpinger		WAN_DHCP 99.242.198.1: Clear latency 17701us stddev 40726us loss 5%
    Mar 4 11:52:04	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 15375us stddev 3923us loss 5%
    Mar 4 11:52:34	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 13526us stddev 12579us loss 22%
    Mar 4 11:52:35	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 15889us stddev 4627us loss 22%
    Mar 4 11:52:51	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 6566698us stddev 11673536us loss 33%
    Mar 4 11:52:52	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 8497724us stddev 11966977us loss 25%
    Mar 4 11:53:40	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 31312us stddev 100983us loss 19%
    Mar 4 11:53:45	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 16690us stddev 15098us loss 13%
    Mar 4 11:53:48	dpinger		WAN_DHCP 99.242.198.1: Clear latency 17276us stddev 40888us loss 7%
    Mar 4 11:53:50	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 16555us stddev 14466us loss 5%
    Mar 4 11:54:19	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 14940us stddev 3428us loss 22%
    Mar 4 11:54:20	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 23175us stddev 76800us loss 21%
    Mar 4 11:54:36	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 7530366us stddev 11233442us loss 26%
    Mar 4 11:54:36	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 6125792us stddev 10992671us loss 32%
    Mar 4 11:55:24	dpinger		WAN_DHCP 99.242.198.1: Alarm latency 121012us stddev 230287us loss 65%
    Mar 4 11:55:38	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Alarm latency 8998240us stddev 10811336us loss 8%
    Mar 4 11:56:08	dpinger		WAN_DHCP 99.242.198.1: Clear latency 21098us stddev 51299us loss 7%
    Mar 4 11:56:13	dpinger		WAN_DHCP6 2607:f798:18:10:0:640:7125:5204: Clear latency 16942us stddev 8519us loss 0%
    

    Unless I should be looking in different logs.


  • LAYER 8 Netgate

    Check the system log. Also might help to have a diagram of how it is all supposed to go together.


  • Netgate Administrator

    Yup, the only way I can see loss like that happening just be booting a VM is if it's trying to use the same IP pfSense is.

    If that is happening the system log will be full of warnings.

    Steve


Log in to reply