Not really best by todays standards, but I am using it (who knows how much longer...)
Barracuda Networks for whatever reason (stupidity?, not enough resources to learn?) do not want to provide the software in VM format (they insisiting on physical appliance - 1U case with desktop board, AMD K7 processor, 512 Mb RAM running bastardized Mandrake kernel 2.4.21)
Of course it is not a problem to convert it to VM Workstation format
Simple free G4L (Ghost 4 Linux) will help
I wonder if it is vital to have VMtools installed
It is bit difficult, as they do not provide any kernel headers that tools installation needs
Anybody can comment on this?
Thanks
Seb
as long as you have the needed drivers installed in your vm for the nic, vmtools are not absolutely required...
homever the main issue will be running in a totally unsupported config, so don't expect any in-depth support from Barracuda if ever needed...
they will know you tampered their install and will use it as an excuse...
I don't know if they use any lock mechanism to be sure their hardware is used such as MAC address checking, specific bios signature ?!
so assuming there's no such protection, running inside a Vm will work but will be totally unsupported by Barracuda...
Sure, I realize it will be unsupported
Yes, they use only MAC for the updates chaeck, but that can (or can it be?) emulated in Vmware (by specyfying the MAC in the vmx file)
Seb
the MAC address range is locked by default in vmware: you can't assign a MAC addres of your choice...
anyway, some folks managed to patch previous versions of vmware W/S to accept any MAC
see here:
http://www.securityfocus.com/archive/119/361360/30/0/threaded
I have no idea if the trick still works with VM W/S 6.0
probably a question for the Workstation forum
But I would not be using WS 6, but ESX
Seb
>But I would not be using WS 6, but ESX
I read in your first post "Of course it is not a problem to convert it to VM Workstation format " so I probably assumed too fast you'll be running VM W/S ![]()
anyway for ESX, I doubt any patching can be done for the MAC issue, but I'll leave the definitive answer to the ESX gurus on the board....
In that case... "Good Bye Barracuda"
Seb
Hi,
Did you get this thing work?
Did you put a barracuda spamfirewall in a VM on vmware Workstation 5?
If yes how did you do that?
I try to do that and I am not able to ping the spam firewall after i put it in to a VM. What is the setting for the virtual nic?
Thanks
Nicolas
I Am Curious about this also.
There must be a way to p2v a barracuda box of any type.
Lets start a new topic possibly and create a "Barracuda Project"
It is a useless piece of software. Ditch it, it is not worth the hardware it runs on.
And its licensing is tied to the MAC address
Just buy Spamtitan
Seb
