Menu

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.

Show posts Menu

Messages - potes

#1
I also need the DEv1 connected to subnet1.

Now I have  VLAN50 (subnet1) on lagg1 interface and VLAN22 (subnet2) on lagg0 interface. Can I attach a VLAN22 to lagg0 and lagg1? That way I will be able to add another network card to Dev1 (is a LXC container) attached to subnet2.
#2
Hi,

Can anybody help this newbie solving this issue.

I have a device (DEv1) in a VLAN subnet (subnet1). I need that device to have also an IP in another VLAN subnet (subnet2) to be discoverable. As the VLAN are assigned to different interfaces I cannot attach another network card to the Dev1 to connect to subnet2.

Can I use a Virtual IP on subnet2 that will forward all request to the DEv1 IP on subnet1?. How can I do it?

I have been looking on internet and in the forums but I cannot find anything, everything I found about Virtual IP deal with the WAN interfaces.

Thanks
#3
THANK YOU very much, I did it as you told me, I only change the interface of the onboard NIC from bge0 to re0 (te other ones keep there name) and it went seamless.

Quote from: potes on January 21, 2021, 08:49:43 AM
Hi,

after searching I found the install function "opnsense-importer", so for what I understand if I put the configuration in a file named "config.xml" on ''/config'' folder it should configure the new machine with the same configuration, am I right? Should I rename the interface names or it should do the change automatically? in case the names differ

Thanks
#4
Hi,

after searching I found the install function "opnsense-importer", so for what I understand if I put the configuration in a file named "config.xml" on ''/config'' folder it should configure the new machine with the same configuration, am I right? Should I rename the interface names or it should do the change automatically? in case the names differ

Thanks
#5
Hi,

I'm planning to change my Opnsense home machine. I have been looking to how to backup and restore the configurations files, but the problem I found is how I can reach the backup file.
In my actual Opnsense configuration I have a quad network card (VLAN configuration) that I want to put in my new machine so I cannot use both machines at the same time, so If I disconnect the old machine and I connect the new one I cannot access my nextcloud server (where is the backup).

Is there anyway to have the backup file on the pendrive where I have the installation image to upload via command line from the installation menu? Or is there any way to upload the backup to a new installation where the only machine at the network is the opnsense machine?

I know it probably wont work, but If I take out the hard drive of the old machine (HP Thin Client T610 plus), and put it on the new machine (HP Thin Client T620 Plus), will work?

Thanks in advance.
#6
Hi toxic, thanks for sharing the set-up, but for what I know (really little as I'm learning), I think is missing the test to see if the unbound service is working. How the machine know that unbound has stop? Thats not done by the test?

Regards

Quote from: toxic on January 03, 2021, 11:44:23 PM
Same issue here, unbound keeps crashing. I tyed the opnsense-revert thing, we'll see if it holds


Quote from: Sabkor on December 29, 2020, 10:27:34 AM
For now, I *think* I've setup a monit test to restart unbound if it crashes. Never used monit before, so we'll see if I did it right...
Meanwhile I tried monit for the first time as well.
I *think* also I got it, but it took me a lot of tries, so for those who might be even more lost than I am, here is what I did in the monit>settings>service settings : add a new service as you can see in the attached picture.

Attached as well, in the monit>status you'll see it has found the proper process id.

I even stopped unbound and it got restarted within the 120 seconds of polling interval.

If you want to make it check faster, it happens on the first settings page, I think that is what would be the polling interval.

Couldn't find a way to get an email notification when the service gets restarted though... At least it restarts ;)
#7
Quote from: alexroz on January 01, 2021, 07:57:24 PM
Quote from: potes on January 01, 2021, 07:51:44 PM
Quote from: Sabkor on December 29, 2020, 10:27:34 AM

For now, I *think* I've setup a monit test to restart unbound if it crashes. Never used monit before, so we'll see if I did it right...

Hi,

I'm also newbie, and also having the same issue with the unbound service stopping. Where you able to create a monit service to restart unbound when stop? can you share the configuration?

Thank you very much

I'm newbie myself but found this topic in documentatin: https://docs.opnsense.org/manual/monit.html#example-1

As I said before i'm newbie (learning with an opnsense at home), and I don't know which ''condition'' should I put to test that unbound is working and for the ''service settings'' which statements to put on ''PID File'', ''Start'' and ''Stop''.

Regarding the patch, i though it was good idea to learn how to use monit to restat a service that stop
#8
Quote from: Sabkor on December 29, 2020, 10:27:34 AM

For now, I *think* I've setup a monit test to restart unbound if it crashes. Never used monit before, so we'll see if I did it right...

Hi,

I'm also newbie, and also having the same issue with the unbound service stopping. Where you able to create a monit service to restart unbound when stop? can you share the configuration?

Thank you very much
#9
Hi everyone,

First of all say that I'm a newbie and I'm on my first opnsense/freebsd install, but as I was able to solve the issue I thought it was a good way to share with all of you.
I have also a HP thin Client 610 plus and I'm installing opnsense on it, I want 64bit with 8Gb.

When I start installing it I got the same error that appear here (is how I found this post). Initially I use the "safe mode" trick to be able to start the machine, but with only one core I was no happy. After reading some other post with similar errors (like disable acpi.... DON'T DO IT...), I start playing around with diferent option on the HP BIOS, and finally found the way to start 64 bits opnsense without any special configuration at boot level.

At HP BIOS, on boot order, we only have to disable all devices under EFI and use instead Legacy, and it works perfectly. I have to disabble it two times, the fisrt time when I boot the installer via USB and a second time on the first boot after the install. I don't know why, the the EFI mode was enable again on the SSD that I install opnsense.

Wish this help someone.