Direkt zum Hauptbereich

How To Set Up A Rock Pi S - Part 2: The Network

After the successful initial set up of my Rock Pi S, I started going on with my project self made smart home assistant. Therefor, it is necessary to configure the network interface.

SSH Does Not Mean Network Is Fine


Though we already are able to connect to the Rock Pi S via SSH, we probably cannot yet ping servers outside our local network. A ping to google.com, for example, will result in no answer:

Destination Host Unreachable

The reason is, that there is no standard gateway set in the network configuration, which causes, that only local network hosts inside the same subnet can be reached. The gateway is like the door of your flat. If You don't know, where it is, You cannot even leave your flat and see the rest of the street.

To find out your standard gateway, there are different approaches between Windows and Linux. Maybe You need to investigate this for your client operating system. On Windows, You open a command line and type:

ipconfig

The output looks like:

Something DNS-Suffix  : router.something
Local IPv6-Address  . : text::text:text:text:more:text%20
IPv4-Address  . . . . : 192.168.3.3
Subnet mask . . . . . : 255.255.255.0
Standard gateway  . . : 192.168.3.1

On Linux, you open a terminal and type:

sudo route -n

This will show you something like this:

Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref  Use Iface
0.0.0.0        192.168.3.1    0.0.0.0        UG    0      0    0    eth0
0.0.0.0        0.0.0.0        0.0.0.0        U     202    0    0    eth0
169.254.0.0    0.0.0.0        255.255.0.0    U     202    0    0    eth0
192.168.3.0    0.0.0.0        255.255.255.0  U     100    0    0    eth0

In the examples above the required information, the standard gateway, is to find in the red line. (On Windows it is the line with "Standard gateway", in Linux it is the line containing "UG" in the column "Flags".) You need the IP-address, in this case it is 192.168.3.1.

Tell the Rock Pi S its standard gateway with:

sudo ip route add default via 192.168.3.1

Done. Now, a ping to google.com should look like this:

rock@rockpis:~$ ping google.com
PING google.com (216.58.213.206) 56(84) bytes of data.
64 bytes from ham02s15-in-f206.1e100.net (216.58.213.206): icmp_seq=1 ttl=56 time=29.4 ms
64 bytes from ham02s15-in-f206.1e100.net (216.58.213.206): icmp_seq=2 ttl=56 time=29.9 ms
64 bytes from ham02s15-in-f206.1e100.net (216.58.213.206): icmp_seq=3 ttl=56 time=29.7 ms


Labels:

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Pi And More 11 - QMC5883 Magnetic Field Sensor Class

A little aside from the analytical topics of this blog, I also was occupied with a little ubiquitous computing project. It was about machine learning with a magnetic field sensor, the QMC5883. In the Arduino module GY-271, usually the chip HMC5883 is equipped. Unfortunately, in cheap modules from china, another chip is used: the QMC5883. And, as a matter of course, the software library used for the HMC5883 does not work with the QMC version, because the I2C adress and the usage is a little bit different. Another problem to me was, that I  didn't find any proper working source codes for that little magnetic field device, and so I had to debug a source code I found for Arduino at Github  (thanks to dthain ). Unfortunately it didn't work properly at this time, and to change it for the Raspberry Pi into Python. Below you can find the "driver" module for the GY-271 with the QMC5883 chip. Sorry for the bad documentation, but at least it will work on a Raspberry Pi 3.
1 Kommentar
Mehr anzeigen

How to use TOracleConnection under Lazarus for Win64

Lazarus Programmers have had no possibility to use TOracleConnection under 64 Bit Windows and Lazarus for years. Even if you tried to use the TOracleConnection with a correctly configured Oracle 11g client, you were not able to connect to the Oracle Database. The error message was always: ORA-12154: TNS:could not resolve the connect identifier specified Today I found a simple workaround to fix this problem. It seems like the OCI.DLL from Oracle Client 11g2 is buggy. All my attempts to find identify the error ended here. I could exclude problems with the TNS systems in Oracle - or the Free Pascal file oracleconnection.pp though the error messages suggestes those problems. After investigating the function calls with Process Monitor (Procmon) I found out, that even the file TNSNAMES.ORA was found and read correctly by the Lazarus Test applictaion. So trouble with files not found or wrong Registry keys could also be eliminated. Finally I installed the Oracle Instant Client 12.1c - aft
1 Kommentar
Mehr anzeigen

Lazarus IDE and TOracleConnection - A How-To

Free programming IDEs are a great benefit for everybody who's interested in Programming and for little but ambitious companies. One of these free IDEs is the Lazarus IDE . It's a "clone" of the Delphi IDE by Embarcadero (originally by Borland). But actually Lazarus is much more than a clone: Using the Free Pascal-Compiler , it was platform-independent and cross-compiling since it was started. I am using Lazarus very often - especially for building GUIs easily because Java is still Stone-Age when a GUI is required (though there is a couple of GUI-building tools - they all are much less performant than Delphi / Lazarus). In defiance of all benefits of Lazarus there still is one Problem. Not all Components are designed for use on a 64 bit systems. Considering that 64 bit CPUs are common in ordinary PCs since at least 2008, this is very anpleasant. One of the components which will not be available on 64 bit installations is the TOracleConnection of Lazarus' SQLDB
Kommentar veröffentlichen
Mehr anzeigen