ToDo

LSO is used by modern operating systems like GNU/Linux. LSO is a performance
capability where TCP segments, when transmitted from the network stack
to the network adapter, melted to a large segment, often bigger then the
MTU from the network adapter. This behaviour speeds up the transition a lot.
The opposite of LSO (Large Send Offload) is called LRO (Large
Receive Offload).

LSO often causes confusion, if network sniffing is not done directly from wire.
Because tcpdump and wireshark are showing heavily overlength packets if
a TCP stream is captured on a adapter connected to a Linux-Box.

LSO and LRO are implemented in the Linux kernel as TSO and GSO/GRO.

Your are able to deactivate this behaviour, then your network capture looks more
like wiretapping. The following commands are executed as root
on Linux 4.9, with wlp2s0 as the (wireless) network device.

Since yesterday I own a RIPE Atlas probe, that means I am a part of the
biggest Internet measurement network ever made. With the collected data from the probes
it is possible to monitor a big part of the Internet, independent from the Internet service providers.
The data is used for science and monitor purposes. The probe has the ability to do checks, some of the common
checks are visualized. With every check (mainly uptime) you earn credits
and with enough of them you can create checks of your own and the check will be executed by the Atlas-network.

At home I put the probe in a separated network, but in fact there is no socket (remote and local) running on the probe.

This morning I decided to create another vim cheat sheet. One that
works for me. There are a lot of cheat sheets outside, but the most
lack of complexity and the other ones are simply not printable on a
single page. I wrote a cheat sheet that covers a lot of commands, for
example: tabs, searching, splitting and comprehensive editing commands.
This all fits on a single page. You may
download the sheet (pdf) from my site or
you can clone it from GitHub.

From time to time I need to encode or re encode videos. I use mencoder a lot, but since two or three
years I use nothing except ffmpeg. Before you start with video encoding you have to know a little
about common video and audio codecs and the
containers. Some times I hear statements
like “I decoded that video to mkv,
now it is small an has a good quality” …
Whatever, I like to post some ffmpeg command lines that work well for me.

USEFULL COMMANDS

Convert a MPEG2 Transport Stream to simple MPEG2 fo further use or DVD compatibility

ffmpeg -i video1.m2t -acodec copy -vcodec copy output.mpg

Cut videos from starting position to end position (use -t instead of -to to use relative time from starting
point (duration))

More or less two years ago I ordered my first smartphone: a Fairphone (FP1). The target
of the Fairphone company is to build a phone with conflict-free resources,
fair working condition and a open supply chain.
I’m really happy with it. It was delivered with a rooted Android 4.2 out of the box.
The Google apps are optional, you do’nt have to use them. In the next weeks there will be an
upgrade to Android 4.4. This Android-version is already fully supported by Google, really good
for security fixes in the near feature. Due to this positive experiences, I ordered the
Fairphone 2 in the second half of 2015 for my wife.

In February 2016 the FP2 was delivered without root access for the stock Android 5.1. But
right after the startup the torture started. The phone crashed and restarts
immediately, mostly five
times a day during use and in idle mode. No reproduction possible, actually without sim-card
and deactivated wifi. But I have waited, because the OS has the version 1.0.0 and I do not trust
those dot zero releases. But after two updates the version number seems to be more trustworthy: 1.3.6..
Nevertheless same behavior.

I decided to switch to the OpenSource version of the FairphoneOS, which
was released on the 28th of April. Now there is root access, but from then the Fairphone
does not restart if it crashes, now the accumulator has to be removed for a second. After
that the FP2 restarts till the next crash…

There are a lot of people out there with the same problems and the official forum
contains a lot of requests according to the crashes. There were Workarounds, but none of
them worked. I was very patient with Fairphone and waited a lot of time, but in June I have
opened a ticket at the Fairphone support-platform, I got no response so far.