Messages

Running 23.7.1_3
I tried every email address I have, local and remote, and all I get is this

023-08-15T10:36:15-07:00   Error   monit   Aborting event   
2023-08-15T10:36:15-07:00   Error   monit   Mail: Delivery failed -- no mail server is available   
2023-08-15T10:36:15-07:00   Error   monit   Cannot open a connection to the mailserver 192.168.100.5:465
2023-08-15T10:36:15-07:00   Error   monit   Cannot connect to [192.168.100.5]:465 -- Connection timed out   

I cannot find any email service to work with Monit. Tried Gmail, Yahoo, Local emails. Nothing works.
Apparently you can no longer use Gmail or Yahoo due to new security on those sites, so I am stuck with using the local account. Not sure if I need a firewall rule to do this.

Monit itself works fine. Just won't send email messages from my main site.
I gave up and just disabled Monit. Not really useful if I can't get messages.

Any ideas on how to get it to work on the same machine as the email servers. Do I need a new firewall rule?

My logs are filled with errors. Using v23.7.1_3
This is a repeating error every second in the logs there are actually thousands of these. Using DHCP on the WAN
How can I fix this?

2023-08-08T08:46:36-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804'' returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-08T08:45:53-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804'' returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-08T08:45:42-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804'' returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-08T08:44:37-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804'' returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-08T08:44:31-04:00   Error   opnsense   /usr/local/etc/rc.routing_configure: ROUTING: refusing to set inet gateway on addressless wan(igc0)   

Quick question.
Should I use "Bind states to interface" if I have two isolated WAN's. One static and one dynamic.
I am not using failover or load balancing.

I am also seeing this. Can it be ignored, or do I have a configuration issue?

I have a working IPsec VPN. I want to use my alternate WAN Interface to connect to it. If I change the IP in my DNS Record I get a policy Error when trying to connect. The certificate uses my OPNsense Hostname and not an IP. I did make sure the Firewall rules were duplicated for the second WAN, LAN, and NAT.

I have created another VPN connection using the new local IP's and it works fine, but changing the DNS record to the secondary WAN does not work.

Any ideas?

I have VPN working fine, but I want to change the Local IP as shown in the VPN Status Overview page.
Where can I do that? Or more specifically, how does OPNsense determine the Local IP for VPN IPsec?

When I try to connect via my other WAN Interface, I get a Policy Error.

No one?

Not asking for how to set it up. Just want to know if Multi-WAN is a viable option with my configuration.

I could not find a scenario chart of when Multi-WAN is useful. My goal is to get as much redundancy as possible.
My question is basically if I should use Multi-WAN. Would it benefit me with the following setup?
First of I want to state that I did try to set up a failover Multi-Wan configuration following the online documentation to the letter. It was not successful as I had many stalled internet accesses. I removed it.

This OPNsense box has 2 WAN's. The business Internet has a 100/20MB Mbps static IP (WAN1), and the other a 1000/50MB Mbps dhcp residential connection (WAN2).
WAN1 is used for incoming SMTP and business websites.
WAN2 is for residential internet, IMAP and SMTP outgoing, IPsec VPN to a local server, FTP, RSYNC, and video streaming server because of it's faster connection. WAN 2 also uses Dynamic DNS

I basically just use WAN1 for ports not allowed by my ISP residential service.

Now the big question. Is Multi-WAN an option for this scenario? Seems to me I have set IP's to do most connections, so I assume failover can't handle that.

I am also having LTE failover installed in a few day on WAN1. That is external to OPNsense.

Your thoughts?

This issue has been resolved with the update to 23.1.11.
The old box was at 23.1.6 and worked. The new box was at 23.1.9 and had the slowdown issue. After update to 23.1.11 problem went away. So it was an OPNsense issue all along.

Still living with this issue. I execute a state table reset every morning at 8AM and it seems to get the users through the day, but this can't be right. Why would resetting the state table make this difference? This morning there were only 650 entries in there. What else does resetting the state table do? Maybe this is a clue.

pmhausen, you were right.
Just got back the old firewall and the disk has write issues. I reinstalled OPNsense with the latest version and it is working fine. I replaced the SSD and tested the old one. It has no read errors but cannot write.

I think that work, although the backend log shows it as an error as below.

2023-06-23T11:23:00-07:00   Informational   configd.py   message a61b4e69-fe65-43ed-9fdc-afb05ae76ab3 [] returned   
2023-06-23T11:23:00-07:00   Error   configd.py   [a61b4e69-fe65-43ed-9fdc-afb05ae76ab3] Script action stderr returned "b'280 states cleared'"   
2023-06-23T11:23:00-07:00   Notice   configd.py   [a61b4e69-fe65-43ed-9fdc-afb05ae76ab3] starting reset_state_table

I took your advice and using 'command:/sbin/pfctl -F states'.
No more error. The backend log shows reset started, but no log entry for what it did. Do I need to change something like script to script-output so I can see what the command did?

I have been unsuccessful trying to reset the state table using cron. All I get is 'returned exit status 127'
can anyone help with my code? Here is what I did

/usr/local/opnsense/service/conf/actions.d/actions_ResetST.conf

Code Select Expand


[start]
command:/usr/local/etc/rc.d/rstate.sh
parameters:%s
type:script
message:starting reset_state_table
description:Reset State Table


usr/local/etc/rc.d/rstate.sh

Code Select Expand


#!/bin/sh
pfctl -F states


Then ran 'service configd restart' in shell and setup the time in cron.

What am I doing wrong?
Thanks

Nothing I tried helped. The only thing I could do is setup a cron job to exectue pfctl -F state every 4 hours.
See attached pics for the state info while the issue was at its worse. Does anything look off here?