<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Route on Michael’s Domain</title><link>https://jeltsch.org/en/tags/route/</link><description>Recent content in Route on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/route/index.xml" rel="self" type="application/rss+xml"/><item><title>Routing network traffic through two different NICs</title><link>https://jeltsch.org/en/route/</link><pubDate>Sat, 03 Jan 2026 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/route/</guid><description>&lt;p&gt;I am just copying a lot of files from our NAS-Backup do my laptop. Since the WiFi was too slow (1 TB takes a few hours in the real world), I connected the NAS directly to my laptop with an ethernet cable. Both machines needed to setup their IP address manually within the same network (which can be whatever; I used 192.168.8.150 for my laptop and 192.168.8.199 for the NAS, and Netmask for both 255.255.0.0). Since this &amp;ldquo;internal&amp;rdquo; network does not provide internet access, my Ubuntu 24.04 laptop fell automatically back to WiFi. To force the laptop to use the wired network, I needed to deactivate WiFi. But now I cannot get online without WiFi. So I needed to tell the computer to use the wired network only for the NAS which has the IP 192.168.8.199. The command I needed is:&lt;/p&gt;</description></item><item><title>OpenVPN server on pfsense and client on Ubuntu 16.04</title><link>https://jeltsch.org/en/openvpn_server_on_pfsense_and_client_on_ubuntu_16_04/</link><pubDate>Fri, 02 Nov 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/openvpn_server_on_pfsense_and_client_on_ubuntu_16_04/</guid><description>&lt;p&gt;I have been setting up an 
 &lt;a href="https://openvpn.net" target="_blank" rel="noopener noreferrer nofollow"&gt;OpenVPN&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 server on my 
 &lt;a href="https://www.netgate.com/solutions/pfsense/sg-3100.html" target="_blank" rel="noopener noreferrer nofollow"&gt;Netgate SG-3100 router&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. I hope this makes syncronizing backups to a physically separate location easier. There are many walkthroughs to set up an OpenVPN server on a 
 &lt;a href="https://www.pfsense.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;pfsense router&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 and that works nicely. However, I am using 
 &lt;a href="https://blog.ubuntu.com/desktop" target="_blank" rel="noopener noreferrer nofollow"&gt;Ubuntu&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 16.04 at work and setting up the client requires a bit more than doing the same on MacOS or Windows. On Ubuntu, it is mandatory to update DNS information manually after establishing the VPN tunnel if you have opted for the setting to route all internet traffic originating from the client through the VPN server. If you do no update the DNA resolver information on the Ubuntu client, you can access the the VPN-internal network (in my case 10.0.0.0/24), but you cannot use hostnames. E.g. ping 
 &lt;a href="https://www.google.com" target="_blank" rel="noopener noreferrer nofollow"&gt;www.google.com&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 will fail, but ping 172.217.21.164 will succeed. Similarly, your browser will not find any URLs. And browsing with IP-addresses (&amp;ldquo;http://172.217.21.164&amp;rdquo;) is not very practical.The default configuration on Ubuntu does not allow for this update of the DNS resolver to happen automatically for security reasons. There is a script included in the 
 &lt;a href="https://packages.ubuntu.com/search?keywords=openvpn" target="_blank" rel="noopener noreferrer nofollow"&gt;Ubuntu package of openvpn&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 that updates this information (/etc/openvpn/update-resolv-conf). But in order for this to work one needs to&lt;/p&gt;</description></item><item><title>A permanent static route for Macintosh OS X (10.4.7)</title><link>https://jeltsch.org/en/permanent_route_osx/</link><pubDate>Sun, 10 Sep 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/permanent_route_osx/</guid><description>&lt;p&gt;I have set up OpenVPN on our pribvate network, but our special setup requires manually adding a static entry to the routing table of computers that we want to access from the outside via our VPN server. In SuSE Linux this is a nobrainer as Yast provides a section where to add static routing information. On MacOS X the command line works, but upon reboot the route is lost:&lt;code&gt;route add 10.8.0.0/24 192.168.0.2&lt;/code&gt;Check what the route is for a specific IP:&lt;code&gt;route get 10.8.0.1&lt;/code&gt;The same command has a different syntax on Linux though:&lt;code&gt;route add -net 10.8.0.0 netmask 255.255.255.0 gw 192.168.0.2&lt;/code&gt;In order to preserve the routing information over a reboot I created the folder AddRoutes in /Library/StartupItems. Inside this folder there have to be two files: AddRoutes and StartupParameters.plist . The content of these files is the following:AddRoutes:&lt;code&gt;#!/bin/sh# Set up static routing tables. /etc/rc.commonStartService (){ ConsoleMessage &amp;quot;Adding Static Routing Tables&amp;quot; route add -net 10.8.0.0/24 192.168.0.2}StopService (){ return 0}RestartService (){ return 0}RunService &amp;quot;$1&amp;quot;&lt;/code&gt;StartupParameters.plist:&lt;code&gt;{ Description = &amp;quot;Add static routing tables&amp;quot;; Provides = (&amp;quot;AddRoutes&amp;quot;); Requires = (&amp;quot;Network&amp;quot;); OrderPreference = &amp;quot;None&amp;quot;;}&lt;/code&gt;These files need to be readable and executable by everybody for MacOS X 10.4.7. However, MacOSX might wipe these files with each system upgrade (at least from Mountain Lion to Mavericks my settings disappeared completely). After recreating them, I got the error message &amp;ldquo;Insecure Startup Item disabled&amp;rdquo; at boot and I needed to give the directory and the files the following permissions to make the error to disappear:&lt;code&gt;drwxr-xr-x 4 root wheel 136 Aug 6 22:44 AddRoutes``-rwxr-xr-x 1 root wheel 238 Aug 6 22:43 AddRoutes-rwxr-xr-x 1 root wheel 123 Aug 6 22:44 StartupParameters.plist&lt;/code&gt;However, the route does not get added in Mavericks by this procedure and I could not find any information how to do this.The original information is from the following website: 
 &lt;a href="http://macosx.com/forums/showthread.php?t=267209" target="_blank" rel="noopener noreferrer nofollow"&gt;http://macosx.com/forums/showthread.php?t=267209&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>How to enable VPN clients to access LAN computers that are not running VPN software</title><link>https://jeltsch.org/en/how_to_enable_vpn_clients_to_access_lan_computers_that_are_not_running_vpn_software/</link><pubDate>Tue, 08 Aug 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_enable_vpn_clients_to_access_lan_computers_that_are_not_running_vpn_software/</guid><description>&lt;p&gt;I installed an OpenVPN service on our server. The default setup worked right out of the box. However, I wanted to use a VPN client to perform offsite backups of the computers in our LAN (using the backuppc software). First I installed OpenVPN clients on all of the LAN computers to be backed up, but OpenVPN on MacOS X seems to be a bit unreliable. Therefore I wanted to setup the VPN server to forward requests to our LAN network. The following changes were necessary:&lt;/p&gt;</description></item></channel></rss>