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

    Adding an "any" rule causes client to randomly lose gateway

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 3 Posters 530 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
      dpsi
      last edited by

      Hi,

      I have 2 networks, LAN and MANAGEMENT, both on different subnets, vlans etc. I need one particular client on LAN to access the resources on MANAGEMENT. When I add a rule to allow access the client will randomly "lose" its default gateway. Windows won't at first catch the problem but eventually it'll give an error. Resetting the eth adapter on the client fixes the problem temporarily. How can I permanently fix this?

      Thanks

      EDIT: It was a NIC issue. I had it plugged into a unTagallbutPvid port on the switch and the crappy display port ethernet NIC would switch between the vlan I selected and vlan 0 (nothing).
      Screenshot_179.png
      Screenshot_179.png_thumb
      Screenshot_180.png
      Screenshot_180.png_thumb

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

        No possible way adding that rule can affect the client like that. Look elsewhere.

        And if your client is on LAN, adding a rule on MANAGEMENT has no bearing on whether the LAN client can access it or not.

        https://doc.pfsense.org/index.php/Firewall_Rule_Basics

        https://doc.pfsense.org/index.php/Firewall_Rule_Processing_Order

        https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting

        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
        • J
          JuantonJohn
          last edited by

          I've seen this when.
          Check to make sure you have allowed traffic to access both interfaces, not just one way.

          | quote: "When I add a rule to allow access the client will randomly "lose" its default gateway"

          Where / what on windows does this?  More info on the setup / error. 
          This client network setup on Windows should not be any different than any other LAN client.

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