The Space network is apparently under repair.
What needs to be done to get it working again so I can turn the Space Probe on and notify people that the Space is open and turn the lights on? 
So far: Draytek Vigor120 ADSL modem, someone has tried configuring it but the PPPoE credentials appear to be incorrect.
ADSL connection fixed. Now to figure out what is wrong with the WiFi.
PS: the problem with the ADSL was VCI/VPI settings which are 8/35 for Australia, and Auth mode is usually PPPoA or PPPoE.
1 Like
WiFi is back!
The Billion that was being used as a switch appears to be unhappy. I think I have a 100Mbps ethernet switch at home that can come and live at MHV.
So no Space Probe for the moment.
I think there is a WiFi router in a box in the shelves near the 3d printers
that might work as a switch?
I couldnāt find such a thing, there are a few USB / 3G modem things up top.
At present the ADSL is syncing at 2.7Mbps. The connection is flaky, it might be worth whoever is the account āownerā to contact Internode and ask that the line be set to a āstability profileā and mention that the highest sync speed weāve seen is about 3-point-something Mbps so thereās no use trying a faster profile.
The stability profile will help prevent drop-outs during high traffic or electrical noise.
Adam and I had a go at installing the Draytek. Sorry I didnāt see the post until now, it looks like you got further than we did! I am under the impression that setting it to 10.0.0.1 and disabling dhcp (handled by aspirin I think) should have been all thatās required to make it all workā¦ The billion wasnāt being used as a switch; it was the previous adsl modem which has just died (and the switch part is all that works).
There is a second white billion that was being used as a switch for the
space probe, but I reset it trying to get it to work as a modem. But I
couldnāt get to see itās Admin menu to configure it.
How many ports do the 3g modems have? Might be enough for the space probe
and RFID scanner?
The white Billionās Ethernet ports were misbehaving. I have a D-Link DES-1008D 10/100M Fast Ethernet Switch which I donāt use anymore (all my Ethernet stuff is gigabit, everything else is WiFi). Iāll drop in to the space on my way home tonight (no Electronics Thursday, I have chores to catch up on) and see if I canāt get the Space Probe up and running again.
I guess Iāll need to update the Space Probe wiki page at the very least.
So my next project (after finishing this water level sensor) is now going to be ārefurbish Space Probe & documentationā, which is likely to include migrating to MQTT.
Sorry guys, very confused about whats going on. Just wanted it say I have a Billion router/modem (same one as the old one) that Iām happy to donate to the space if itāll help.
The story so far:
I arrived at the Space on Wednesday night to find that the Space Probe was blinking red. The LED strips would not turn on, and there was no WiFi. Or rather there was MHV being advertised but I couldnāt connect.
It turns out that a few days ago the old ADSL modem/router died, and people tried setting up a replacement. Along the way various things were tried, and the white Billion which used to be the switch sitting out in the lounge connecting the RFID and Space Probe to the network, was no longer working. So thereās the blue/black Billion ADSL modem/router which died, and the white Billion ADSL modem/router/switch which was previously serving as just a switch, both were left sitting on the lab desk with all the networking gear last night.
So far Iāve managed to configure the new Draytek Vigor ADSL modem/router, which is now tucked behind the laser printer on top of the filing cabinet in the lab room. Part of its status display indicates that it synced at just over 2Mbps, which I noted on this thread and is a cue to get someone to talk to Internode and have the ADSL profile cut down to a stability profile (ADSL that syncs at under 4Mbps means you have a poor/long line and will likely be better off with a more robust signal provided by the stability profile).
I restarted the Billion WiFi AP/router, and that appears to have restored WiFi connectivity.
When I left last night, the WiFi and Internet were still working, but the Space Probe was still not connected and the LED strips were still not āworkingā.
All up there are a bunch of āBillionā items: the Blue/Black ADSL modem/router which was previously serving as the ADSL connection, the white ADSL modem/router/switch which was previously serving as the switch in the lounge, and the black WiFi AP/router which was and is serving as the WiFi AP for the upstairs space.
(the blue/black billion is a very deep blue that might appear to many people to be black)
/cue Carl Sagan voiceover: āBullions and Bullions of Bullions.ā
Iāll be at the space tonight to see what I can do. Sorry to have left it in a bit of a mess.
Iāll try to get there after work and drop off this switch. Itās way over specification for the specific job, but itāll get things working again 
I think I have a 10Mbps hub somewhere, you know that ancient 1990s technology which was slower than 3G wireless?
Found it! XD 
WITH SPARKLIGHTS!
Please do not plug that in, it makes Network people cry 
Itās perfectly fine for the task at hand, which is connecting two ultra-low-speed devices!
Thereās even room for six more projects to be connected via 10-base-T. Remember when we called it that, instead of just āEthernetā? One possible project could be a LED strip controller, so people in the lounge can actually control the lights.
I think we are able to set the profile through internodeās web interface and have done that a few times in the past trying to got something optimal.
Good to know!
also, hereās something that might be of interest for future Ethernet-connected projects: http://www.amazon.com/TP-LINK-TL-SF1008P-100Mbps-8-Port-802-3af/dp/B003CFATT2
Then use a suitable receiver at the other end (such as Freetronics EtherTen Arduino-compatible with 802.3f daughterboard).
Another alternative is the hobby-POE style Freetronics POE injector: http://www.freetronics.com.au/products/poe-injector-4ch#.VS9bO84RrOY
Or even more brutally maker-efficient, modifying this workgroup hub to inject the power directly.
Hubs are no longer being made for a reason - itās a bad way of doing things now. We know better. So we manufacture switches.
For those who donāt know the difference, a hub can be considered a ādumbā device - it receives a message and then duplicates that message on ALL ports, adding to network traffic and noise.
A switch is smarter - it learns which device is connected to which port (or more accurately which device can be reached by which port (in cases of a switch connected to a switch for example)) and only sends the message on that port.