Messages

16

21.1 Legacy Series / Re: DHCPv6 [LAN] Settings

« on: May 10, 2021, 09:57:26 pm »

Under Interfaces (for LAN), you probably need to tick the box to allow manual adjustment of dhcpv6 for it to show under services.

Thank you for the reply. I did not know about this change in settings. Initially, I just enabled the manual mode and then noticed that DHCPv6 stopped working. I went into the DHCPv6 settings and enabled the server, but it still wasn't working. Finally, I noticed that RA was disabled.

IMO, it would be more straight-forward if enabling manual mode would cause the settings for DHCPv6 and RA to be set to the same settings as they were in auto-mode. They must have been abled in auto-mode, otherwise DHCPv6 would not have been working. Anyway, not a big deal...

17

21.1 Legacy Series / DHCPv6 [LAN] Settings

« on: May 10, 2021, 05:12:54 am »

I just did a clean reinstall of 21.1. Normally, I prefer to display lease times in local time, not UTC. I found the DHCPv4 [LAN] settings in the usual place, but when I looked for the DHCPv6 settings, I noticed there is no page for [LAN] settings. Have these settings been moved somewhere else?

18

21.1 Legacy Series / Re: Update Problems

« on: May 10, 2021, 04:13:05 am »

I saved the settings, then restored default settings, then reloaded only a few settings from the saved settings, such as CA and certificate, then I manually configured the DHCPv6 WAN settings. After that, it's working again. Very strange that this happened, since it was working up to an update in April (a bit over two weeks ago), then it stopped working. Even more strange, since whatever happened seems to have affected both the release and development systems. I haven't made any changes to either of these systems in months, other than keeping them updated.

19

21.1 Legacy Series / Re: Update Problems

« on: May 08, 2021, 08:46:38 pm »

No changes since installation. Very simple systems, no packages, mostly using default settings.

20

21.1 Legacy Series / Re: Update Problems

« on: May 08, 2021, 08:34:32 pm »

I can look it up using nslookup, but dns lookup from within opnsense isn't working. I tried restarting unbound, but that made no difference. Really strange.

21

21.1 Legacy Series / Update Problems

« on: May 08, 2021, 07:00:56 pm »

I have a couple of OPNsense VMs, one running the release version and the other running the development version. This morning, I tried to update the development version from the web user interface and encountered errors with the repository. I tried to update the release version with the web user interface and encountered similar errors. I've attached screen captures. Is there a problem with my systems?

22

21.1 Legacy Series / Re: Console menu gone in 21.1.3 / 21.7.a_159?

« on: April 07, 2021, 04:12:39 pm »

Going to System / Access / Users / root and saving fixed it. I didn't change anything and nothing changed in the config.xml.

(I saw the same behavior when using the local VGA console and echo $shell told me that it was actually running /bin/csh.)

Cheers

Maurice

I'm experiencing the same problem and saving the root user did not make any difference.

For what it's worth, I noticed that the most recent update before this happened was that the SSH package was reinstalled.

23

21.1 Legacy Series / OPNsense 21.7.a_314 Console Login Directly to Shell Mode

« on: April 07, 2021, 03:59:00 am »

I updated my development system to OPNsense 21.7.a_314. After the update, when I login to the console, it goes directly into shell mode. There are no obvious other problems. I've never encountered this before. Is this a known problem?

24

21.1 Legacy Series / Re: Native-kernel wireguard support for 21.1 feasible? FreeBSD 13 may have it

« on: March 17, 2021, 06:28:10 am »

That means Netgate convinced FreeBSD to do what Scott Long suggested. Oh man, get ready for more shit in the next couple of years. This is just the beginning of the drama.


Cheers,
Franco

I'm not sure which is worse, that Netgate rammed their broken implementation of Wireguard into FreeBSD a few weeks before a release, expecting it to be part of the release, or that FreeBSD let them. It's amazing.

25

21.1 Legacy Series / Re: Many thanks and the traffic graphs are beautiful!

« on: March 16, 2021, 05:38:41 pm »

Agreed, the graphs look great. It would be nice if they could display both IPv4 and IPv6 traffic.

26

20.7 Legacy Series / Re: Installer for 20.7 hangs at "Select Task" on Hyper-V Server 2019 Generation 2 VM

« on: January 18, 2021, 02:52:31 am »

I have three different OPNsense VMs running on windows server 2019 hyper-v (not all at the same time, but different versions). It's correct that the installer still requires being interrupted in two places, but aside from that, it installs and runs fine. The installer problem is not a show-stopper.

As for your other problem, I haven't experienced it. I occasionally encounter a message that OPNsense cannot communicate with the update server, but it usually works if I try again.

27

20.7 Legacy Series / Re: Question about updating beta

« on: August 13, 2020, 01:24:44 am »

Worst case you borked your ABI mirror link...

Try this first:

# opnsense-revert -r 20.1.9 opnsense-devel

If that doesn't download...

# opnsense-update -sn "20.1\/latest"

And try again.


Cheers,
Franco

Thank you for the reply.

I tried opnsense-revert -r 20.1.9 opnsense-devel. It completed without any apparent issues. I rebooted after that and it's working. However, after that, I did opnsense-update and opnsense code core.

Here is the output:

Code: [Select]

root@OPNsense:/usr/core # opnsense-code core
Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
ABI 20.1 is no longer supported
Fetching origin
Already up to date.

After that, I tried opnsense-update -sn "20.1\/latest" and then did opnsense-update and opnsense code core. There was no difference. Something seems to be borked, alright.

Do you have any other suggestions or should should I reinstall it?

28

20.7 Legacy Series / Re: Question about updating beta

« on: August 08, 2020, 04:20:31 am »

I tried git config pull.rebase true before opnsense-code core. The same message appeared as I posted previously.

The system is now at:

OPNsense 21.1.a_15-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020

Is there any way to fix the issue that's causing the message?

29

20.7 Legacy Series / Question about updating beta

« on: July 30, 2020, 01:40:53 am »

I'm running this version:

OPNsense 20.7.b_244-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020

I updated using the following"

opnsense-update

This results in:

Nothing to do.

opnsense-code core

This result in the following:

Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
ABI 20.1 is no longer supported
Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.

What is the recommended next step?

30

20.7 Legacy Series / Re: 20.7-BETA images with HBSD 12.1

« on: May 29, 2020, 06:46:49 am »

Remember to install the new dhcp6c...

I didn't update anything. dhcp6c seems to be working fine as-is.