Tag Archives: network

Home network improvements

Currently my home network is pretty simple … at least for a computer scientist! ;-)

Gateway Appliance Picture - License CC BY-SA by Cuda-mwolfe

Gateway Appliance – License CC BY-SA by Cuda-mwolfe

My ISP provided an all-in-one box with TV, landline and network router. The latter being very limited and with a crap WiFi access point (AP). So I’ve been using my old Asus RT-AC68U router as a gateway, a 24 ports switch and a Ubiquiti Unifi AP for providing WiFi in the complete house (and garden). The router and switch went into the basement whereas I’ve placed the AP roughly in the house centre. The ISP box could not be configured as bridge but supported to set a DMZ host, so I’ve configure the Asus router to be the DMZ.

Here is the basic setup:

+--------+             +--------+
|        |    DMZ      |        |          +------------------------+
|ISP Box +-------------+ Router +----------+ Switch                 |
|        |             |        |          +--+------+---+---+---+--+
+--------+             +--------+             |      |   |   |   |
                                              |      |   |   |   |
                                           +--+--+   +   +   +   +
                                           | AP  | Home Network / Lab
                                           +-----+

So I’m using only 2 ports on my router (or more exactly network gateway), the WAN and one on the LAN. This router is the peace in my current network I want to change and I will explain why and how.

Post updated on 2018-06-13.

Continue reading

Ubuntu 18.04 (Bionic Beaver) – Some notable changes for sysadmin and Java dev

If you administer a Ubuntu server or if you are a power user, you might have a look at these particular changes in Ubuntu before and after upgrading. They can impact your installation and the way you use it.

  • NTP is no longer supported (part of Universe), you should use now Chrony. My opinion is that Chrony is not a bad choice either, it’s perhaps smoother in handling leap seconds (via smearing) but obviously less accurate than NTP in the case.
  • The local DNS resolver is no longer dnsmasq but systemd-resolvd. For most user this should be transparent. Note that if systemd-resolvd does not receive a DNS configuration, it will fallback to using Google Public DNS.
  • Network will be now managed by systemd-networkd (or still by NetworkManager on the desktop) for new installation. If you upgrade, you will still have the old `/etc/network/interfaces` file (and al) and the ifup and ifdown scripts. But this is no longer installed on new installation. Instead you have systemd-networkd and netplan. For people upgrading there is (not yet) clear path to switch to the new tools if wished.

Ubuntu 18.04 offers many more changes and I’m looking forward to upgrade my desktop and server. There are other changes not mentioned above which should be evaluated before upgrading. But I consider the above ones as core element which everybody needs whatever the purpose of the server is.

For developers, I would take care with Java and the OpenJDK. Ubuntu 16.04 LTS came with OpenJDK 8 which is the current LTS version of Java. The next LTS version of Java is 11 which is not yet published. Ubuntu 18.04 will come with OpenJDK 10 (a short-term support edition) by default and will switch the default to OpenJDK 11 when it will be released (hopefully only for new installation). Ubuntu will still provide OpenJDK 8 in universe for 18.04 with security support provided until EOL of Ubuntu 16.04 LTS (so until April 2021) to offer developer a transition time (while waiting for Java 11 to be published, matured and application migrated/validated on this new platform).

Testing DNS response time

Since Google released its Public DNS, I was curious about how it would really perform. Thus, I have looked around and I have found a script on the internet that I ran at home, here are the results:

+------------------+--------+--------+--------+
| Domain           | My ISP | Google | OpenDNS|
+------------------+--------+--------+--------+
| lifehacker.com   |  17 ms |  68 ms |  68 ms |
+------------------+--------+--------+--------+
| facebook.com     |  18 ms |  69 ms |  68 ms |
+------------------+--------+--------+--------+
| manu-j.com       |  19 ms |  79 ms |  70 ms |
+------------------+--------+--------+--------+
| reddit.com       |  58 ms |  88 ms |  66 ms |
+------------------+--------+--------+--------+
| tb4.fr           |  16 ms |  64 ms |  67 ms |
+------------------+--------+--------+--------+
| bbc.co.uk        |  55 ms |  65 ms |  67 ms |
+------------------+--------+--------+--------+
| lemonde.fr       |  58 ms |  63 ms |  78 ms |
+------------------+--------+--------+--------+
| dailymotion.com  |  58 ms |  66 ms |  68 ms |
+------------------+--------+--------+--------+
| faz.de           |  57 ms |  65 ms |  99 ms |
+------------------+--------+--------+--------+
| gmx.de           |  56 ms |  62 ms |  68 ms |
+------------------+--------+--------+--------+

Google Public DNS and OpenDNS performed quite similarly. However, my own ISP is still quicker to respond, a possible answer is that Google DNS in Europe are located in Frankfurt, Germany.

N.B.: these tests were performed on a wireless link under Mac OS X Leopard in Toulouse, France. If you want to run the script on a Mac, you should change the first line of the script to #!/bin/bash

Update 2009.12.10: