I have VirtualBox working with the PacketFence zen VM that is downloadable from
the PacketFence site.
It took a little tweaking to get the VLANs to show up in the guest VM.
Here is a sloppy bunch of notes that may help if you are determined to stick
with VirtualBox.
---
I needed vlans 290,291,292,390,391 and 392 to be available in the guest VM.
eth0 is the default interface for the VirtualBox host.
On the host that runs VirtualBox, I added the interfaces:
vi ifcfg-eth0.290
vi ifcfg-eth0.291
vi ifcfg-eth0.292
vi ifcfg-eth0.390
vi ifcfg-eth0.391
vi ifcfg-eth0.392
ifup eth0.290
ifup eth0.291
ifup eth0.292
ifup eth0.390
ifup eth0.391
ifup eth0.392
ifcfg-eth0.290 looks like this:
[root@vhost network-scripts]# more ifcfg-eth0.290
DEVICE=eth0.290
VLAN=yes
ONBOOT=yes
BOOTPROTO=dhcp
just edit and copy that to the other ifcfg-eth0.XXX files (these live in
/etc/sysconfig/network-scripts folder)
(does not matter what the IP is on the host for that vlan interface, as long as
it is UP and running)
Then, I attached them to new interfaces on the VirtualBox guest VM
(packetfence). They show up as unique interfaces in the guest VM.
(nic1 is the default nic -> management IP)
VBoxManage modifyvm "PacketFence" --nic2 bridged --bridgeadapter2 eth0.290
VBoxManage modifyvm "PacketFence" --nic3 bridged --bridgeadapter3 eth0.291
VBoxManage modifyvm "PacketFence" --nic4 bridged --bridgeadapter4 eth0.292
VBoxManage modifyvm "PacketFence" --nic5 bridged --bridgeadapter5 eth0.390
VBoxManage modifyvm "PacketFence" --nic6 bridged --bridgeadapter6 eth0.391
VBoxManage modifyvm "PacketFence" --nic7 bridged --bridgeadapter7 eth0.392
boot the Guest VM (packetfence) and log in as root (to the shell prompt)
I added the interfaces (eth2 thru eth7) to the guest VM. In my case, I wanted a
static IP assigned to each of the vlan interfaces.
example:
[root@pf-zen-desktop network-scripts]# more ifcfg-eth3
DEVICE=eth3
# was ifcfg-eth2.290
ONBOOT=yes
BOOTPROTO=static
NM_CONTROLLED=no
IPADDR=10.200.1.10
NETMASK=255.255.0.0
(repeat for each VLAN interface)
Once that is done, edit the packetfence config and change all the vlan
"eth0.290" or whatever vlan references to match the new interfaces
example:
vi /usr/local/pf/conf/pf.conf
(change [interface eth2.290] )
to:
[interface eth3]
ip=10.200.1.10
.
.
.
mask=255.255.0.0
repeat that for each of the VLAN interfaces.
I have been using this setup and it works great with VirtualBox.
----- Original Message -----
From: "Primož Marinšek" <[email protected]>
To: [email protected]
Sent: Thursday, October 18, 2012 4:40:17 AM
Subject: [PacketFence-users] Packetfence in virtual environment
Dear All
I hope I'll not get shut down too fast here, but I've hit a wall.
I'm testing (or would like to) PF to evaluate it and see if we can implement it
into some of our solutions. It looks great on paper so I thought I'd give it a
try.
I've installed PF running on VirtualBox thinking "what could go wrong", but I
found out soon enough that VLANs are the problem. I've been reading of some
workarounds for this, but it seem a waste of time for this.
Is VMware Player any better that VirtualBox at this or is the ESXi the only
solution for this?
I just want to run PF on my ubuntu to give it a try with our WLAN network.
--
Primož Marinšek
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
