Messages

16

22.1 Legacy Series / Re: Getting back in to a "locked" OpnSense box using console

« on: April 14, 2022, 07:44:47 am »

looks like restoring from a backup is a top-level option.

I'll try that in a moment and will report back.

)(*&^#@$! Firefox . . . how I love thee!

From the recesses of my brain upwelled a memory / thought that maybe I should clear my Firefox cache, etc.  This has sometimes helped when having problems accessing protected sites (although usually when I am presented with authentication dialog which I was not getting from OpnSense at all).

Lo and behold! I have logged in to OpnSense, without resorting to console!

Either way, I would still like to hear any ideas about my inability to login via SSH.

I will investigate this further in another moment.  There does not seem to be an anti-lockout (or maybe it was actually "auto-lockout" !!) rule.  So much for the double check (referenced above) I thought I had performed.

17

22.1 Legacy Series / Re: Getting back in to a "locked" OpnSense box using console

« on: April 14, 2022, 06:45:42 am »

what are the steps to restore from a backup when in the console?

From a screenshot of the console I just found elsewhere online, it looks like restoring from a backup is a top-level option.

I'll try that in a moment and will report back.

Either way, I would still like to hear any ideas about my inability to login via SSH.

18

22.1 Legacy Series / Getting back in to a "locked" OpnSense box using console

« on: April 14, 2022, 06:32:51 am »

I am a very recent OpnSense convert and enjoying it tremendously so far.  It is incredibly intuitive and/or cleanly laid out compared to OpenWRT, DD-WRT and especially MikroTik's RouterOS with which I had multiple false starts.  Thank you OpnSense developers (and predecessors) for your great work!

In spite of the intuitiveness, this afternoon I managed to lock myself out (of the web interface) while experimenting with VLANs.

Surprisingly, I am NOT able to log in via SSH to get anything done.  Connection attempts to a known correct port time out with either the admin or my single "named" user.

I am fairly certain I gave each user SSH access and that the non-standard SSH port was added (automatically, then double-checked) to the "anti-lockout" rule.  It is, however, possible I did that on an earlier test installation.

So, I guess I am left with attaching a keyboard and display.

My related questions then are:

• Where are the docs showing how to use the console? [I have poked around in https://docs.opnsense.org/manual/  and found nothing, even in the troubleshooting section, which surprised me quite a bit.
• In the absence of such documentation what are the steps to restore from a backup when in the console? (I assume it might be much quicker to do that than find and fix whatever arcane thing I was trying to do with VLANs (especially since I applied a bunch of changes (I know, I know!  )

I'm hoping to not have to reinstall to restore a backup (although that would not be a worst-imaginable case scenario! )

Thanks in advance for any insights.

19

22.1 Legacy Series / Re: os-ddclient

« on: April 14, 2022, 06:12:52 am »

Hi @Greenlan

Good on you for taking the time to provide constructive information.

You're welcome!  Paying it forward is great.  I think it is especially important in the open source arena where so many are volunteering in the first place.

I provide a ton of tech support to people who rarely reciprocate with other-kind help and often don't even pay the bills in the case that some are "clients," so I am particularly sensitive to this.

What I think would be ideal is for contributors to help expand the official docs as the ddclient plugin is developed. Then all of this sort of information is in one place and easily accessible:

Interesting.  I thought this sort of detail might be in the docs and actually looked there first, but found it entirely devoid of specific implementation details.

Do you really think that this fine granularity would be accepted?  [ A subsection would need to be added at minimum. ]

20

22.1 Legacy Series / Re: os-ddclient

« on: April 11, 2022, 02:50:49 am »

I'm a new OpnSense user (about 3 days) and first time poster.

I thought I would post something helpful in this thread before pestering anyone with possible assistance requests elsewhere within these forums! 

NameCheap is previously acknowledged as working in this thread, but there seems to be no previous detailed instruction set for the "new" os-ddclient.

So, for assistance with getting dynamic DNS in a NameCheap account working with OpnSense, here's the exact "setup-fu"


Connecting OpnSense to NameCheap's "A+ Dynamic DNS Record" service

    Service: NameCheap
    Username: example.com  [ put your TLD in Username _ do NOT use the NC account Username ]
    Password: the "special" NameCheap Dynamic DNS password   [ NOT the NC account password ]
    Hostname: subdomain only [ or @ ... if you want all subdomains routed to this IP address ]
    Check ip method: Interface
    Force SSL: Yes
    Interface to monitor: WAN_Interface


It took me a while to figure out the Username issue as various other DynDNS update clientsI have used have treated this a bit differently!

Hopefully this will help future searchers with any challenges using OpnSense with NameCheap dynamic DNS services.