OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of fred.bloggs »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Topics - fred.bloggs

Pages: [1]
1
23.7 Legacy Series / [solved] IPv6 firewall log - Source and Destination are inverted
« on: December 16, 2023, 07:45:58 pm »
Hi,

we are currently adding IPv6 to our setup. The basics work well so far. The OPNsense gets its IPv6 /56 net, RA is working and all the clients and servers succesfully get their IPv6 "global" and "unique local" addresses from /64 subnets and can surf the internet (IPv6 and IPv4) without any problems. The clients and servers also can get pingend by their global IPv6s from the internet, so far so good.

Problems start when trying to open inbound ports from the internet for our servers in the DMZ. We added a firewall rule to the DMZ:

--
Action: pass
Interface: DMZ
Direction: in
IP Version: IPv6
Protocol: TCP
Source: any
Destination: <global IPv6 address of web server in DMZ>
Destination port range: 80
--

The connection to port 80 from the internet does not work and the live view of the firewall log shows this:

--
State: Block
Interface: DMZ
Direction: in
Source: <global IPv6 address of web server in DMZ>:80
Destination: <global IPv6 address of internet client trying to connect>:17619
Label: Default deny / state violation rule
--

It seems that the "source" and "destination" are inverted?! I do not understand why and what to do here to get inbound connections working. I hope that someone can give me a hint regarding this issue.

Version: 23.7.10_1
Architecture: amd64

2
General Discussion / [Feature Request] Use certificate both for smtpd and smpt connections in postfix
« on: August 11, 2022, 06:34:45 pm »
Hi,

some smart host providers allow authentication via certificate instead of IP or user/password. E.g. O365 outlook connector supports this.

To make this work the following settings in postfix conf need to be set for outgoing connections:
postconf -e "smtp_tls_cert_file = <cert file>"
postconf -e "smtp_tls_key_file = <cert key>"

As I can see, currently the certificate selected in the GUI only applies to inbound connections:
postconf -e "smtpd_tls_cert_file = <cert file>"
postconf -e "smtpd_tls_key_file = <cert key>"

Am I missing something or may there be a chance to add this support?
Thank you.
Fred

3
22.7 Legacy Series / [SOLVED ]Bug in nginx plugin version 1.28_2 on OPNsense 22.7_4
« on: August 07, 2022, 12:17:30 am »
Hi, I think there is a bug with the nginx plugin version 1.28_2 on OPNsense 22.7_4. (updated from 22.1.10_4).

I have "Basic Authentication" enabled on a "location" and assigned  a "Basic Credentials List". When accessing the URL the basic auth form pops up and credentials can be entered. But even when entering correct credentioals, the popup reappears.

In this moment a system firmware error is thrown:
---
PHP Fatal error:  Uncaught ArgumentCountError: crypt() expects exactly 2 arguments, 1 given in /usr/local/opnsense/scripts/nginx/setup.php:231
Stack trace:
#0 /usr/local/opnsense/scripts/nginx/setup.php(231): crypt('<here goes the password>')
#1 {main}
  thrown in /usr/local/opnsense/scripts/nginx/setup.php on line 231
 ---

At the same time also nginx reports an error:
---
*18413 user "<here goes the user name>" was not found in "/var/db/nginx/auth/d0c4603...
---

Maybe someone can look into this. Thanks.



Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2