[Bitnami Moodle 4.3] Static IP failure

[martinjp84]

Platform

Virtual Machine

bndiagnostic ID know more about bndiagnostic ID

Nope

bndiagnostic output

No response

bndiagnostic was not useful. Could you please tell us why?

Not related

Describe your issue as much as you can

Instructions for static IP are incorrect for latest debian 5.10/moodle 4.3 version.

https://docs.bitnami.com/virtual-machine/faq/configuration/configure-static-address/

Address reverts to DHCP during reboot. Restarting systemd-networkd.service resolves it temporarily.

[mdhont]

Could you explain what you mean with temporarily? Does it revert after reboot after restarting systemd-networkd.service?

[martinjp84]

It reverts after a reboot

…

________________________________ From: Michiel ***@***.***> Sent: Wednesday, February 21, 2024 9:21:52 PM To: bitnami/vms ***@***.***> Cc: martinjp84 ***@***.***>; Author ***@***.***> Subject: Re: [bitnami/vms] [Bitnami Moodle 4.3] Static IP failure (Issue #1403) Could you explain what you mean with temporarily? Does it revert after reboot after restarting systemd-networkd.service? — Reply to this email directly, view it on GitHub<#1403 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB7ZMYXCWG5SAQDR4URI4SDYUYULBAVCNFSM6AAAAABDEIZM3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGM3TQOJTGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[martinjp84]

Editing /etc/systemd/network/25-wired.network and matching either the interface name or alt name fails to keep the static IP after a system reboot. Static IP is always applied after restarting systemd-networkd.service.

File in /etc/network/interfaces.d called '50-cloud-init' is taking priority, editing this file with the below contents will allow a static IP but it will not update the welcome screen section 'You can access the application at http://ip-address', the IP here will remain the same as before.

50-cloud-init file config for static IP. Note that 'ens3' should be replaced with the real interface name or alt name.

The loopback network interface

auto lo
iface lo inet loopback

The primary network interface

auto ens3
iface ens3 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.254

[martinjp84]

Disabling cloud-init by creating a file at - /etc/cloud/cloud.cfg.d/99-custom-networking.cfg and containing 'network: {config: disabled}' does not revert the control back to /etc/systemd/network.

Editing /etc/network/interfaces or /etc/network/interfaces.d/ (latter takes priority), seems to be the current solution

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.