Messages

1

24.7 Production Series / Re: Some bug and i cant boot

« on: November 09, 2024, 02:57:15 pm »

The thread below should be of help

https://github.com/opnsense/core/issues/1091

You will likely need to boot from a USB flash drive to edit the file indicated in that thread. If you don't have one, you will need a working computer to download the ISO/image and create the USB boot drive.

2

24.7 Production Series / Re: 24.7.3 clean install & DNSCrypt proxy logs

« on: September 14, 2024, 01:16:33 am »

Same here. No changes in the logs after updating to 27.7.4 but all the rest works.

The logs will display if you set the time frame to "no limit¨.

3

24.7 Production Series / 24.7.3 clean install & DNSCrypt proxy logs

« on: September 11, 2024, 12:57:27 am »

After a clean installation of 24.7 and upgrade to 24.7.3 I restored the backup of my latest 24.1 Opensense configuration xml.

DNSCrypt is my only LAN DNS server. It resolves locally and also to all LANs.

Only 1 thing did not work well: the DNSCrypt proxy logs page.

2 problems:

1-
After restoring and reboot, the logs displayed no content. Domains were being resolved so it was working.

The default option is ¨Last day¨. When switching to ¨no limit" the logs do show, but.. read below.


2-
notice the alignment in the images. The date, severity and process columns are off.
In comparison, check the columns in the logs for DHCP (last image)


This is a display issue. The proxy is working and logs are being collected.

4

23.7 Legacy Series / Re: I can't find instructions for freedns.afraid.org

« on: April 27, 2024, 06:00:53 pm »

As of OPNsense 24.1.6 this works.

I am using Interface v4 as Check IP Method otherwise my VPN IP was being set.

Thanks for sharing.

Just wondering if the force SSL protects the usr/passw sent when syncing.

Took a while to get it working. You get the data from https://freedns.afraid.org/dynamic/v2/?style=2 (v1 is not usable with ddclient). Also, the "native" backend is crucial, otherwise it will not work.

General settings:
Backend: Native

Service: custom
Protocol: DynDNS 2
Server: sync.afraid.org
Username/Password: Your FreeDNS username/password
Hostname(s): Your FreeDNS FQDN there
Check IP Method: FreeDNS
Interface to monitor: WAN
Force SSL: ticked

5

21.1 Legacy Series / Routing between interfaces and VPN

« on: July 30, 2021, 01:13:00 am »

I am a newbie with OPNsense and would appreciate your comments on this:

This is my setup:

ISP – OPNsense __ eth1 -- VPN -- LAN1 ... PC1, PC3
                           |__ eth2 -- WAN -- LAN2 ... PC2, PC4
                           |__ eth3 ...

OPNsense is permanently connected to VPN for LAN1 traffic.  LAN2 goes thru OPNsense NAT to access the internet with my ISP public IP.

I needed computers from LAN2 to access computers in LAN1 (ssh, smb, nfs, etc) and vice versa

As all LAN1 traffic is sent to VPN, I tried creating a floating rule. Did not work

I think i may need to somehow 'route' only local traffic  between (LAN1) 192.168.10.X and (LAN2) 192.168.20.X  before it reaches the gateway for each interface: VPN or WAN.

Just not sure how. Any ideas are appreciated.