You are here

Home » Forums » General discussion

GS105Ev2 stops "VLANing"

9 posts / 0 new
Log in or register to post comments
Last post
Tue, 08/30/2016 - 23:28
#1
w6bi
w6bi's picture
GS105Ev2 stops "VLANing"
This is the second time my GS105Ev2 has stopped working properly.  The first time I just reset it back to factory defaults, manuallly reconfigured it, and it resumed working properly.

This time I upgraded it to the latest firmware (V1.4.0.9) from V 1.3.0.3.  It appeared to retain its config after the firmware upgrade.  I saved off the config, cold started it, and reloaded the config.   It's still not working.

Symptoms:
  • Node doesn't get an IP address from my WAN DHCP server (it's still working - I verified that).
  • DtD no longer is working between my two nodes.
I've verified by inspection that the configuration is per the AREDN docs.
Any troubleshooting ideas?

Thanks.
Top
Wed, 08/31/2016 - 11:06
K5DLQ
K5DLQ's picture
not sure.  BUT, if the switch
not sure.  BUT, if the switch is bad, NetgearPro switches have a LIFETIME warranty.  :-)
Top
Wed, 08/31/2016 - 11:34
kg9dw
kg9dw's picture
If you plug a laptop in, does
If you plug a laptop in, does it get a address from your WAN gateway?

I've got three of these switches live in a production network and I haven't had a single failure. 
Top
Wed, 08/31/2016 - 23:32
w6bi
w6bi's picture
Lapotp works, node doesn't
by plugging a laptop in the port that normally feeds the AREDN node, the laptop successfully gets a WAN IP address, where the node doesn't.
I guess that means my node is dorked up?  What now?  Cold start the node?
Top
Thu, 09/01/2016 - 00:35
(Reply to #4)
KG6JEI
This could also mean the
This could also mean the switch is no longer tagging the packets.

In theory if the switch is fully configured with PVID to Lan (untagged) and VLAN 1 Tagged then the laptop shouldn't be able to get an IP. 
Top
Thu, 09/01/2016 - 23:46
w6bi
w6bi's picture
Troubleshooting
I'll be replacing the node this weekend - we'll see what happens after that.  I still suspect the switch, though.
Top
Mon, 09/05/2016 - 19:37
w6bi
w6bi's picture
Test results.

Replacing the TP-link that was giving the odd results mentioned above with a newly-configured NSM2 resolved the issues.  I suspect internal configuration differences that might not be accounted for in the code.  (Speculation on my part only.)

I forgot to mention in the original post, that the problem occurred immediately after checking the Mesh Gateway box and applying the change.

Top
Mon, 09/05/2016 - 22:29
(Reply to #7)
KG6JEI
If that is indeed the case
If that is indeed the case you would be best off to open a ticket and file a support data file into it along with the steps to reproduce otherwise it's not likely to be tracked and resolved. 
Top
Mon, 09/05/2016 - 23:25
w6bi
w6bi's picture
TPLink issues
I have enough equipment on-hand to try to replicate the issue; if I'm successful, I'll open a ticket.
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer