Messages

1

20.7 Production Series / Cron <root@fw> periodic daily/weekly/monthly

« on: August 09, 2020, 09:54:24 am »

Hi, i feel a bit stupid because i cannot find out where these mails are coming from:

From root@fw  Mon Aug  3 03:01:43 2020
Return-Path: <root@fw>
X-Original-To: root
Delivered-To: root@fw
Received: by fw (Postfix, from userid 0)
        id A5FD9D9FB03; Mon,  3 Aug 2020 03:01:43 +0200 (CEST)
From: Cron Daemon <root@fw>
To: root@fw
Subject: Cron <root@fw> periodic daily
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20200803010143.A5FD9D9FB03@fw>
Date: Mon,  3 Aug 2020 03:01:00 +0200 (CEST)
Status: RO

mail: illegal option -- E
Usage: mail [-iInv] [-s subject] [-c cc-addr] [-b bcc-addr] to-addr ...
            [- sendmail-options ...]
       mail [-iInNv] -f [name]
       mail [-iInNv] [-u user]

Sometime i fiddeled around with Cron jobs sending mail. Then it worked but later i found out that this mails aggregate over time for periodic daily/weekly/monthly.

I think i read all documentations and posts about Cron jobs in OpnSense but damn it i cannot change the behaviour. Would anyone like to find the mistake with me? I really appreciate this.

2

20.1 Legacy Series / Cron periodic daily mail: illegal option -- E

« on: June 21, 2020, 07:50:34 am »

Hi, recently we discovered the cron integration with Opnsense and tried all options. We found our solution and our cron jobs works fine. There is one thing which we could not fix which is possibly related to some of our tests.

Every night the cron job for "periodic daily" stops with complains about mail:

From root@fw  Sun Jun 21 03:01:39 2020
Return-Path: <root@fw>
X-Original-To: root
Delivered-To: root@fw
Received: by fw (Postfix, from userid 0)
        id 224C5D9FB03; Sun, 21 Jun 2020 03:01:39 +0200 (CEST)
From: Cron Daemon <root@fw>
To: root@fw
Subject: Cron <root@fw> periodic daily
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20200621010139.224C5D9FB03@fw>
Date: Sun, 21 Jun 2020 03:01:00 +0200 (CEST)
Status: RO

mail: illegal option -- E
Usage: mail [-iInv] [-s subject] [-c cc-addr] [-b bcc-addr] to-addr ...
            [- sendmail-options ...]
       mail [-iInNv] -f [name]
       mail [-iInNv] [-u user]

We cannot find the source for that. Could someone enlighten me?

Tobias

3

20.1 Legacy Series / Re: WAN Port slow

« on: April 18, 2020, 12:06:32 pm »

Solved it finally. I had a routed IP address on the Upstream Gateway to the bridged Fbox. With the new Fbox and 1Gbit bridging is not possible anymore. "Exposed Host" is the alternativ. On the firewall i changed noting, just switched to "Exposed host" in the Fbox.

A second Upstream Gateway in the 192. net solved the problem for me. Fbox is natting and the "old" gateway is still there (not as upstream) handling the routet IP address.

Don not know exactly where the problem was, but it is solved now

Thank you for your ideas.

4

20.1 Legacy Series / Re: WAN Port slow

« on: April 17, 2020, 09:26:30 am »

The new firewall is up and running. Nice 

But there is no change in speed 

Directly connected to Fritzbox speed is optimal. With Opnsense in between not. Just 200-300Mbit and 3-10Mbit upload.

I measure directly on the firewall at the WAN port. Changed the kabel already. Changed each apparently relevant setting in OpnSense. I'm at a bit of a loss.

What else could i optimize?
 

5

20.1 Legacy Series / Re: WAN Port slow

« on: April 15, 2020, 07:48:45 am »

I ordered this one: https://www.ipu-system.de/produkte/ipu675.html. Much to much of almost everything but who knows what comes up. Delivery from China does take a long time nowadays.

6

20.1 Legacy Series / Re: WAN Port slow

« on: April 12, 2020, 09:46:12 pm »

I am not sure which CPU/Setup would fit best für my needs.

What do you think about this one?

https://de.aliexpress.com/item/32920921042.html?gps-id=pcStoreLeaderboard&scm=1007.22922.122102.0&scm_id=1007.22922.122102.0&scm-url=1007.22922.122102.0&pvid=e2793994-0169-4314-98b1-dbbd6ef8189e&spm=a2g0o.store_home.smartLeaderboard_819228523.32920921042

7

20.1 Legacy Series / Re: WAN Port slow

« on: April 12, 2020, 08:27:44 pm »

Thank you, i'll talk to the https://www.apu-board.de/, lets see what they suggest. Thank you!

8

20.1 Legacy Series / Re: WAN Port slow

« on: April 12, 2020, 05:37:24 pm »

Ah, thats a point. Will look for a new hardware - any suggestions for 1Gbit?

9

20.1 Legacy Series / Re: WAN Port slow

« on: April 12, 2020, 05:26:21 pm »

Thanks! Checked them off and on (where disabled). No difference :/

I was thinking that the cpu is to slow. But top shows around 30-40% usage for python process.

10

20.1 Legacy Series / WAN Port slow

« on: April 12, 2020, 05:04:41 pm »

Hi, since we have cable with 1Gbit down/50Mbit up we experience slow net performance. If we connect directly to the cable modem (FritzBox 6591) we have around 800Mbit down/40Mbit up. If we go through our OPNsense Ghz small (SML20083D) we experience only ~100-200MBit/~4-10Mbit.

Our setup is straight forward, no special requirements. OpnSense is connect to the FritzBox via Exposed Host.

Very could we start to narrow down the problem?

11

18.1 Legacy Series / Re: Uncaught Error: Call to undefined function encrypt_data()

« on: May 26, 2018, 03:45:01 pm »

Manual backup from System/Configuration/Backup works fine.

12

18.1 Legacy Series / Uncaught Error: Call to undefined function encrypt_data()

« on: May 26, 2018, 03:42:01 pm »

Since update to 18.1.8-ef579d069 these error message appears in the GUI:

Code: [Select]

Unfortunately we have detected at least one programming bug.

User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
FreeBSD 11.1-RELEASE-p10  a6fa9599a(stable/18.1)
OPNsense 18.1.8-ef579d069 [18.1.6-1ba9a4da3] OpenSSL 1.0.2o  27 Mar 2018 (amd64)
Plugins os-clamav-1.5 os-postfix-1.2
Time Sat, 26 May 2018 15:35:28 +0200

[21-May-2018 01:00:00 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to undefined function encrypt_data() in /usr/local/etc/inc/config.inc:318
Stack trace:
#0 /usr/local/opnsense/scripts/remote_backup.php(8): backup_to_google_drive()
#1 {main}
  thrown in /usr/local/etc/inc/config.inc on line 318
[22-May-2018 01:00:00 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to undefined function encrypt_data() in /usr/local/etc/inc/config.inc:318
Stack trace:
#0 /usr/local/opnsense/scripts/remote_backup.php(8): backup_to_google_drive()
#1 {main}
  thrown in /usr/local/etc/inc/config.inc on line 318
[23-May-2018 01:00:00 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to undefined function encrypt_data() in /usr/local/etc/inc/config.inc:318
Stack trace:
#0 /usr/local/opnsense/scripts/remote_backup.php(8): backup_to_google_drive()
#1 {main}
  thrown in /usr/local/etc/inc/config.inc on line 318
[24-May-2018 01:00:00 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to undefined function encrypt_data() in /usr/local/etc/inc/config.inc:318
Stack trace:
#0 /usr/local/opnsense/scripts/remote_backup.php(8): backup_to_google_drive()
#1 {main}
[...]
a.s.o.

The backup to Google Drive is not working anymore. Has something changed?

13

17.7 Legacy Series / Re: Update to 17.7.1 not offered

« on: September 02, 2017, 04:02:16 pm »

Yes that was it. (LeaseWeb Frankfurt DE). Switched to default and now the update is there. Knew it was easy and I missed something. Thank you!

14

17.7 Legacy Series / Solved: Update to 17.7.1 not offered

« on: September 02, 2017, 11:48:30 am »

Since upgrade to 17.7. the GUI speeded up tremendously! Perfect, good work, thank you

Today i saw that there is 17.7.1 available. But it is not offered to be installed. Not from the GUI as well as not from cli.

It shows up like that:

17.7.1 2017-08-31   
17.7 (installed) 2017-07-31

Obviously i miss something. But what?

15

German - Deutsch / Re: Ports in Firewall-Konfiguration bleiben ausgegraut

« on: June 11, 2016, 04:32:13 pm »

Changelog lesen hilft

doc/15.7.23
32   o firewall: lock port numbers on protocols that are not TCP/UDP

Das war das? Oder?

Danke!