Hi,

I have a Debian 9 netbook here. Because I have an unusual setup here, I need to use manual IP address configuration. I used the default network manager to setup the static IPv4 and IPv6 addresses on the wifi interface. When I start the system, all works fine, and the correct IPs and routing information as I setup via the GUI are in place.

However, when there's a network upset (most probably due to the router rebooting, or some other wifi disturbance), the static IPs are gone and are replaced by a DHCP assigned IPv4 address. This causes a number of issues, breaking connectivity with the BBS that is running on the system.

In the good old days, I'd have done a total manual configuration, and this would have stuck, but I decided to use the tools provided for 2 reasons:

1. To work with the new ways of doing things, rather than figting the system.

2. To simplify the configuration of the wifi (i.e. not having to mess around with wpa-supplicant directly).

Anyone seen this behaviour? And better still, anyone have a solution?
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

26 May 19 20:04, you wrote to all:

I have a Debian 9 netbook here. Because I have an unusual setup here, I need to use manual IP address configuration. I used the default network manager to setup the static IPv4 and IPv6 addresses on the wifi
interface. When I start the system, all works fine, and the correct IPs and routing information as I setup via the GUI are in place.

However, when there's a network upset (most probably due to the router rebooting, or some other wifi disturbance), the static IPs are gone and are replaced by a DHCP assigned IPv4 address. This causes a number of issues, breaking connectivity with the BBS that is running on the
system.

In the good old days, I'd have done a total manual configuration, and
this would have stuck, but I decided to use the tools provided for 2 reasons:

1. To work with the new ways of doing things, rather than figting the system.

2. To simplify the configuration of the wifi (i.e. not having to mess around with wpa-supplicant directly).

Anyone seen this behaviour? And better still, anyone have a solution?

Have you considered assigning the netbook a static IP address using DHCP?

I believe most modern routers support this, though I prefer to disable my router's DHCP server and run my own dnsmasq service on a separate machine.

dnsmasq has some useful options in dnsmasq.conf:

# Always give the host with ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes #dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m

# Give a host with ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60

# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite

--- GoldED+/BSD 1.1.5-b20180707
* Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)

On 05-29-19 21:39, andrew clarke wrote to Tony Langdon <=-

Have you considered assigning the netbook a static IP address using
DHCP?

Not an option. I run multiple networks on the one wire, and the main IP(v4) address is not on the same logical network as the DHCP server. Otherwise I would have gone down that road.

The other issue is I'm losing my IPv6 address as well, when DHCP kicks in.


... See if you can guess which drink will make me love you.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)