You are here

Notes on Netgear GS105Ev2

13 posts / 0 new
Last post
WU2S's picture
Notes on Netgear GS105Ev2

In order to save and restore switch configurations on the Netgear GS105Ev2 switch, you must use the latest version of the switch firmware AND the latest version of the ProSafe Utility. 

First, download the ProSafe Utility from the Netgear downloads page - version 2.3.5 - unzip and install.

Next, download the current firmware from the Netgear GS105Ev2 download page - version

Lastly, install the new firmware with the new ProSafe Utility. These latest version fix a bug that prevented restoring switch configurations.

When this is completed, you will be able to save and restore the switch configurations available in the AREDN Software section.

Netgear GS105Ev2 config files not restoring

I am a new AREDN user trying to set up my ProSafe switch using the pre-made configurations. I have the GS105Ev2. I visited the AREDN site and downloaded the config that I think will be most useful for me, which is "GS105Ev2_3-1-1.cfg" (3 LAN, 1 NODE, 1 WAN). I downloaded the most recent version of the ProSafe Utility noted above and updated the switch firmware to the latest (V1.4.0.2).

When I try to upload the .cfg file to the switch, the switch does not accept the config file and gives the error "Configuration restore failure!". I have tried several of the GS105Ev2 config files, in case it was only the 3-1-1 file was not working. None work, same result: "Configuration restore failure!"

Would it just be easier to configure the VLAN settings by hand? Do you have a "cheat sheet" for this? Maybe screenshots from the browser showing the configuration settings so people can make the changes by hand?

Thanks in advance for any assistance.

KE2N's picture

It did not work (last week) for me either. Forced me to figure it out (sort of).

What would be really handy are screen shots of those three sub-menus under 802.1Q/Advanced, for a couple of configurations




AE6XE's picture
The current pre-made

The current pre-made configurations for the GS105Ev2 switch are likely built on top of a less-than-current version of the firmware on the switch.  This is on me as I didn't check the firmware at the time I created these pre-built configurations and should have.    I don't have access to the switch anymore and we won't be able to inspect what GS105Ev2 firmware version was used until 1st week in Dec.   Sorry about that folks, we'll get the site updated with the compatible switch firmware as soon as we can.   Looks like over time we'll need pre-built configs for switch, switch hardware version, AND switch firmware version.  Hopefully, netgear won't be releasing new firmware versions every day :) .

AE6XE's picture
I can't reproduce this issue.

I can't reproduce this issue.   Can you please check the "System->Status->Switch Information" page?   what firmware version is showing--attach a screen shot?    I was able to load the .cfg files available on this website in to a GS105Ev2 for both firmware versions 1) V1.4.0.2 and 2) V1.3.0.3  (the current and prior version.)



Screenshots from both the newest version of ProSafe Plus Utility ( and from the switch web interface (using latest version of Chrome).

I'm happy to meet up if you want to try the switch in person. Email me directly, just reply to that thread we already have going.

Image Attachments: 
AE6XE's picture
KI6VPB,  can you send me a

KI6VPB,  can you send me a backup .cfg file created from your netgear GS105Ev2?    We're in unknown territory here as the .cfg files may not be transportable across netgear devices, even if both have the same firmware version.   This may have something to do with the history of upgrading firmware versions on the device.   I want to bring up the .cfg files from your system and mine in a hex editor and hope I can spot something that will clue us in to what is going on.   Can you also send me the exact .cfg that fails to load on your netgear -- just in case it somehow got changed?       thus send me a .cfg that works and one that does not on your device.  I'd expect the reverse in loading on mine netgear...

<callsign> at

Thanks for helping to get to the bottom of this. 

Joe AE6XE   

Switch configs sent. For the

Switch configs sent. For the saved config from my switch, I just defaulted the switch settings, then saved the CFG file. That way, maybe you can default the settings in yours, and have an apples-to-apples set of settings to compare.

I also did a quick test with Firefox and Chrome, downloading the CFG file from the website in each browser. A binary comparison shows the same file from each, so it's not an issue of the browser mangling the file.

Let me know what else I can provide.

K5DLQ's picture
I'll need to check the backup

I'll need to check the backup files.  I wonder if they were made with 1.3.x firmware....

Anyway, there is a How-To on configuring a switch manually:



@K5DLQ - Thanks for the

@K5DLQ - Thanks for the manual configuration link, it's even the config I was most interested in using. I'll read through it and see if it makes sense.

Config for two nodes

do you happen to have this illustration for two nodes? It seems like it should be very straight forward but I am missing something.

Do you have a config for a tough witch with three nodes and two LANs?

Nevermind. I got it.

Are smart switches necessary?

Basic question: are "smart" LAN switches even necessary?

An AREDN/Broadband Hamnet node uses three VLANs on its LAN port: default (untagged), 1 and 2. The default (i.e., untagged) VLAN serves local computers. The node runs a DHCP server on this VLAN, so you can plug in an ordinary computer and it will "just work".

VLAN 2 is used for linking two or more nodes. An ordinary client computer will simply ignore any traffic on VLAN 1 unless it has been explicitly configured to use it. DHCP is not used.

VLAN 1 is used to talk to an "upstream" ISP, such as a cable or DSL modem (or another LAN served by one) to access the outside Internet and/or create tunnels over it to remote mesh nodes. The node runs a DHCP client on this VLAN. Again, an ordinary computer will simply ignore any traffic on VLAN 1 unless it has been explicitly configured to use it.

An ordinary "dumb" (unmanaged) switch simply passes all Ethernet frames unmodified, including any VLAN tags. So it seems to me that the only time you really need a smart (managed) switch is when you want to use VLAN 1 to talk to an upstream network that expects untagged traffic. Then you'd use the switch to translate VLAN 1 tags on the mesh node port to/from untagged traffic on the upstream network port, and to not pass untagged or VLAN 2 traffic to the upstream network.

If the Ubiquiti nodes had more than one physical Ethernet port, VLANs wouldn't even be necessary. The main purpose of a VLAN is to control where broadcasts go, and this is especially important with DHCP since the mesh node acts as a DHCP client on one VLAN while it's a DHCP server on another, and you must keep these separate. The nodes also broadcast other types of information such as ARP (Address Resolution Protocol) and OLSR "Hello" packets, but it wouldn't hurt to send these to the client or upstream networks because they'd just be ignored except by other mesh nodes.

AE6XE's picture
The Doc section shows a usage

The Doc section shows a usage of non-802.1q (aka 'dumb' switch) configuration: .    I was bit a couple of times when I re-purposed the node and forgot the LAN DHCP,function and been turned off in this configuration--the negative of this approach.    Be sure to check out the Ubiquiti AirRouter supported in beta. It has 5 ports, including WAN, DTDLink, and 3 LAN ports for not too much more cost than a smart switch--ballpark of $50 total new. 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer