nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Continue wired network from mesh node

unknown

Is it possible to continue a wired network from a R500 mesh node?

I am running a unleased r500 mesh network with the main node connected to a router with internet. I would like to add a switch to a mesh node on the other side of our building to add some computers (without wifi) on that end.

Find more posts tagged with

Accepted answers

All comments

unknown

yes - this is doable however you may run into issue with regards to users behind the switch not receiving IP through DHCP.
You can resolve the issue with commands mentioned in below Post

https://forums.ruckuswireless.com/ruckuswireless/topics/anyone-know-how-to-disable-directed-dhcp-on-...

unknown

Thank you! I'll try and test it this evening disabling directed DHCP on each AP.

michael_brado

Monnat is correct, to disable directed-dhcp might help clients beyond the MAP to get IPs.

Remember only Root Mesh APs can be Unleashed Master or Gateway mode AP, and be sure
to avoid forming loops in your network connections.

unknown

I will test with a few static addresses first. I’ll look up the debug mode and scripts needed to change the directed dhcp setting when Dhcp is really needed on the other end. It’s my home network, not much experience with such extended ap’s 😉

michael_brado

I'm not sure static IP clients beyond Mesh AP will work, as Ruckus would have no way to know those client MACs exist.
We don't have the commands to say this mac with this IP is on this interface, unless it's on your AP switch port side...?
Please share your test results.

unknown

This is the situation I would like to create:

Image_ images_messages_5f91c43b135b77e2479d3296_f9b768755b256a1c20948e27a2ca1f0a_RackMultipart20180313766433owf-792022c5-4629-4b62-a44b-2f5e78d9576c-2071203871.PNG1520931635

Image_ images_messages_5f91c43b135b77e2479d3296_f9b768755b256a1c20948e27a2ca1f0a_RackMultipart20180313766433owf-792022c5-4629-4b62-a44b-2f5e78d9576c-2071203871.PNG1520931635

unknown

yes its doable as suggested earlier.. thx

unknown

Found this in Ruckus documentation. It might be easier than I thought.
Image_ images_messages_5f91c43b135b77e2479d3e2a_ed7f85382acd1e744987cdf583def2b3_RackMultipart2018031433054ra42-c36777b7-b8d3-448f-b993-ca51563ad451-202740364.PNG1521009888

Image_ images_messages_5f91c43b135b77e2479d3e2a_ed7f85382acd1e744987cdf583def2b3_RackMultipart2018031433054ra42-c36777b7-b8d3-448f-b993-ca51563ad451-202740364.PNG1521009888

unknown

yes, its pretty much the same you made...

unknown

I've tried the easy way, setting Gateway mode on
unleashed.ruckuswireless.com. Servers on the other end are getting
access to internet, but, de AP is acting as DHPC server. It might be
enough for now. I'll start testing lowering subnet ranges to make sure
the first network can reach ip's in the Ruckus network.
Still, if it won't work as expected, I'll dive into the (ssh/bash?) commands.