On a sunny day (22 Jun 2018 19:49:51 GMT) it happened A. Dumas
 wrote in
:

>Jan Panteltje  wrote:
>> Best is to give it a fixed IP address anyways.
>
>Perhaps, but don’t fix the ip address on the client, leave it on dhcp and
>use your router to assign a fixed address. 99.3% of routers currently on
>the market can do that.

For some, that is possibly the best solution, yes,
I have a bunch of computers, sensors, including some raspis, on the LAN.
The LAN is on 24/7 while the cable modem ('router') is not.
Things are restarted, connected, disconnected all the time.
You can give the computers names in /etc/hosts:

...
192.168.178.154     camera4
...

and from that moment on refer to it by name:
~# ping camera4
PING camera4 (192.168.178.154) 56(84) bytes of data.
64 bytes from camera4 (192.168.178.154): icmp_req=1 ttl=255 time=0.738 ms


There are other reasons for fixed IP addresses too,
some are hard-coded in the sensors (internet of things)
and can only be changed via some serial config program, UDP based sensors.
If you let a router assign the addresses then chances are for a conflict.
Fixed IP address are also much more convenient in testing and debugging.

And also in the router (cable modem in my case) port forwarding is specified,
for example port 80 to the web server raspi, to some other system for ssh, etc
etc.
and that needs a fixed address specified.
And then there is MAC based filtering only allowing some MACs on the Wifi.
There are probably more reasons but it is still early Saturday morning ...
:-)

Last night I wrote a new version of ip_to_country,
need to see if I can make it faster using successive approximation in the very
very long IP list.
But it does work, finds most countries (all so far).
If people need it I can put what I have now on the website, ask here.
Work in progress.

--- SoupGate-Win32 v1.05