Over a week late to this thread, but for the archives: If you don't want the new hobby of managing snort outside of PF, you ought to be able to set your monitor interface to a bonding interface, bond0 instead of eth0. Then you have no PacketFence software issue.
You *do* potentially have a hardware issue, in that you will not be able to set different IP addresses and send traffic from the bonded components, suggesting dedicated interfaces, though you could overcome this with VLAN sub-interfaces. On RHEL/CentOS, you configure a bonding interface like this. Sub-interfaces are specified like DEVICE=eth3.20 and VLAN=yes. # cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static HWADDR=12:34:56:78:9A:01 ONBOOT=yes MASTER=bond0 SLAVE=yes NM_CONTROLLED="no" # cat /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 BOOTPROTO=static HWADDR=12:34:56:78:9A:02 ONBOOT=yes MASTER=bond0 SLAVE=yes NM_CONTROLLED="no" # cat /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet BONDING_OPTS="" -- Rich Graves http://claimid.com/rcgraves Carleton.edu Sr UNIX and Security Admin ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
