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?ãã---ã þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.auã

Vk3jed wrote to All <=-ãã Vk> I have a Debian 9 netbook here. Because I have an unusual setupã Vk> here, I need to use manual IP address configuration. I used theã Vk> default network manager to setup the static IPv4 and IPv6ã Vk> addresses on the wifi interface. When I start the system, allã Vk> works fine, and the correct IPs and routing information as Iã Vk> setup via the GUI are in place.ãã Vk> However, when there's a network upset (most probably due to theã Vk> router rebooting, or some other wifi disturbance), the static IPsã Vk> are gone and are replaced by a DHCP assigned IPv4 address. Thisã Vk> causes a number of issues, breaking connectivity with the BBSã Vk> that is running on the system.ãã Vk> In the good old days, I'd have done a total manual configuration,ã Vk> and this would have stuck, but I decided to use the toolsã Vk> provided for 2 reasons:ãã Vk> 1. To work with the new ways of doing things, rather thanã Vk> figting the system.ãã Vk> 2. To simplify the configuration of the wifi (i.e. not having toã Vk> mess around with wpa-supplicant directly).ãã Vk> Anyone seen this behaviour? And better still, anyone have aã Vk> solution?ããI'm not a Debian expert, but I do use a couple of Raspberry Pi's ãrunning Raspbian (which is basically Debian Stretch). What has ãalways worked fine for me is to edit /etc/dhcpcd.conf and just add ãthe following block on to the end of the file:ããinterface wlan0ãstatic ip_address=192.168.1.99/24ãstatic routers=192.168.1.1ãstatic domain_name_servers=192.168.1.1ããThat's it. Obviously adjust IP's and maybe the interface name to ãsuit.ãã... Internal Error: The system has been taken over by sheep at line 19960ã--- MultiMail/Linux v0.52ã þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FLã

On 05-26-19 08:22, Dan Clough wrote to Vk3jed <=-ãã DC> I'm not a Debian expert, but I do use a couple of Raspberry Pi'sã DC> running Raspbian (which is basically Debian Stretch). What hasã DC> always worked fine for me is to edit /etc/dhcpcd.conf and just addã DC> the following block on to the end of the file:ãã DC> interface wlan0ã DC> static ip_address=192.168.1.99/24ã DC> static routers=192.168.1.1ã DC> static domain_name_servers=192.168.1.1ãã DC> That's it. Obviously adjust IP's and maybe the interface name toã DC> suit.ããHmm, and IPv6 as well? Spose all I can do is give it a try. :)ããJust had a look. Looks like my system is using dhclient. I've added theãequivalent options (for IPv4) to dhclient.conf.ããã... We are the very model of cartoon individuals.ã--- MultiMail/Win32 v0.49ã þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.auã