Messages

Try this as root to put the shell back:

Code Select Expand

chsh -s /usr/local/sbin/opnsense-shell root

This did it, but it didn't stay.

Try this as root to put the shell back:

Code Select Expand

chsh -s /usr/local/sbin/opnsense-shell root

This did it!

Better to turn off backups in System: Settings: Misc -- likely caused by a damaged netflow backup

you want to find out now not later

Well, I turned off backups as above.  had a backup and installer ready. The reboot went without any issue.

Dare I try turning the backup back on?  Or just leave it off forever?

Thank you!

[DO YOU THINK ALL IS SAFE?]

Hi, the situation is, I updated to 24.7.12.  Everything seemed fine.
[I needed to move some plugs around]
Pressed "shutdown" on the GUI.  GUI said it was shutting down.
A minute or so went by.
it had not shut down so I used the terminal screen "5 Power off the system"
[did my stuff]
went to turn it back on.  As said in this post.

Code Select Expand

    tar: Retrying... 
    tar: Damaged tar archive 
    tar: Retrying... 
    tar: Damaged tar archive 
    tar: Retrying...`

https://forum.opnsense.org/index.php?topic=15735.0


As this thread said

Code Select Expand

control-c saved the day.  It just booted.
As the thread said, I have now, (not before) "System: Settings: Miscellaneous and set "disable" for all periodic backups."

I am on the "hobbyist" side of the experience fence here.  I am scared to death to reboot.  I powered off to add a UPS, so that is good, but one day I will have to update.  Perhaps my double "shut down" didn't let the periodic backup work?

DO YOU THINK ALL IS SAFE?  Or should I reinstall and restore configs?  I don't have a broken device do I? I have not touched it as its working.

Thank you in advance.

It's a cosmetic leftover. And you can reset the plugin conflict from the System: Firmware: Status page...


Cheers,
Franco

THANK YOU

[it's not supposed to change colors.]

it has stuck to yellow since then.  And I think this does answer it, it's not supposed to change colors.  I just hope its the monitor going bad and not the OPNsense box.

BUT, you didn't read my "long version" as it was stuck in a boot loop, it did not load.  :-(  Maybe you are skilled enough to reflash the ISO via ethernet, But I am not.


also, side note, I get impatient with the GUI, it says "rebooting" and hangs there sometimes for a while, if I turn on the terminal monitor, I can see it running through its checks.  I don't type in it much, but it's nice to glance at or in emergencies like this one when you are relaoading!

Short version:
My Console color is changing from white to yellow, and seems to be changing slowly. Is this correct?

Long version:
I don't  use the console much, but I tried to rollback to a previous saved config and ... it went poorly. I got an boot error, i believe with the kernel and was not good!  Text looped constantly on the screen.  Sometimes it would load something with a "root" login and I could not log into console with password!  I don't know if that was something changed in an update, or I did it previously, or the failed rollback did it, but root login was turned off in settings.  I don't think it was me, so the other two!  I am not an expert, but what I did was reinstall OPNsense.  (Which by the way, downloading it, with no internet, involved me digging out some old gear out of a closet. That's another long story, and a lot of fun.)   AND i was worried that the device was going bad as the terminal text kept changing color.  (Seems to be stuck on yellow now.)  (It is an old monitor, cant discount that possibility either.) once I got to the interface, I was able to reinstall the config.  All the while it kept changing slowly from white to yellow.

I am in a similar spot, now, with similar questions. Would love a response or if you figured it out, please provide a link or guide!

Thanks!

I currently have two PiHoles on two servers.  I set up KeepaliveD so there is a master and slave, as a failover system.  In the config of KeepaliveD the VIP is stated.  I also added the VIP to the OPNsense interface.

When I do firewall rules, do I just add the two server IP's or do I need to include the VIP?

I guess I am trying to understand how a VIP works, the documentation is not helping, and I cant find anything else on it.  I am not doing CARP or anything, and that is the type of googling I keep finding, like a VIP for HA, with CARP involving the WAN and everything.  I just need an internal LAN VIP.

I have done something wrong, I can ping the VIP and shut down a server, and I see failover and it go back to pinging, but when I shut down the 2nd server, it just keeps pinging!   And its similar for the PIHoles.  If I shut down both piholes, the DNS still works on the PC.

still gettin em

[What does work]

I am able to use the GUI, but having trouble with tthe KVM switch that goes to VGA. I tried "root" and when I type my user it says "this account is currently not available"

Leave no stone unturned, I may have done something stupid. 

In System > administration, I have console checked.  It had been working with "VGA"  and I also tried "serial"

What does work is unchecking "Password protect the console menu" However, I had to enter a user name and password.

What am I missing?

My question is currently about interfaces, but it also applies to vlans. How can you allow across subnets?

I have 2 interfaces. Ip range on one is igb1 - 192.168.1.0/24
IP range of the second is igb2- 192.168.69.0/24

On the igb2 69 2nd interface, I plug in a cisco switch. (That's it nothing on the switch.) 192.168.1.11.  So other ip range on this interface. Firewall rules all set to allow all on both interfaces . I can't access it from a computer on the 1st 192.168.1.0 range.

Everything I read says I should be able to access it. I have tried to read about "gateways" and "static routes" and it seems to say I don't need those. Any thoughts? Or do I?