First up, big thanks to all techie geeks who attempted help with the router/hub/modem thingie problem – Lovely G, TH and Christian Renz, all fine peoples with some top advice.
However, in the end it was me who came up with the solution. Yes, me. I’m sat here thinking about the problem, and how everyone says ‘but ethernet ought to connect automatically’. TH in fact pointed out that I ‘must have had the ethernet connected to configure the modem in the first place’. And that’s the bit that sparked my next thought… My problems all seemed to stem from the fact that I’d configured it all via wireless, so it saw the Wireless as the primary internet connection, and wasn’t sending the right DHCP info to the ethernet side of things at all.
So, I do what every self-respecting geek-in-a-fix does, and restored the factory settings on the modem, turned off the airport on the laptop, plugged in the ethernet and started again.
This time, it worked like a dream. DHCP assigned LAN IP details (shark, ask TH) to the ethernet side of things, I was all hooked up in seconds, and could properly configure the wireless side of things to actually have a password on it! Yay for me.
However, more important than all of that, I could also then do the software update for the Looperlative, fixing a bug I found two days ago (Bob uploaded the fix yesterday – how’s that for customer service???), and cleaning up the audio even further (it already kicked the arse of every looper I’d ever used)… So scratch that title – Bob. Officially. Rules.
Oh yes.
Well done! I was thinking it over the other night after you went offline (and off to nightshelter) I thought if it was me what would I do? I’d switch off everything superfluous, reset the factory default and connect to it via Ethernet, get that up-and-running and only then activate the WiFi.
But no use me suggesting that to you now. I’ve got a new Router/Switch to sort out at some point … fancy a job doing mine?