Messages

Help, I cannot get SMB access with a remote user.
I setup a dedicated opnsense firewall using one of my static WAN IP's as the WAN to allow access to/from a single remote user.
OPNsense has the LAN set to 192.168.40.1/24 and the WAN as 99.99.99.99 (using this IP as WAN example)
The IP of the local user is 192.168.40.26 which is what I want the remote user access to.
Let say the IP of the remote user is 50.50.50.50 for now which may change to dynamic later on, so I can just use an Alias when that happens.

All I need is for only the one remote user (50.50.50.50) full access to the local user (192.168.40.26) on all ports. No other access allowed.
I can ping 99.99.99.99 from 50.50.50.50, so I know there is a connection with an ICMP allow rule I put in the WAN rules.
I tried just one WAN rule making the source 50.50.50.50 to any. Didn't work
I tried just one LAN rule making the source any to destination any. Didn't work
I tried both together.

For more info, this local computer has a dedicated NIC with it's IP as 192.168.40.26. This plugs into the OPNsense box. The only other NIC in the OPNsense box is the one for the connection to the WAN IP 99.99.99.99.
There are no active Windows or any other firewalls running on the local or remote computers.

This should be simple, only one remote user to access only one local IP. The main reason I am using OPNsense instead of Windows firewall is because I need to ultimately use an Alias with the remote domain name info.

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

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.

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.

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!

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

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

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

This user has Comcast. IPv6 is disabled.

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.

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

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.

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

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.

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'