Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Use of 'Invert Match' against an interface network with a virtual IP address

    Scheduled Pinned Locked Moved Firewalling
    1 Posts 1 Posters 157 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dmph
      last edited by dmph

      Hi,

      I'm seeing that when using the 'Invert Match' check box when specifying an interface network destination, it does not behave correctly when that interface also has a virtual IP address associated with it.
      So in my firewall rule on my LAN interface I have the following set up for the destination:
      3e1e4249-a9f9-42f1-b3fa-3822428c4c81-image.png

      My WLAN2 network is 10.105.112.1/24

      My firewall log entry showing the issue is:
      0cea0cd2-3d90-476c-8fb3-f5f597f7544e-image.png

      Virtual IP address setting for this network is:
      7bce6126-76c8-46f7-877d-3b97cdfb8112-image.png

      Looking at /tmp/rules.debug I can see that rule entry as:

      pass  in log  quick  on $LAN inet proto tcp  from { 10.105.106.0/24 172.30.106.0/24 } to { !10.105.112.0/24 !172.30.112.0/24 } tracker 1590594136 flags S/SA keep state  label "USER_RULE: LOGGER - packets to non-WLAN2 network"
      

      So I'm guessing that the entries in the curly braces are ORed together so the 'to' section always matches.

      Is this correct?

      If so how would I go about fixing it?

      I'm using 2.4.5-RELEASE (amd64) built on Tue Mar 24 15:25:50 EDT 2020 FreeBSD 11.3-STABLE.

      Kind regards,

      mark

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.