Anyone starting with single-board computers can save a lot of money/hassle in extra purchases, by connecting their Raspberry Pi / Beaglebone Black / Udoo to their network via an Ethernet cable. Remotely controlling the device in a headless configuration saves the hassle of connecting keyboard, mouse, computer screen and buying micro HDMI cables, powered hubs, etc.
One of the first problems that you run into on a first boot though is that the device is not set up with a static IP, thus forcing you to find the device on your network. This tutorial will show you three (of many) ways of finding the IP of the devices connected on your network (I will update this list as time goes on):
- Using your Router
- Using Fing – Network Tools
- Using the net view command
In this tutorial I have a Raspberry Pi (with Occidentalis) and an Udoo Quad (with udoobuntu) connected on the network.
1. Router Method
This method will require you to have access to your router. You can log into your router through a browser window.
- Open your browser
- Type in your router IP address into the address bar (the IP varies, but try: 192.168.0.1 or 192.168.1.1 or your default gateway-address, which sometimes works).
- You will be asked to login, which requires you to know the router login information. You can ask whoever is in charge of your network. If this is not an option, try one of the other methods.
- If you logged in successfully, there should be a section that talks about the status of the network and shows all the clients that are connected:
Note that the Udoo (192.168.1.150) shows up as “Unknown”, but you can still see its IP and connect to it. This should only be troublesome if you have many “Unknown” systems on your network, which will mean that you will have to try and log into each. The Raspberry Pi (192.168.1.71) shows up fully identified with the IP showing.
You can download Nmap for Windows, Linux, and Mac here. Once installed you can either use the command line or the GUI. Here is the GUI output:
The Raspberry Pi MAC addresses start with: B8:27:EB. You can see Raspberry IP (192.168.1.71) next to the manufacturer info (Raspberry Pi Foundation).
The udoo was also found (192.168.1.150), but if you didn’t know that the manufacturer was Seco and if you had more devices on your network, you would have to search a bit.
3. Fing – Network Tools
In this step you will need Fing – Network Tools which is available for free from the Google Play store. It will work on any Android device and tell you information about your network. All you have to do is ensure that your Android device is connected to the same network as your Singleboard Computer and then press the “scan” button.
See following image for a sample output. (Tip: press power button + volume down for two seconds on Android devices to take a screenshot):
The program was able to identify both the udoobuntu (192.168.1.150) and the raspberry pi (192.168.1.71) with the appropriate IP addresses. Fing managed to find all other random network devices that make up a modern household. The program also has other useful features (I think) but I am only using it for IP identification thus far.
4. ‘Net View’ Command
I did not have any luck with this command on Windows 8.1, but someone mentioned it to me and who knows, it might work for you.
- Press the [Windows key] + [R] button
- In the dialog type cmd and press enter
- in the command prompt type net view and get the following output:
The command only found the personal computers that run windows on my network. The command did not find the Raspberry Pi or the UDOO nor any smart phones. It might work for you though. Give it a try.