"
Please disregard. I didn't realize that firewall logging was disabled by default on the LAN interface. After enabling that, I was able to see the culprit. It was the "Canon MF Network Scanner Selector" on one of my PCs, which scans the network for a Canon scanner. After setting up OPNsense, I used a different LAN IP network than I used to use, and reinstalled the printer driver for it's new IP, but printer scan service started flooding the network looking for a printer that was on a different network.
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.
Pages1
#1
23.1 Legacy Series / Re: Odd traffic behavior - WAN source to private address destination
February 07, 2023, 06:26:47 AM #2
23.1 Legacy Series / Odd traffic behavior - WAN source to private address destination
February 07, 2023, 02:59:35 AM
I just finished setting up OPNsense for the first time, and I noticed some odd behavior in the log file live view. I'm constantly seeing outbound traffic from my WAN IP address to 192.168.1.84 - 192.168.1.116 over port 8610, which doesn't make sense to me. None of my networks start with 192.168, so I don't think I'm getting the traffic direction confused by thinking it's inbound for some reason. This is only happening on the WAN interface, so it doesn't seem like a device on my LAN is causing this.
Am I interrupting this right? Does anyone have any idea on what might be causing this, or might know how I can look into this deeper?
Am I interrupting this right? Does anyone have any idea on what might be causing this, or might know how I can look into this deeper?
Pages1
