1
General Discussion / Re: cloud-init NoCloud with OPNsense 21
« on: October 04, 2021, 08:57:32 am »
Do you have any idea?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
General Discussion / cloud-init NoCloud with OPNsense 21
« on: September 28, 2021, 04:18:32 pm »
Hi everyone!
I'm new to OPNSense (also to FreeBSD in general
) and I'm interested to use cloud-init to configure at least LAN (vtnet0) with static ip address, root password and eventually running custom scripts in a OPNsense VM created with Qemu to apply a custom configuration.
I saw that opnsense github repo has cloud-init port [url]https://github.com/opnsense/ports/tree/master/net/cloud-init[/url, so I installed it with:
Then I added cidata.iso image to Qemu as required by cloud-init NoCloud with user-data and meta-data.
I already tested those files on ubuntu server 21 and kali linux. They are correct at least on those OSs
I found the cdrom as /dev/cd0 and mounted with
I also edited /etc/fstab appending this line:
to auto mount the cdrom at boot.
Finally, I created (because unexisting) /etc/rc.conf with this content:
and restarted my OPNsense VM.
What I expect now is that cloud-init will start automatically at boot.
However this doesn't happen, probably because I have to configure something.
If I run `cloud-init init` via terminal it throws error:
On both Kali Linux and Ubuntu Server it works easely.
I have some questions about this:
1) Is it possible to use cloud-init port with NoCloud and a cdrom (cidata) with configuration files or it supports only Cloud services with OpenStack and so on?
2) Is my configuration above correct or am I missing something?
3) Why does it appear the error above? How can I fix it?
Thank you.
I'm new to OPNSense (also to FreeBSD in general
) and I'm interested to use cloud-init to configure at least LAN (vtnet0) with static ip address, root password and eventually running custom scripts in a OPNsense VM created with Qemu to apply a custom configuration.I saw that opnsense github repo has cloud-init port [url]https://github.com/opnsense/ports/tree/master/net/cloud-init[/url, so I installed it with:
Code: [Select]
pkg install net/cloud-initThen I added cidata.iso image to Qemu as required by cloud-init NoCloud with user-data and meta-data.
I already tested those files on ubuntu server 21 and kali linux. They are correct at least on those OSs
I found the cdrom as /dev/cd0 and mounted with
Code: [Select]
mkdir -p /media/cdrom
mount -t cd9660 /dev/cd0 /media/cdrom
I also edited /etc/fstab appending this line:
Code: [Select]
/dev/cd0 /media/cdrom cd9660 ro 0 0
to auto mount the cdrom at boot.
Finally, I created (because unexisting) /etc/rc.conf with this content:
Code: [Select]
cloudinit_enable="YES"
and restarted my OPNsense VM.
What I expect now is that cloud-init will start automatically at boot.
However this doesn't happen, probably because I have to configure something.
If I run `cloud-init init` via terminal it throws error:
Code: [Select]
stages.py[WARNING]: Failed to rename devices: Unexpected error while running command.
Command [`ip`, `-6`, `addr`,`show`, `permanent`, `scope`,`global`]
Exit code: -
Reason: [Errno 2] No such file or directory: b`ip`
Stdout: -
Stderr: -
No `init` modules to run under section `cloud_init_modules`
On both Kali Linux and Ubuntu Server it works easely.
I have some questions about this:
1) Is it possible to use cloud-init port with NoCloud and a cdrom (cidata) with configuration files or it supports only Cloud services with OpenStack and so on?
2) Is my configuration above correct or am I missing something?
3) Why does it appear the error above? How can I fix it?
Thank you.
Pages: [1]