Messages

1

24.1 Legacy Series / Re: Puzzled

« on: March 14, 2024, 04:47:39 pm »

That was part of it. Got it working. Found a hidden rule from an earlier time. Clue was the rulenr. Once I found it in the file and deleted it. All worked again. Strange it didn't show up in the GUI rules

2

24.1 Legacy Series / Puzzled

« on: March 14, 2024, 12:39:51 am »

I can't figure out why one remote IP cannot reach the server. The only clue I have is the absence of a label and different rule number. I have both packets captured in the attachments. The bad pic  cannot get to the server. How do I find the rulenr, as I suspect the rule the bad packet is using is different.

3

23.7 Legacy Series / dropping internet last few days

« on: October 24, 2023, 01:35:43 am »

I have been experiencing intermittent internet loss. not sure if it is the firewall. I did have some errors at the same time this happened today in the OPNsense log. Does this point to anything? I am on the latest OPNsense version.

2023-10-23T16:24:35-07:00   Error   api   no active session, user not found   
2023-10-23T16:18:34-07:00   Error   configd.py   [872b9217-6625-4f0b-9e90-f1e42cc38724] Script action failed with Command '/usr/local/opnsense/scripts/firmware/query.sh remote ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 44, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/firmware/query.sh remote ' returned non-zero exit status 1.   
2023-10-23T16:18:34-07:00   Error   configd.py   Timeout (120) executing : firmware tiers   

Also the general log shows this
2023-10-23T16:24:29-07:00   Error   opnsense   /usr/local/etc/rc.newwanip: The command '/bin/kill -'TERM' '57694''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 57694: No such process'   
2023-10-23T16:24:23-07:00   Error   dhcp6c   transmit failed: Can't assign requested address   
2023-10-23T16:24:23-07:00   Warning   opnsense   /usr/local/etc/rc.bootup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(ixl0)   
2023-10-23T16:22:14-07:00   Error   opnsense   /usr/local/etc/rc.newwanipv6: The command '/bin/kill -'TERM' '76961''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 76961: No such process'   
2023-10-23T16:19:22-07:00   Warning   opnsense   /usr/local/etc/rc.linkup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(ixl0)   
2023-10-23T16:18:53-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:37-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:36-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:35-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:29-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:28-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:28-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:25-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:24-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:24-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:23-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:22-07:00   Error   dhcp6c   transmit failed: Network is down   
2023-10-23T16:18:22-07:00   Error   dhcp6c   transmit failed: Network is down

I am running 2 WAN's in the OPNsense box. Only one WAN died. The ISP said there was no outage.
Problem happens once a day. Problem always points to dhcp6. the WAN that works only uses IPv4. Should I disable IPv6 on the problem LAN? I am using Prefix delegation size of 64. Is that a problem. ISP is Cox

Any help is appreciated.

4

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 17, 2023, 08:57:29 pm »

A Comcast modem is plugged into the WAN port. This is filtered from dmesg. The display was too large to upload so I posted the most recent dsmeg info. See attached
The 4 NIC ports are built-in to the mini-pc
Thank you Franco, I really appreciate your assistance!

5

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 17, 2023, 06:25:17 pm »

The error I mentioned shows up whenever the interface goes down.
I looked at dmesg from the console and it has a ton of these
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
igc0: link state changed to DOWN
igc0: link state changed to UP
There is no timestamp on anything here so I have no idea when these happened
igc0 is the WAN interface

6

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 17, 2023, 04:53:54 pm »

Went down twice last night between Midnight and 3AM. For about one minute each time.
I turned on GW monitoring. Shows RTT-2.2ms RTTd-.3ms and Loss at 0%
This is Comcast cable. We are trying to get them to put in fiber since they have it everywhere around them.
My 4 other locations do not have this issue and Comcast says it is not them, of course.

I put in a new firewall about 3 months ago because of this issue, so that pretty much eliminates the firewall except I am using the same config downloaded from the old one. I do not see anything suspicious in that file.

The firewall log only shows the same thing over and over again and happens during the outages. I want to get rid of this error. so I know if it is the cause of the outages.
2023-08-16T12:12:06-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'

This is my only clue. It shows the pid coming from dhcpdv6 and happens every time during these outages. Franco says this message is benign, but it happens at the same time as the outages. I am not sure if this error is the cause or result of the outages
Any ideas

7

23.7 Legacy Series / Re: Monit email not working

« on: August 16, 2023, 07:51:30 pm »

Resolved by using outlook.com. Still would like to know how to use my local email.

8

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 16, 2023, 07:19:22 pm »

This user has Comcast. IPv6 is disabled.

9

23.1 Legacy Series / Re: DDNS IP/updated columns do not update

« on: August 16, 2023, 06:36:54 pm »

Should have stuck with the old version seeing the lack of support for the new one. Still not fixed in 23.7. Now the old version has been removed.

10

23.7 Legacy Series / Re: OPNsense 23.7.1-amd64 - Dynamic DNS client still broken

« on: August 16, 2023, 06:30:47 pm »

I use Cloudflare and it is working, but the 'Current IP' and 'Updated fields' are still blank. Never got them working.
Not sure why.

11

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 16, 2023, 06:22:33 pm »

No gateway monitoring. This is a very basic firewall setup with only one static IPv4. Goes down 4-8 times a day for 2-4 minutes at a time. The ISP said it isn't them.

12

23.7 Legacy Series / Re: Firewall randomly going down.

« on: August 16, 2023, 05:45:56 pm »

I was looking for reasons the firewall was disconnecting from the internet randomly throughout the day and saw this in the logs which corresponds with the outage times. If these messages are benign then I will look for other causes. The internet closes down for 2-3 minutes every time it happens. I was looking to see what was causing this.
IPv6 is not used in this firewall

13

23.7 Legacy Series / Firewall randomly going down.

« on: August 16, 2023, 12:53:30 am »

This appears in the log when the firewall goes down. This happens 4-8 times a day.
Funny thing is. this system does not use IPv6 at all, so where could this come from? What does this mean?
Firewall uses a static IP on the WAN. No DHCP

2023-08-15T10:34:33-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'

Any help is greatly appreciated.

14

23.7 Legacy Series / Re: Repeating error in my logs

« on: August 15, 2023, 05:15:08 pm »

Yes they were older, but it is still happening, just not as often. How can I track down this error? Also it shows dhpdv6, when this firewall has only one static IP with no IPv6 assigned. Where is this error coming from?

023-08-15T10:34:33-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-15T10:28:05-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-15T10:27:54-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-15T10:26:51-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-14T15:29:30-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-14T15:28:41-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-14T15:28:30-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'   
2023-08-14T15:27:27-04:00   Error   opnsense   /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77804''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 77804: No such process'

15

23.7 Legacy Series / Monit email not working

« on: August 14, 2023, 11:51:20 pm »

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?