NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chirpa
Mar 07, 2009Luminary
Running VirtualBox VM host on ReadyNAS Pro
What is VirtualBox?
So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
With the OS booted up and just sitting at the desktop, top reports:
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
# Creating the Virtual Machine.
$ VBoxManage createvm -name "Windows2003" -register
$ VBoxManage modifyvm "Windows2003" -memory "1024MB" -acpi on -boot1 dvd -nic1 nat
$ VBoxManage createvdi -filename "/c/backup/VirtualBox/Windows2003.vdi" -size 10000 -register
$ VBoxManage modifyvm "Windows2003" -hda "/c/backup/VirtualBox/Windows2003.vdi"
$ VBoxManage registerimage dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxManage modifyvm "Windows2003" -dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxHeadless -startvm "Windows2003" &
# Connected via Remote Desktop at this point.
# After the installation, first page requires Ctrl-Alt-Del, so I sent the keycodes.
$ VBoxManage controlvm "Windows2003" keyboardputscancode 1d 38 53
# System is up and running, time to install GuestAdditions for better video, etc.
$ wget http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage registerimage dvd /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage controlvm "Windows2003" dvdattach /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
With the OS booted up and just sitting at the desktop, top reports:
top - 16:17:10 up 1 day, 17:58, 1 user, load average: 0.00, 0.01, 0.00
Tasks: 93 total, 1 running, 92 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.7%us, 0.2%sy, 0.0%ni, 99.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2072432k total, 2020100k used, 52332k free, 6120k buffers
Swap: 1048536k total, 144k used, 1048392k free, 784620k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10297 root 20 0 1104m 1.0g 4720 S 4 52.5 57:31.53 VBoxHeadless
12792 root 20 0 46092 9520 1720 S 1 0.5 59:54.51 motion
12196 root 20 0 9196 7688 980 S 0 0.4 0:57.72 wastesrv
1 root 20 0 1948 600 508 S 0 0.0 0:01.30 init
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
$ mkdir /lib/modules/`uname -r`/miscOr, if you want to compile the kernel modules yourself:
$ cd /lib/modules/`uname -r`/misc
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxdrv.ko
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxnetflt.ko
$ echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.list
$ wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
$ apt-get update
$ apt-get install virtualbox-2.1
$ /etc/init.d/vboxdrv start
envyious:/c/backup# echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.listInstall of VirtualBox 2.2.2, before Sun updates the Debian Repository...
envyious:/c/backup# wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
envyious:/c/backup# apt-get update && apt-get install build-essential
...
Setting up build-essential (11.3) ...
envyious:/c/backup# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
envyious:/c/backup# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
envyious:/c/backup# cd GPL/linux-x86-2.6/
envyious:/c/backup/GPL/linux-x86-2.6# make && make prepare
...
envyious:/c/backup/GPL/linux-x86-2.6# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# KERN_DIR=/usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# apt-get install virtualbox-2.1
...
Setting up virtualbox-2.1 (2.1.4-42893_Debian_etch) ...
Adding group `vboxusers' (GID 101) ...
Done.
Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
Starting VirtualBox kernel module: done.
envyious:/c/backup/GPL/linux-x86-2.6# cd
envyious:/c/backup/GPL/linux-x86-2.6# VBoxManage list vms
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
# cd GPL/linux-x86-2.6/
# make && make prepare
# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
# export KERN_DIR=/usr/src/linux
# apt-get install libfontconfig1 libglib2.0-0 libice6 libsdl1.2debian libsm6 libx11-6 libxcursor1 libxext6 libxi6 libxmu6 libxrandr2 libxrender1 libxslt1.1 libxt6 python2.4
# wget -q http://download.virtualbox.org/virtualbox/2.2.2/virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
# dpkg -i virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
Setting up virtualbox-2.2 (2.2.2-46594_Debian_etch) ...
Recompiling VirtualBox kernel module: done.
Starting VirtualBox kernel module: done.
441 Replies
Replies have been turned off for this discussion
- I should have mentioned that I solved the previous issue. I realised I was extracting onto a small partition and filling it up. I changed to /c/VirtualBox and the whole GPL did extract fine.
So the problem must be something else? - XaverTutor@ troypiggo
# VBoxManage setproperty machinefolder "`pwd`"
???
where is your default machine folder set?
you should set it to e.g /c/VirtualBox or something you may have created.
I'm pretty sure that VBox is creating a new drive at the default machine folder if you do not specific a path.
please run this commandVBoxManage showvminfo "Lucid" > Lucid.txt
and check the paths in the first 5 lines and somewhere in the middle of the txt file (look for "IDE Controller (0, 0): ...")
i guess the the Virtual drive for your vbox is created in your root partition and during the install it gets filled till the limit of the partition is reached - jmalmlundAspirant
troypiggo wrote: I should have mentioned that I solved the previous issue. I realised I was extracting onto a small partition and filling it up. I changed to /c/VirtualBox and the whole GPL did extract fine.
So the problem must be something else?
No, not necceseryly...
# VBoxManage setproperty machinefolder "`pwd`"
You set the machinefolder to your current directory when you issued the above command.
The "pwd" command is a short for "print working directory" so if you were in the root-home dir when gave the commands setting up your vm the you're storing the disk-image on the small sys-partition. - Thanks guys. Can't access the machine until Monday, so can't post output to show you. Pretty sure `pwd` was /c/VirtualBox - I know what the command means and was just being lazy. But would like to check in case I did something silly. I usually do type full paths for safety.
Xaver wrote: @ troypiggo # VBoxManage setproperty machinefolder "`pwd`"
???
where is your default machine folder set?
you should set it to e.g /c/VirtualBox or something you may have created.
I'm pretty sure that VBox is creating a new drive at the default machine folder if you do not specific a path.
please run this commandVBoxManage showvminfo "Lucid" > Lucid.txt
and check the paths in the first 5 lines and somewhere in the middle of the txt file (look for "IDE Controller (0, 0): ...")
i guess the the Virtual drive for your vbox is created in your root partition and during the install it gets filled till the limit of the partition is reached
As I suspected (and really, really hoped I was right) above, `pwd` was in fact /c/VirtualBox. Does anything else in here look amiss to those with more experienced VB eyes?Name: Lucid
Guest OS: Ubuntu
UUID: 758b714b-b394-4947-8dde-86aeeba418be
Config file: /c/VirtualBox/Lucid/Lucid.vbox
Snapshot folder: /c/VirtualBox/Lucid/Snapshots
Log folder: /c/VirtualBox/Lucid/Logs
Hardware UUID: 758b714b-b394-4947-8dde-86aeeba418be
Memory size: 1024MB
Page Fusion: off
VRAM size: 32MB
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
RTC: local time
Hardw. virt.ext: off
Hardw. virt.ext exclusive: off
Nested Paging: off
Large Pages: off
VT-x VPID: off
State: powered off (since 2011-06-20T00:20:02.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): /c/VirtualBox/Lucid.vdi (UUID: 363b1622-250e-44c5-931c-9
95b37c45ebe)
IDE Controller (0, 1): /c/downloads/ubuntu-10.04.2-server-i386.iso (UUID: 98b5f
c2b-9d00-4581-9a52-9dc24b7a0907)
NIC 1: MAC: 08002770BF35, Attachment: NAT, Cable connected: on, Trace
: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0
NIC 1 Settings: MTU: 0, Socket( send: 64, receive: 64), TCP Window( send:64, r
eceive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
Audio: disabled
Clipboard Mode: Bidirectional
VRDE: disabled
USB: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Shared folders: <none>
VRDE Connection: not active
Clients so far: 0
Guest:
OS type: Ubuntu
Additions run level: 0
Configured memory balloon size: 0 MB- jmalmlundAspirant
troypiggo wrote:
As I suspected (and really, really hoped I was right) above, `pwd` was in fact /c/VirtualBox. Does anything else in here look amiss to those with more experienced VB eyes?Name: Lucid
Guest OS: Ubuntu
UUID: 758b714b-b394-4947-8dde-86aeeba418be
Config file: /c/VirtualBox/Lucid/Lucid.vbox
Snapshot folder: /c/VirtualBox/Lucid/Snapshots
Log folder: /c/VirtualBox/Lucid/Logs
Hardware UUID: 758b714b-b394-4947-8dde-86aeeba418be
Memory size: 1024MB
Page Fusion: off
VRAM size: 32MB
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
RTC: local time
Hardw. virt.ext: off
Hardw. virt.ext exclusive: off
Nested Paging: off
Large Pages: off
VT-x VPID: off
State: powered off (since 2011-06-20T00:20:02.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): /c/VirtualBox/Lucid.vdi (UUID: 363b1622-250e-44c5-931c-9
95b37c45ebe)
IDE Controller (0, 1): /c/downloads/ubuntu-10.04.2-server-i386.iso (UUID: 98b5f
c2b-9d00-4581-9a52-9dc24b7a0907)
NIC 1: MAC: 08002770BF35, Attachment: NAT, Cable connected: on, Trace
: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0
NIC 1 Settings: MTU: 0, Socket( send: 64, receive: 64), TCP Window( send:64, r
eceive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
Audio: disabled
Clipboard Mode: Bidirectional
VRDE: disabled
USB: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Shared folders: <none>
VRDE Connection: not active
Clients so far: 0
Guest:
OS type: Ubuntu
Additions run level: 0
Configured memory balloon size: 0 MB
Well I'll just quickly dump my webserver info and you can compare for your self ;)
Name: webserver
Guest OS: Ubuntu (64 bit)
UUID: 59eed2f8-b144-475d-3edf-72782b3b198a
Config file: /c/VirtualBox/Machines/webserver/webserver.vbox
Snapshot folder: /c/VirtualBox/Machines/webserver/Snapshots
Log folder: /c/VirtualBox/Machines/webserver/Logs
Hardware UUID: 59eed2f8-b144-475d-3edf-72782b3b198a
Memory size: 256MB
Page Fusion: off
VRAM size: 2MB
HPET: on
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: on
PAE: on
Time offset: 0 ms
RTC: local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging: on
Large Pages: on
VT-x VPID: on
State: running (since 2011-06-24T05:06:57.060000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): SATA Controller
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 10
Storage Controller Bootable (0): on
SATA Controller (0, 0): /c/VirtualBox/Machines/webserver/Ubuntu_64bit.vdi (UUID: f14f9c77-81c7-a20d-9718-de62e221b2c9)
SATA Controller (1, 0): /opt/VirtualBox/additions/VBoxGuestAdditions.iso (UUID: 12be4c39-a20d-81c7-a97a-acf78fdb73ff)
NIC 1: MAC: 080027E26FA7, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Mouse
Keyboard Device: USB Keyboard
UART 1: disabled
UART 2: disabled
Audio: disabled
Clipboard Mode: Bidirectional
Video mode: 640x480x0
VRDE: enabled (Address <ip-addr>, Ports <port>, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
VRDE port: <port>
Video redirection: disabled
VRDE property: TCP/Ports = "<port>"
VRDE property: TCP/Address = "<ip-addr>"
VRDE property: VideoChannel/Enabled = <not set>
VRDE property: VideoChannel/Quality = <not set>
VRDE property: Client/DisableDisplay = <not set>
VRDE property: Client/DisableInput = <not set>
VRDE property: Client/DisableAudio = <not set>
VRDE property: Client/DisableUSB = <not set>
VRDE property: Client/DisableClipboard = <not set>
VRDE property: Client/DisableUpstreamAudio = <not set>
USB: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Shared folders:
Name: 'media', Host path: '/c/media' (machine mapping), readonly
VRDE Connection: not active
Clients so far: 0
Guest:
OS type: Ubuntu_64
Additions run level: 1
Configured memory balloon size: 0 MB - XaverTutorhere is my dump included:
viewtopic.php?p=302193#p302193
sorry i cant see anything wrong either, I am not really more experienced
how much memory do you have in your NAS? - jmalmlundAspirantJust a quick update of the install instructions...
Miniguide on installing/upgrading VirtualBox 4.1.0 on RAIDiator 4.2.17.
Section 1 for new installations,
apt-get update
apt-get install build-essential amd64-libs lib64stdc++6 bzip2 lib64z1 lzma
apt-get --reinstall install libc6-amd64
Section 1 for upgrades,
apt-get update
apt-get -f install
Section 2 for both new installs and upgrades.
mkdir /c/VirtualBox
cd /c/VirtualBox
wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.17_WW_src.zip
unzip -q RNDP6xxx_4.2.17_WW_src.zip "linux-2.6.37.5/*"
ln -snf `pwd`/linux-2.6.37.5 /usr/src/linux
cd linux-2.6.37.5
cp arch/x86/configs/defconfig.smp .config
make ARCH=x86_64 silentoldconfig
make prepare
make modules_prepare
make
make modules
cd ..
wget -q http://download.virtualbox.org/virtualbox/4.1.0/VirtualBox-4.1.0-73009-Linux_amd64.run
wget -q http://download.virtualbox.org/virtualbox/4.1.0/Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
chmod 755 VirtualBox-4.1.0-73009-Linux_amd64.run
Section 3, optional for upgraders, not relevant for new installs.
IF upgraders want to start clean with the install insert this command now to uninstall previous lingering VirtualBox components.
./VirtualBox-4.1.0-73009-Linux_amd64.run uninstall
Section 4, install/upgrade VirtualBox
./VirtualBox-4.1.0-73009-Linux_amd64.run
Section 5, new installs
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
Section 5, for upgrades,
It's to my knowledge not possible to just upgrade the extpack, the old one needs to be uninstalled to allow the new pack to be installed.
/usr/bin/VBoxManage extpack uninstall "Oracle VM VirtualBox Extension Pack"
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
Note that it's the extpack that contains the RDP module...
Xaver added a really nice set of instructions on how to set up a basic virtual machine here, just keep in mind that most ReadyNas'es come with only 1GB ram, don't assign too much to your virtual machines or everything will come to a crawl if heavy memory swapping starts to occur.
Mini FAQ:
1. Are these instructions valid for my ReadyNas of type <insert your Nas here>?
If it has an 64bit intel CPU they should be. (I have a ReadyNas Pro Pioneer so if you have something else, well then your milage may vary and if so, then please help us by posting the specifics for your type of nas.)
2. Why is AMD stuff mentioned when the ReadyNas boxes use Intel cpu's?
Because the cpu is 64bit, more details by sphardy: here
3. A new version is out, (Radiator or VirtualBox), is this guide still valid?
Well, other than that you have to use other links and perhaps extract a newer kernel version than what's suggested herein you can still follow the guide and change to newer versions/links where needed.
ps. I've been thinking that it would be nice if there was a wiki so that it would be easier for anyone to help out keeping the instructions up to date... get in touch if you'd like to be a part of such a wiki-forum. - jmalmlundAspirantJust a word of waring, DON'T update to RAIDiator 4.2.19 yet! The apt-get repository isn't up-to-date and running 'apt-get -f install' will actually remove the some packages required to build the needed VirtualBox kernel modules.
- JeIlMaAspirant
jmalmlund wrote: Just a word of waring, DON'T update to RAIDiator 4.2.19 yet! The apt-get repository isn't up-to-date and running 'apt-get -f install' will actually remove the some packages required to build the needed VirtualBox kernel modules.
Forget to remove autoupdate... So RAIDiator has been upgrade to 4.2.19. Is there some steps that I can make to get this back to business?
-JeIlMa
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!