Maciej Uhlig: > > PF VM boots with one network interface which is eth3 instead of eth0. > eth3 is down and doesn't get IP address from VB DHCP server. > > Why not the intended interface is assigned by VB? Any hints?
Actually I'm able to answer this question. There is a file in PacketFence VMware image: /etc/udev/rules.d/70-persistent-net.rules which contains descriptions of ethernet interfaces eth0, eth1, eth2 and eth3. VirtualBox assigns ethernet interface to eth3. One need to delete eth0, eth1, and eth2 descriptions and edit eth3 description to be eth0. Then shutdown VM. After reboot, eth0 only is present. As far as lack of eth0 IP address is concerned, this is due to a bug in OS /sbin/dhclient. These remarks are of minor importance, for the records only, I'll even don't file bug reports, developers eventually may take it into account. MU
smime.p7s
Description: Kryptograficzna sygnatura S/MIME
------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
