Can i just come back to this please? I've finally had some time to do some work on it. Couldn't solve it on my in-use wndr3700v4 - I was sitting thinking about it and I have a spare wndr3700v4 so I grabbed that, connected it only to my laptop (no WAN for simplicity, just ethernet to port 1 and power) .
Testing:
With a clean-flashed stock Netgear firmware, Windows identifies the network and I can set it as private - as expected. When I reboot the router, Windows recognises the network as the one previously connected to and behaves as expected. Excellent
This is the same with both versions of the stock firmware that I have and tested -
1.0.2.96 and 1.0.2.102.
From 1.0.2.102 I used the factory image and upgraded to 1.12.0 - Windows detects new network and I can set it as private (as expected)
When I rebooted, instead of recognising that previous network profile a new one is generated adding +1 incrementally with each reboot network 3,4,5,6 etc.
I have tried various gargoyle builds
1.11.0
1.12.0
1.12.x
1.13.x
and they all behave in the same way.
If it's relevant -
The mac address in the status / LAN page is xx:xx:xx:xx:xx:9A which is the MAC address on the sticker on the bottom of the router.
The mac address in Status/WAN page is xx:xx:xx:xx:xx:9B
Where both addresses are the same bar that last letter?
Im really struggling to work this out now, does anyone have any further info please?
It can't be windows or it would happen with the stock firmware as well and it doesn't happen with the stock firmware(s) so I really do think it's gargoyle but something I can't figure out on my own. And it happens on 2 separate wndr3700v4
that I have at home - I *think* the chances of 2 separate units having the exact same hardware fault are pretty low?
If anyone has a wndr3700v4 with any of the gargoyle builds listed currently installed (and it's not too much trouble) could you please reboot your router from within the firmware and see if it happens to you?
Many thanks
