ok i confirmed the config of switch 2, as per the edit above.
Ok, how does switch 2 get an address?
It... doesn't. it just constantly reverts to its default/fallback IP and i have to set a static ip on that subnet to get to the management.
General quesiton: do netgear switches suck or something?
There should be a page where you can set the device's IP address and mabe its management VLAN. While it should theoretically work via DHCP, set it manually to somethin in the desired management network. Make sure that the address is not used by any other devices and is outside the DHCP pool. 192.168.1.3 would theoretically work for switch 2, and 192.168.1.2 might be good for switch 1. (that's how I might organize them) -- assuming that 192.168.1.0/24 is your management network.
Then it should stay on that address.
The low end ones do, yes. As do the low end managed switches from TP-Link. Both of these comapnies make good switches as you go up-market, but their entry level stuff is pretty bad.
I had an old GS724Tv2 that behaved exactly the same. The default IP was 192.168.0.239 and it would always revert to it and never really request an address via DHCP. If the switch is accessible and you can spare a port, configure this as your management port. The downside is that you will have to physically access the switch in order to configure it.
In the end, I replaced it (by a switch supported by OpenWrt).
I have been using GS108TV3 switches with Netgear Firmware. And got some mysterious problems...
After flashing them to OpenWrt everything works as expected.
Generally its a good idea to use the same operating system at all devices. At least the same gui. This makes life much more easy for inexperienced users (like me).
Just an update on this. I'm convinced the firmware on the switches is the problem.
In the end, i wound up creating a vlan 1 interface and deleting lan, so there are no "real' interfaces on my lan side at all - they're all 802.1q vlan devices and interfaces.
i had to untag the port from switch 2 to switch 1 (also pvid '1') - there's no way to set a management vlan on this device, so i guess it's semi vlan-aware? but untagging that port then allowed it to get an IP via DHCP.
switch 1 did not work the same - i untagged the port (pvid 1) that goes from switch 1 to the router and tried to get a dhcp ip assignment... no dice. in the end, i've got this switch accessible by a static IP though.
my wireless AP was the same - it's vlan aware, but kinda not. so i had to untag(pvid 1) the hard wire connection between the AP and the switch. it seems to work in that i can manage the AP on a 192.168.1.x IP address, and it seems to be routing wireless vlan traffic to the other vlans correctly.
not sure i fully understand how a port can be trunking VLAN 80 but be untagged/PVIDed to VLAN 1 though... is this just odd behavior or is it consistent with how tagged/untagged ports should work?
in any case, thanks much for your help.
One follow-up question (sorry i would pm you but i can't figure out how)
i have a pi-hole/unbound on a separate device. my plan will be to hook this device up to vlan .1 and then advertise it as a dns server but only to my internal lan (i.e. don't care about ad-blocking for guests).
i think this accomplished in luci by editing the relevant vlan interface > dhcp > advanced > and then putting in 6,192.168.1.xxx as the DNS server... is that right?
follow-up question: where do you determine what the "default" dns service is (for devices/applications that don't specify their own dns server)?
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.