Messages

1

General Discussion / Re: How can I change the mount device?

« on: April 29, 2023, 03:21:21 am »

I just got around to changing the boot file system in /etc/fstab to /dev/da0p3, which worked. Thanks! 

When I edited /etc/fstab, I noticed there's also an entry for a swap file: /dev/gpt/swapfs. I get an error opening it when I reboot, but that hasn't caused any problems (yet.) I've got 8GB of memory, so I should probably create a swap file. How do I create a swap file and where?

2

General Discussion / How can I change the mount device?

« on: February 06, 2023, 02:51:07 am »

In preparation for upgrading from 21.7.8 to 22.1, I thought it would be a good idea to clone my OPNsense SSD in case something goes wrong. But when I boot from the cloned SSD, the root mount fails because the cloned SSD has a different device name than the original SSD. OK, so I entered ufs:/dev/<cloned disk/partition device> and it worked.

Now, how do I change the mount device so I don't have to enter the mount device every time the system reboots? Is it stored where it can be edited or is it in the boot record somewhere that can't be edited?

Thanks in advance for any help.

[I'm thinking if something goes wrong and I have to revert, I can clone the clone back to the original SSD and maybe it'll be assigned the original device name?]

3

19.7 Legacy Series / 19.7.2 Unbound DNS requires forwarding

« on: August 17, 2019, 06:51:27 pm »

After updating from 19.7.1 to 19.7.2, Unbound DNS no longer works unless I enable forwarding to DNS servers configured in System...Settings...General. Unbound DNS worked fine without forwarding before the update.

Is this related to the problem reported in this post: [RESOLVED] Force gateway broken? If so, can someone tell me how to apply the patch? And if the patch causes problems, how would I back out of it?

4

19.7 Legacy Series / 19.7 incorrect status for IPV6 Interfaces?

« on: July 17, 2019, 07:11:31 pm »

See attached screen capture. Prior to upgrading, this screen would have shown WAN_DHCP6 Online, PerfectPrivacy_DHCP6 Offline (I've never been able to get that to work in Opnsense or PFsense, which is another topic altogether.) Also, the PerfectPrivacy_DHCP6 Network Monitor would be down. But after upgrading it looks like Opnsense has mixed up which IPV6 interface is which. It shows PerfectPrivacy_DHCP6 Online, which isn't true, and WAN_DHCP6 Offline, which also isn't true. And it shows the WAN_DHCP6 Network monitor down and the PerfectPrivacy_DHCP6 monitor running.

When I check the WAN and VPN connections with ipleak.net, everything looks the same as it did before upgrading, so I think everything is working but the status reporting is confused.

5

19.1 Legacy Series / Re: 19.1 r1 setup console stopped at booting

« on: February 13, 2019, 12:57:01 am »

I had this problem after upgrading from 18.7.4 to 19.1.1.

I'm using a ProtecLi FW4A-0 nano PC with a Lilliput monitor with HDMI input connected to the FW4A-0 VGA port through a VGA-to-HDMI adapter.

Per weust's advice, I went into the WebGUI interface, selected System...Settings...Administration, and unchecked "Use the virtual terminal driver (vt)". The primary monitor was already set to VGA.

Works now.

6

18.1 Legacy Series / Re: Where can I download 18.1.13?

« on: November 24, 2018, 03:00:40 am »

Thanks, but where can I download 18.1.6? I can't find any images other than 18.7.7.

7

18.1 Legacy Series / Where can I download 18.1.13?

« on: November 22, 2018, 02:17:44 am »

I'm having a lot of problems with OpnVPN in version 18.7.x that did not occur in 18.1.13. Where can I find a copy of 18.1.13 to download?

8

18.7 Legacy Series / Strange OpnVPN client behavior in 18.7.7 (and maybe earlier 18.7.x releases)

« on: November 21, 2018, 05:05:07 am »

Before I get into my strange problems with OpnVPN in 18.7.x, the urgent thing I need to know is how to back up to 18.1.13. The download mirrors only have the latest 18.7 version. Where are the legacy versions?

Unfortunately, I’m not sure in which 18.7.x release my problems with OpnVPN started, and I’m not sure exactly which release I popped into when I updated from 18.1. I’m not even sure which 18.1 release I updated from. I hadn’t checked the update status for a few months because all was working we’ll, and when I updated I didn’t note the current and new versions. I probably came from something like 18.1.11 and went to 18.7.6, then updated to 18.7.7 not long after.

Anyway, here are the strange things I’ve seen:

- OpnVPN client randomly stops without warning. The only way I know it’s stopped is if I happen to notice a client that’s supposed to be on the VPN has the ISP IP address instead of the VPN IP address. Sometimes the OpnVPN client won’t restart, and it’s because it gets an error due to the tunnel still being open (i.e., the crash, or whatever it is, leaves the tunnel open.) I can temporarily fix it by running OpenVPN with a different client config (i.e., a different server offered by the VPN service), or I can reboot OpnSense.

- I use a VLAN to route some clients and their DNS requests to the VPN. The “VPN” VLAN is assigned to the client depending on which smart switch port it’s plugged into or which wireless network it’s on. This has worked fine for a long time. After I updated to 18.7.6 or 18.7.7, random clients on the LAN (not the VPN VLAN) would have their DNS requests sent through the VPN instead of the ISP. In some cases, their IP address would stil be the ISP, but in other cases their IP would be the VPN. I think this problem started when I put in a firewall rule passing the static IP address for a LAN printer to clients on the VPN VLAN in an attempt to get clients to be able to discover the printer. When I removed the rule, the problem seemed to go away. But there was nothing about the rule that should have caused this behavior. It’s possible the rule had nothing to do with it, but removing the rule reset the firewall.

- Before I describe the next problem, be advised that I’ve never been able to get IPV6 to work with the VPN, though it is supported by the VPN and works via their OpnVPN client on IOS and WINDOWS. I wasn’t able to get it to work on pfSense, either, even after spending many hours trying, and consulting both the VPN tech support and pfSense forum members. Basically each said the other’s platform “doesn’t do it right”, and I got nowhere. Note that IPV6 works fine in OpnSense through my Comcast ISP.

- The last straw happened tonight. I couldn’t get to any websites on a client connected to the wireless network on the LAN. When I checked the client’s IPV4 address, it was a VPN IP, when it should have been an ISP IP, and it had an ISP IPV6 address! Never saw that before - IPV4 going through the VPN, even though it should have gone through the ISP, and IPV6 going through the ISP. Bizarre.

Did I mention that none of these things happened prior to 18.7.x, and that my configuration hasn’t changed since I updated from 18.1.x?

My sense from reading the thread about OpnVPN firewall rules no longer working in 18.7.x is that OpnVPN is seriously messed up in 18.7.x.

I can’t wait for these bugs to get fixed, so I’d like to back up to 18.1.13. I assume that can’t be done in place and requires downloading a new image and doing a clean install. But the mirrors don’t have any images prior to the current one. Where are the legacy versions?