It looks like you're new here. If you want to get involved, click one of these buttons!
Subscribe to our Patreon, and get image uploads with no ads on the site!
Base theme by DesignModo & ported to Powered by Vanilla by Chris Ireland, modified by the "theFB" team.
Comments
Because the Soudcraft's default behaviour is to behave as a WiFi hotspot, I thought using a cable connection would do similar - except wired. And so, I thought if I hooked it into the router's WAN port (which it is when in router mode) that I could then connect multiple devices to the router's LAN and then I should be able to get to the Soundcraft.
If I'm understanding correctly, the Soundcraft has a LAN option which means it can connect to the LAN side of the router. Which my router doesn't offer in router mode.
The option is there to connect the two over WiFi. And it might help, as I think half the issue with connections is because phones and iPads are being moved around and often a fair distance away from the Soundcraft. If the mini router stays nearby and offers a better WiFi connection to devices then it might be good. In that case, I believe the Soundcraft is connecting to the router's LAN and it doesn indeed ask for a network SSID and password.
Still, if I can get it to work how it was at one point last night then that would be usable. Though I've no idea what I did and even why it was working that way.
But then I've been speak utter bollocks on this thread so maybe this continues the trend.
If the desk can't, then you need something else to be the main glue if you use the gizmo you have in client mode, at which point you may as well just use the something else with a patch lead and bypass the gizmo.
Either way, the gizmo doesn't help.
With what you describe two posts above the problem will be configuring the WAN port so it's on a known static alternate subnet and hard coding a suitable IP in the desk so that the desk becomes "the Internet" and can be routed to. Otherwise a combo of NAT and firewalling and fucked addressing will stop you accessing it.
So the solution is to go get the right tool for the job, or get a local mate who *really* knows this stuff to come set it up for you.
@PolarityMan sometimes things that are shit at being the access point/hotspot are fine at being a client to a proper AP, hence asking the question. To which there's consistently no answer, making the only viable response to be, once again, buy a more appropriate fucking router and use a cable
Not got it working yet but I'm sure it'll be possible.
Put all devices on DHCP
Cable the desk in
Assuming the desk LAN port is a LAN port and isn't for sending channels over ethernet, it will work.
We use a UI24r in one of my bands with an external router. I do know the other other models in the UI range have a reputation for issues with their onboard wireless networking reliability but the instructions above should cover setting the IP ranges to use an external unit instead. We share the custom IP address with band mates.
It does require powering up.the router first, then the Ui16 once the router is ready.