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

    Adding more hosts to ALIAS used in rule doesn't work. BUG?

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 368 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.
    • E
      elkato
      last edited by

      I'm using FW NAT+rule using an Alias as source IPs on the rule. Working OK. Now I'm trying to add more hosts to the alias, apply all changes but traffic for those new IPs are being denyied, checked on system logs/firewall, and tcpdumping on WAN and LAN ifaces.
      This is UDP traffic.
      Doing tcpdump I see traffic knocking on WAN, but not passing out through LAN iface on FW.

      Using last version on pfsense
      2.4.3-RELEASE-p1 (amd64)
      built on Thu May 10 15:02:52 CDT 2018
      FreeBSD 11.1-RELEASE-p10

      IS this a bug?

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        IS this a bug?

        Probably not. Countless people do the same thing.

        You'll probably have to give a more-specific example including screen shots, contents of the Alias/table (Diagnostics > Tables) before and after the new address addition, the port forward, firewall rule, etc.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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