Philippe, On Tue, May 24, 2011 at 1:43 AM, DOMINEAUX Philippe <[email protected]> wrote: > I had the same trouble in upgrading packetfence. > The solution I've found is to set the NIC parameters like this : > > BOOTPROTO=dhcp > > After changing that I can now find the eth1 in configurator.pl > > I hope it could help. > > Philippe Domineaux > Administrateur Réseau - Network Administrator
I agree that there are ways around it. The reason that changing to BOOTPROTO to dhcp works is the interface gets an IP if the interface has an IP it is visible to packetfence. I am saying that this behavior is not correct when dealing with a monitor interface it should display all interfaces available not just the ones with IP's assigned to them. -- _ /-\ ndrew Niemantsverdriet Academic Computing (406) 238-7360 Rocky Mountain College 1511 Poly Dr. Billings MT, 59102 ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
