Defined New Network and Switch (DCHP) is MIA...?

Hi all,

I have been pulling my hair out (both of them) for several days trying to figure this one out. I have the Gold, and my physical setup started out as follows:

All ports (1-3) on the 192.168.1.1/24 network. Physically, everything is split between ports 2 and 3: I put the video feeds to the Rokus throughout the house on port 2 via a switch, and everything else is on port 3. Worked great. Now, in order to isolate an IoT network (which the Rokus are), I defined a new network on port 2 as follows:

1) Removed the port 2 assignment from the 192.168.1 network

2) Defined new network (192.168.132.1/24) on port 2

Now, everything is set up as DHCP (nothing hard-coded), so the assumption is that the Firewalla would simply dole out new addresses in the new network (since the switch is physically connected to port 2, and by extension everything connected to the switch). It took a while, but the Rokus came back online with the new addresses, and my daughter was delighted that her TV now worked again. Here's where it gets weird. The switch itself never came back (ie. it was never relisted with the new address, and the old listing simply says that the device is offline). My understanding is that if the switch is MIA, then everything connected to the switch should also be MIA. I have tried everything from power cycles to deleting the listing in the Firewalla hoping that it would re-list, all to no avail. Meanwhile, all the devices connected to the switch are just fine, and are listed as online. What am I missing? Thanks!

Okellyro

February 06, 2023 13:19

Was the switch setup as a hard coded static assignment on the old network... if so you would need to login to the switched console (or move it back to the old network) to gain access and set it to DHCP ... maybe?

Anakin Skywalker

February 07, 2023 04:21

Hi Okellyro,

Nothing was hardcoded (everything was DHCP). Several hours (?) after I posted, the switch finally showed up. So, now everything is as it should be, but I am still somewhat confused by the timing. If the switch was truly not recognized by the Firewalla, then why did the attached devices (Rokus) show as online (and worked fine)? And why were the attached devices recognized several hours before the switch itself? Well, in any case, everything worked out, and I just have a great deal to learn, Thanks!

February 07, 2023 05:10

could be that the lease on the switches needed to expire! the other devices like roku or PC/Printer/Laptops act differently ... anyhow ... its working.

Defined New Network and Switch (DCHP) is MIA...?

Comments

Didn't find what you were looking for?