# Switch active before it's configured - avoidable?

**URL:** <https://forum.openwrt.org/t/switch-active-before-its-configured-avoidable/36017>\
**Category:** Network and Wireless Configuration\
**Created:** [April 28, 2019, 8:49am UTC](https://forum.openwrt.org/t/switch-active-before-its-configured-avoidable/36017 "2019-04-28T08:49:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jeff](https://forum.openwrt.org/letter_avatar/jeff/32/5_5575768a8748004e209b776fc1b2916d.png) [@jeff](https://forum.openwrt.org/u/jeff)\
**Post date:** [April 28, 2019, 9:12am UTC](https://forum.openwrt.org/t/switch-active-before-its-configured-avoidable/36017/2 "2019-04-28T09:12:57Z")

</div>

These home-router chips usually come up in a configuration appropriate for OEM WAN/LAN use and are “leaky” as a result until OpenWrt is running and re-configures them. They’re also generally reset on config change, but that is typically much less than a second so most never see the ill effects.

I don’t think there’s a good solution as I don’t think one can keep the phys powered down at boot. You might be able to do something with a custom boot loader, as the problem starts at power on. I typically use the WAN port as my VLAN trunk to help mitigate this somewhat.

---

_[View the full topic](https://forum.openwrt.org/t/switch-active-before-its-configured-avoidable/36017)._