Why would you think that? The firmware should shift the firewall settings over to the 2.5 GB port when it is set up.Is the 2.5GbE LAN/WAN port a security risk when used for WAN and the firmware is reset, connecting the WAN/Internet to the LAN?
OE
Why would you think that? The firmware should shift the firewall settings over to the 2.5 GB port when it is set up.
I did several times. The firmware should detect that port is on a WAN connection. Was also thinking you had put something in your tea this morningRead it again.
OE
I did several times. The firmware should detect that port is on a WAN connection. Was also thinking you had put something in your tea this morning
If it doesn't result in a 192 IP I'm thinking there's a mechanism in the FW that should take care of that. Then again these aren't the smartest devices either.
I think the thing that would stop it becoming a problem is that in the scenario where you do a factory reset you're forced to go thorough the initial setup procedure before anything works.Given the configurable LAN/WAN port is configured for WAN and wired to the Internet... if the firmware is reset and that port defaults to LAN port5, is the Internet now wired directly to the LAN and is this a security risk until disconnected?
OE
I would think the default setting is LAN which would be offering DHCP to the ISP which wouldn't work.Yeah, that's the uncertainty I'm wondering about. I can think of various scenarios where the condition could go unnoticed for an extended period of time.
OE
I think the thing that would stop it becoming a problem is that in the scenario where you do a factory reset you're forced to go thorough the initial setup procedure before anything works.
I would think the default setting is LAN which would be offering DHCP to the ISP which wouldn't work.
Why not just lab it up and see what it does?
I think you're inventing edge case scenarios just for the sake of it. If some idiot wires things up incorrectly and doesn't check/notice that it's not working properly that's a human problem not a router problem.Yes, but... previously my concern was for the novice commissioning multiple routers for AiMesh and inadvertently reconnecting the WAN cable to a LAN port. Now a configurable LAN/WAN port and firmware reset makes this much more likely to happen. So, just wondering how the firmware might handle it to protect the user's LAN.
Where's Tech9 when I really need an answer!
OE
Routers only do what you tell them to do.human problem not a router problem.
I think you're inventing edge case scenarios just for the sake of it. If some idiot wires things up incorrectly and doesn't check/notice that it's not working properly that's a human problem not a router problem.
I understand that accidents happen but you have to draw the line somewhere. In the scenario you're describing I think it's highly unlikely (although not impossible) that the misconfigured network wouldn't be very quickly apparent. I don't think it could easily go unnoticed.We all appreciate calling people idiots in situations that come easy to ourselves, but... accidents happen. In this situation, if simply resetting the router creates a network security risk that could easily go unnoticed, it is worth knowing about. Safety... safe computing... is regular practice, not an edge case, imo.
OE
He's talking about a factory reset rather than a reboot.You can set the primary WAN to the 2.5 on the Dual WAN page.
That way it stays set as primary WAN even if you reboot.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!