It is year 2122, we’ve finally succeed to fight climate changes and some developers have just removed IPv4 support from Linux Kernel. Now when connecting to a WiFi access point, a computer only receives an IPv6 configuration. What are the differences from an IPv4 network ?
It is pretty easy to know by heart IP addresses of useful hosts inside an IPv4 LAN network. But with IPv6, It is way more difficult to memorize these addresses.
There is a Pi-hole DNS inside my home network since a while, it is a really powerful add blocker system. While I was looking for a DNS64 solution, I discovered Pi-hole did not have a DNS64 option. At first, I was afraid to have to choose between the Pi-hole or the DNS64. But then I discovered several methods to combine Pi-hole with an external DNS64 service.
Introduction For many purposes, it is been a while since I wanted to have a NAT64 gateway inside my LAN. Sadly, at the time of this writing, my home router does not propose that kind of service. So why not trying to run it on a Raspberry Pi ? NAT64 gateway is mainly used to reach IPv4 network from IPv6 network. There are many possible applications, such as opening an IPv6 access to a server farm that was only designed to operate through IPv4, or giving an access to IPv4 Internet for hosts only having an IPv6 configuration. This article describes how to configure a Raspberry Pi as a working NAT64 gateway with the help of the Tayga software.
Introduction I spent years using both SSH and GnuPG, without really taking care about how were built fingerprints. Lately I started to migrate from ssh-agent to gpg-agent and a new player entered the game: Keygrip. That was enough, I needed to know exactly what was behind these three identifiers.
Introduction Configuring an OpenVPN infrastructure does not require to understand every inner processes. As soon as the goals are reached, most of the time there is no need to go further into the software mechanisms. But through this article, I wanted to go into a more advanced understanding of: the OpenVPN 2.4 IPv4 routing policy
Introduction Configuring an OpenVPN infrastructure does not require to understand every inner processes. As soon as the goals are reached, most of the time there is no need to go further into the software mechanisms. But through this article, I wanted to go into a more advanced understanding of: the OpenVPN 2.4 IPv6 routing policy
Introduction The way a VPN works is quite simple, a client connects to a server, a ciphered tunnel is created between the client and the server. And as soon as this tunnel is up and running, the client and the server start to exchange their network traffic trough that tunnel. There are many possible applications to create with a such tool, this article focus on the following(s): Avoiding to forward the entire traffic through the VPN tunnel
Introduction The way a VPN works is quite simple, a client connects to a server, a ciphered tunnel is created between the client and the server. And as soon as this tunnel is up and running, the client and the server start to exchange their network traffic trough that tunnel. There are many possible applications to create with a such tool, this article focus on the following(s): Reaching the VPN server through both IPv4 and IPv6
Introduction The way a VPN works is quite simple, a client connects to a server, a ciphered tunnel is created between the client and the server. And as soon as this tunnel is up and running, the client and the server start to exchange their network traffic trough that tunnel. There are many possible applications to create with a such tool, this article focus on the following(s): Exchanging both IPv4 and IPv6 traffic trough the VPN tunnel