Hi all,
Looking for some help setting up a Netgear GS108Tv2 switch. I’ve read and read about all this but just can’t seem to get my arms around it. Here’s the situation:
- Equipment is installed in an Anchorage hospital.
- There are currently two AREDN nodes on 3.4 GHz to be connected. We might add up to two or three more nodes on 3.4 or otherwise. There are actually a total of five runs of Cat5e from the roof of the facility into the EOC in the basement where the station is. Of course, just two of these runs are currently in use, one for each of the 3.4 nodes.
- There are two desktop computers to connect to this network. They should both get full access to the MESH as well as to “each other”.
- We’ll want to be adding a VOIP phone to the system.
- I’m hoping to add a wifi access point. I have a Ubiquiti AirRouter I was simply hoping to plug into the switch to add that capability.
- I DO NOT anticipate that the hospital will allow feeding of their internet to our network. Any internet access will come from the mesh from other sources.
Can someone please hold my hand through the switch setup process? I’ve already updated the firmware on the switch, but the rest is Greek to me. I've tried to understand this concept of VLANs, etc., but I'm too new to this and time is short, thus need some help.
The 3.4 GHz nodes are already on the roof and installed. All of the inside station gear, mesh and otherwise, is to be installed this Friday. Was hoping to be ready to plug and play.
Thanks,
Kent Petty, KL5T
District Emergency Coordinator, Anchorage
VLAN 1 is always the management VLAN and all ports (1-8) should be tagged (T).
VLAN 2 is always the device-to-device (DtD) linking VLAN, so the ports that you will use for AREDN nodes should be tagged on this VLAN. Let's say ports 1 thru 5 are tagged (T) and the remaining ports are excluded. This lets you plug your first two nodes into ports 1 & 2, and then add up to 3 more nodes to ports 3 thru 5 as you implement them.
VLAN 11 is the the VLAN you use to connect the AREDN node in port 1 to other devices in ports 6 thru 8, such as laptops, cameras or VoIP phones. In this VLAN Port 1 is untagged (U) and ports 6 thru 8 are also untagged (U) so the devices in ports 6-8 will get DHCP issued IP addresses from the node in port 1. Ports 2 thru 5 are excluded.
While I do not have this particular NetGear switch, I do have a GS108E and the setup should be similar. If you need a screen capture of the setup, please ask.
-Randy
Hi Randy,
Thanks for that input. What you are conveying to me generally makes sense, but when I try to translate the instruction to application within the switch interface, I just get lost. The interface I see doesn't actually resemble the examples I'm seeing on the other threads, hence my confusion. I can't tell what I'm supposed to leave alone and what I'm supposed to edit.
Probably going to have to a do a remote desktop session somehow with somebody to work this out. I'm set up with Chrome Remote Desktop and/or TeamViewer if you're game.
Thanks,
Kent
I just purchased one of these switches and although I've read through the GS105E setup on the website and the info in this thread, this VLAN business is new to me. I would certainly appreciate it if you could email me or post screen captures of the setup pages on your switch.
Thanks & 73,
Ron N4RT
Bromley, AL
I will post some screen shots of the 8 port switch setup in a few days. We have two of our granddaughters visiting this weekend, so most (all?) of my energy with be used chasing them around.
-Randy
73,
Ron
Hi Randy,
My first attempt here to start up a Vlan. I have a pretty busy tower station on Mesh, Three 2.8 NanoBridge units, One 5.8 NanoBridge, One Bullet2MHP. Prior to today, all units were dtd via the Netgear GS108Ev3 set to factory settings with the 802.11 QoS on all 8 ports. Today I made the decision to learn about the Vlan and see how far I could get. I wrestled the switch out of my tower-mounted box and finally managed to get my computer to find it with the configuration software. I set it the same as a GS105E 802.1Q Advanced in your configuration settings, only progressed all the way to 8 and 7 with the Tag/Untag/clear indicators, however, am I correct in believing that file is deficient of Vlan10 and Vlan20, which appear to be necessary after watching Darryl's video. I definitely do not have a subnet indication on my unit W0HU-Nano1, which will be the controlling unit for WAN (with internet connected to 8). I am new to this aspect of networking, so will need some assistance, if you can please. The units all are still dtd no problem.
Jerry
The VLAN numbers (except for VLAN 1 and VLAN 2) are arbitrary numbers just chosen to distinguish "local" traffic on one node from "local" on another node on the same switch. The idea is that if you want a couple of devices, say a VoIP phone and a camera, to get their DHCP addresses from Node A, say a 2.4 GHz Nanostation, then you need at least three ports and a VLAN to have them all talk together. So, you put the Node A Nanostation on Port 1, for example, the phone on port 2 and the camera on port 3. On the switch, you define a VLAN, say VLAN79 in this case, and Untag port 1,2, and 3 on VLAN 79. The phone and the camera will get their IP addresses from the Nanostation, and the Nanostation will show the devices and their DHCP leases in the "Port Forwarding, DHCP and Services" section of the node's Basic Setup page.
If you have a second node, say Node B is a Rocket with a sector antenna, and you want some other devices associated with Node B, maybe a Raspberry Pi and a laptop computer, you can setup another VLAN on the 8 port switch. Node B could go into port 4, the Raspberry Pi into port 5 and the laptop into port 6. Then, on the switch, define a VLAN, say, VLAN64, and Untag ports 4,5, and 6 on VLAN64. The RasPi and the laptop will get their IP addresses fron the Rocket in port 4.
You still have to setup VLAN1 for an Internet connection, assuming that is what you want to do, and the instructions for this are above. Also you will want Node A and Node B to see each other, so you must setup VLAN2 as a Device-to-Device (DtD) link as described earlier with ports 1 and 4 Tagged on VLAN2.
Hope this helps clarify the situation a bit, and if it doesn't, please keep asking questions. We all learn from these exchanges.
73,
Randy
Now my interface looks like this:
AREDN-SW#