Most of us have Ethernet in our homes today. The real backbones of the Internet though, use no wires at all. Optical fibers carry pulses of light across the land, under the sea, and if you’re lucky, right to your door. [Sven Brauch] decided to create an optical link. He didn’t have any fiber handy, but air will carry laser pulses over short distances quite nicely. The idea of this project is to directly convert ethernet signals to light pulses. For simplicity’s sake, [Sven] limited the bandwidth to one channel, full-duplex, at 10 Megabits per second (Mbps).
The transmit side of the circuit is rather simple. An op-amp circuit acts as a constant current source, biasing the laser diode. The transmit signal from an Ethernet cable is then added in as modulation. This ensures the laser glows brightly for a 1 bit but never shuts completely off for a 0 bit.
The receive side of the circuit starts with a photodiode. The diode is biased up around 35 V, and a transimpedance amplifier (a current to voltage converter) is used to determine if the diode is seeing a 1 or a 0 from the laser. A bit more signal conditioning ensures the output will be a proper differential Ethernet signal.
[Sven] built two identical boards – each with a transmitter and receiver. He tested the circuit by pointing it at a mirror. His Linux box immediately established a link and was reported that there was a duplicate IP address on the network. This was exactly what [Sven] expected. The computer was confused by its own reflection – but the laser and photodiode circuits were working.
Finally, [Sven] connected his PC and a Raspberry Pi to the two circuits. After carefully aligning the lasers on a wooden board, the two machines established a link. Success! (But be aware that a longer distances, more sophisticated alignment mechanisms may be in order.)
Want to know more about fiber and networking? Check out this article about wiring up an older city. You can also use an optical link to control your CNC.
There’s a big to-do going on right now in Germany over particulate-matter air pollution. Stuttgart, Germany’s “motor city” and one of Dante’s seven circles of Hell during rush hour, had the nation’s first-ever air pollution alert last year. Cities are considering banning older diesel cars outright. So far, Stuttgart’s no-driving days have been voluntary, and the change of the seasons has helped a lot as well. But that doesn’t mean there’s not a problem.
But how big is the issue? And where is it localized? Or is particulate pollution localized at all? These questions would benefit from a distributed network of particulate sensors, and the OK Lab in Stuttgart has put together a simple project(translated here) to get a lot of networked sensors out into the wild, on the cheap.
The basic build is an ESP8266 with an SDS011 particulate sensor attached, with a temperature and humidity sensor if you’re feeling fancy. The suggested housing is very clever: two 90° PVC pipe segments to keep the rain out but let the dust in through a small pipe. The firmware that they supply takes care of getting the device online through your home WiFi. Once you have it running, shoot them an e-mail and you’re online. If you want help, swing by the shackspace.
We love these sort of aggregated, citizen-science monitoring projects — especially when they’re designed so that the buy-in is low, both in terms of money spent and difficulty of getting your sensor online. This effort reminds us of Blitzortung, this radiation-monitoring network, or of the 2014 Hackaday-Prize-Winning SATNOGS. While we understand the need for expensive and calibrated equipment, it’s also interesting to see how far one can get with many many more cheap devices.
What is hacking and what is network engineering? We’re not sure where exactly to draw the lines, but [Artem]’s writeup of pivoting is distinctly written from the (paid) hacker’s perspective.
Once you’re inside a network, the question is what to do next. “Pivoting” is how you get from where you are currently to where you want to be, or even just find out what’s available. And that means using all of the networking tricks available. These aren’t just useful for breaking into other people’s networks, though. We’ve used half of these tools at one time or another just running things at home. The other half? Getting to know them would make a rainy-day project.
Is there anything that
socat can’t do? Maybe not, but there are other tools (
Rpivot) that will let you do it easier. You know how clients behind a NAT firewall can reach out, but can’t be reached from outside?
ssh -D will forward a port to the inside of the network. Need to get data out? There’s the old standby
iodine to route arbitrary data over DNS queries, but [Artem] says
dnscat2 works without root permissions. (And this code does the same on an ESP8266.)
Once you’ve set up proxies inside, the tremendously useful
proxychains will let you tunnel whatever you’d like across them. Python’s
pty shell makes things easier to use, and
tsh will get you a small shell on the inside, complete with file-transfer capabilities.
Again, this writeup is geared toward the pen-testing professional, but you might find any one of these tools useful in your own home network. We used to stream MP3s from home to work with some (ab)use of
ssh. We keep our home IoT devices inside our own network, and launching reverse-proxies lets us check up on things from far away without permanently leaving the doors open. One hacker’s encrypted tunnel is another man’s VPN. Once you know the tools, you’ll find plenty of uses for them. What’s your favorite?
Thanks [nootrope] for the indirect tip!
With almost 8 billion souls to feed and a changing climate to deal with, there’s never been a better time to field a meaningful “Internet of Agriculture.” But the expansive fields that make industrial-scale agriculture feasible work against the deployment of sensors and actuators because of a lack of infrastructure to power and connect everything. So a low-power radio network for soil moisture sensors is certainly a welcome development.
We can think of a lot of ways that sensors could be powered in the field. Solar comes to mind, since good exposure to the sun is usually a prerequisite for any cropland. But in practice, solar has issues, the prime one being that the plants need the sun more, and will quickly shade out low-profile soil-based sensors.
That’s why [Spyros Daskalakis] eschewed PV for his capacitive soil moisture sensors in favor of a backscatter technique very similar to that used in both the Great Seal Bug and mundane RFID tags alike. The soil sensor switches half of an etched PCB bowtie antenna in and out of a circuit at a frequency proportional to soil moisture. A carrier signal from a separate transmitter is reflected off the alternately loaded and unloaded antenna, picking up subcarriers with a frequency proportional to soil moisture. [Spyros] explains more about the sensor design and his technique for handling multiple sensors in his paper.
We really like the principles [Spyros] leveraged here, and the simplicity of the system. We can’t help but wonder what sort of synergies there are between this project and the 2015 Hackaday Prize-winning Vinduino project.
Continue reading “Using Backscatter Radio for a Soil Sensor Network”
Recently ZDNet and Gizmodo published articles outlining a critical flaw in a large array of personal printers. While the number of printers with this flaw is staggering, the ramifications are even more impressive. Ultimately, any of these printers could have documents sent to them stolen even if the document was only intended to be printed as a hard copy.
Luckily the people responsible for this discovery are white-hat in nature, and the release of this information has been made public so the responsible parties can fix the security flaws. Whether or not the “responsible party” is the manufacturer of the printer, though, is still somewhat unclear because part of the exploit takes advantage of a standard that is part of almost all consumer-grade printers. The standard itself may need to be patched.
Right now, however, it doesn’t seem clear exactly how deep the rabbit hole goes. We all remember the DDoS attack that was caused by Internet of Things devices that were poorly secured, and it seems feasible that networked printers could take some part in a similar botnet if a dedicated user really needed them. At the very least, however, your printed documents might not be secure at all, and you may be seeing a patch for your printer’s firmware in the near future.
We all know feature creep can be a problem in almost any project. A simple idea can often become unusable if a project’s scope isn’t clearly defined in the beginning. However, the opposite problem sometimes presents itself: forgetting to include a key feature. [Zach] had this problem when he built a Raspberry Pi magic mirror and forgot to build a physical reset/shutoff switch. Luckily he had a spare Amazon Dash button and re-purposed it for use with his Pi.
The Raspberry Pi doesn’t include its own on/off switch. Without installing one yourself, the only way to turn off the device (without access to the terminal) is to unplug it, which can easily corrupt data on the SD card. Since [Zach]’s mirror was already complete, he didn’t want to take the entire thing apart just to install a button. There’s already a whole host of applications for the Dash button, so with a little Node.js work on the Raspberry Pi he was able to configure a remote-reset button for his mirror.
This is a similar problem for most Raspberry Pi owners, so if you want to follow [Zach]’s work he has done a great job detailing his process on his project site. If you’re looking for other uses for these convenient network-enabled buttons, he also links to a Github site with lots of other projects. This pizza button is probably our favorite, though.
NASA has been tracking bright meteoroids (“fireballs”) using a distributed network of video cameras pointed upwards. And while we usually think of NASA in the context of multi-bazillion dollar rocket ships, but this operation is clearly shoe-string. This is a hack worthy of Hackaday.
The basic idea is that with many wide-angle video cameras capturing the night sky, and a little bit of image processing, identifying meteoroids in the night sky should be fairly easy. When enough cameras capture the same meteoroid, one can use triangulation to back out the path of the meteoroid in 3D, estimate its mass, and more. It’s surprising how many there are to see on any given night.
You can watch the videos of a meteoroid event from any camera, watch the cameras live, and even download the meteoroid’s orbital parameters. We’re bookmarking this website for the next big meteor shower.
The work is apparently based on [Rob Weryk]’s ASGARD system, for which the code is unfortunately unavailable. But it shouldn’t be all that hard to hack something together with a single-board computer, camera, and OpenCV. NASA’s project is limited to the US so far, but we wonder how much more data could be collected with a network of cameras all over the globe. So which ones of you are going to take up our challenge? Build your own version and let us know about it!
Between this project and the Radio Meteor Zoo, we’re surprised at how much public information there is out there about the rocky balls of fire that rain down on us every night, and will eventually be responsible for our extinction. At least we can be sure we’ll get it on film.