OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 19.1 Legacy Series »
  • Insights reporting incorrectly?
« previous next »
  • Print
Pages: [1]

Author Topic: Insights reporting incorrectly?  (Read 2225 times)

FingerlessGloves

  • Full Member
  • ***
  • Posts: 114
  • Karma: 11
    • View Profile
    • FingerlessGloves
Insights reporting incorrectly?
« on: June 16, 2019, 03:11:11 pm »
Hi Guys,

I've been looking through my insights data and I think I've found a bug or something anyway?

So I've got my 192.168.20./24 network which is its own VLAN and interface set to access the internet via a VPN gateway.
Ipleak.net and any other IP service shows VPN's IP not my WAN IP. Which is good and how I want it.

The Firewall rule which allows the network access to the internet has the gateway set as the VPN gateway and has a local tag set "NO_WAN_EGRESS".

In the float rules I have a rule set so if it sees traffic exiting the WAN with the tag "NO_WAN_EGRESS" it drops the data. So if for some reason the VPN drops the traffic can't escape via the WAN interface.

When I look at my insights, I see traffic for 192.168.20.70 coming from my WAN interface. How is this possible?
I have no Port forwarding going to this network at all.

Attached you will see my NAT and an export some example reported traffic.
VPN_Network is alias of 192.168.20.0/24
Our_Network is alias of 192.168.20.0/24,192.168.10.0/24,192.168.2.0/24

Does anyone know why this is happening? looks to be a bug to me?

Jonny
Logged
Adventuring through internet pipes
My Blog

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 19.1 Legacy Series »
  • Insights reporting incorrectly?
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2