I had a problem with RTNetlink (rtnl) address configuration on Linux. The effect of the NEWADDR command was realized only a few seconds later than the rtnl_talk() returned. Here is why...
I have used serial terminal interfaces for communication for a while. For message generation and parsing I have used the previously introduced sercomm solution. For testing on Linux systems, I have used the following stuff.
I have used serial message generating and parsing solutions for a while. I implemented it on many ways before, but a few years ago I have written an universal one.
My colleagues and I have used this stuff in many projects. It works on Linux and in embedded systems (i.e., ATMEGA8).
I had some serious problems with destination option XFRM processing on newer Linux kernels (3.3 and 3.4). The sent Binding Update (BU) message was corrupt, because the Destination Option header overwrote the beginning of the MH part.
While testing the binaries with valgrind, which use the pthread library, the results usually contains several possible leak sections, which are raised inside the pthread library.
A major update of MIPv6 Packet Flows document has been created.
New MIPv6 related protocol descriptions has been included: Hierarchical Mobile IPv6, Enhanced Route Optimization, HA Reliability Protocol (I-D), Global HA-HA (I-D)
Sometimes I have to check some details, for example in the routing tables on the Home Agent or on the Mobile Router. In this case I always had to start my test environment, and lookup the tables.
Now I made a simple dump about the most important things:
I would like to setup a VPN server for my home NAS. I would like to connect to it from my MacBook and my Android phone out-of-box. I have decided to use L2TP with IPsec. I had an old, unused Fonera 2.0.