[BlueOnyx:26531] Re: Network settings changing.

[Fungal Style]

Hi Michael,

Thank you for the prompt reply, the server is a VM, but very stock, nothing has been added/removed or fiddled with, this is why I was also puzzled as I have not seen it happen previously and thought maybe an update may have switched something.

So your comment about "/etc/is_aws" if it is present, would that mean that if I set the IP address via the ./network<tab> script, then add an emply file of that name in the location specified the setting for IP and network settings should be locked?
If that is the case, that would make me feel more secure as the reason the the restart was a high resource usage slowing things to a standstill where things were effectively "broken", as the server tends to get hit hard with (wordpress) xmlrpc requests even when they are blocked via .htaccess denial and upon reboot (hard reset), the issue was observed.

I may need to expedite the move to 5211R as I have no idea how it would have lost the settings and went to DHCP (and seemed to be locked in DHCP as the primary setting).

Regards
Brian




-----Original Message-----
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> On Behalf Of Michael Stauber via Blueonyx
Sent: Friday, October 6, 2023 12:54 PM
To: blueonyx at mail.blueonyx.it
Subject: [BlueOnyx:26530] Re: Network settings changing.

Hi Brian,

> Not sure if this has been questioned before, but had an issue earlier 
> today where I had to restart a server and although the server had been 
> running for a long time with a static IPv4 address, it seems it 
> discovered a rogue DHCP server and decided it would use the IP address 
> from DHCP instead. When trying to change the IP address it was a 
> little weird as the settings would not stick as it kept reverting to 
> the DHCP server assigned IP address.


The whole network stack of BlueOnyx doesn't use DHCP at all. When you install BlueOnyx DHCP gets turned off and static network settings are configured. And they remain static unless someone manually fiddles with it or maybe some third party software fiddles with it.

I can't imagine a way how the network settings would switch to DHCP on their own. So I'm as confused as you are why this has happened in your case.

The only way how you can still use DHCP on a BlueOnyx (there are some valid usage cased for this after all) is when you create the (empty) file /etc/is_aws. When that is present, all network related handlers and constructors will no longer have permissions to change your network settings at all. But even then: That doesn't switch your server to DHCP on its own and one has to manually modify the network config files to do so.

--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx