<![CDATA[Update broke SG-1000 VLANs]]>Hello,

I have an SG-1000, and I've been pretty happy with it. I've been keeping it relatively up to date, and pulled one of the earlier 2.4.0-RC builds without incident. However, yesterday, I pulled 2.4.0.r.20171004.1430, and from the perspective of my PC, routing never seemed to come back up.

On closer inspection via the serial console, the SG-1000 DID come back up, but wouldn't route anything to any of my LANs. I have four LANs, all on various tagged VLANs, with no untagged interfaces configured at all (I've been using a similar configuration for years on various pfsense boxes). I was not able to get anything to route until I put the base interface into promiscuous mode.

At this point, it works, but I am wondering if this is a regression or an intentional change? What is the best course of action for configuring the box so I don't have to connect the serial console and set promisc every time it reboots?

Thanks very much in advance.

-Bill

]]>https://forum.netgate.com/topic/121013/update-broke-sg-1000-vlansRSS for NodeMon, 05 Oct 2026 17:49:55 GMTFri, 06 Oct 2017 08:05:12 GMT60<![CDATA[Reply to Update broke SG-1000 VLANs on Mon, 09 Oct 2017 12:33:36 GMT]]>Bill,
They have updated the other thread that they are aware and working on a fix. Probably monitor that thread for updates.

]]>https://forum.netgate.com/post/726120https://forum.netgate.com/post/726120Mon, 09 Oct 2017 12:33:36 GMT<![CDATA[Reply to Update broke SG-1000 VLANs on Fri, 06 Oct 2017 15:27:52 GMT]]>Bill,
I also have the same problem. I responded to another thread (got bumped to the top) that this seems to be a regression that was fixed previously. I have found for me their fix of putting the parent nic (cpsw1) in promiscuous mode has fixed it for me. Glad to see it wasn't just my device.

]]>https://forum.netgate.com/post/725681https://forum.netgate.com/post/725681Fri, 06 Oct 2017 15:27:52 GMT