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

    Can't reach printer from 1 network out of 3

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 2 Posters 647 Views 2 Watching
    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.
    • C Offline
      cITs 0
      last edited by

      Hi,

      I can't seem to find what I might have done wrong so i decided to register and ask here.

      I currently have 3 networks (2 on wifi, 1 on lan) and configured a printer on a wifi network with a static IP, but I can not reach it from within its own network. I can reach the printer over the other 2 networks without any issues. I went as far as deleting all my rules for that particular network and simply having one rule from that network to any but i still can't even ping the printer. For a brief moment i thought pfblocker might interfere but that wasn't it. I also had a look at pfTop but i couldn't even find any state that was being logged when pinging.

      I am pretty confused because my wifi rules were originally configured to look exactly the same (before i trashed the one having issues), but the behavior is or at least appears to me to be completely different. Any ideas what I might be missing or should be looking for?

      If it's any help I'm running Pfsense 2.5 on an APU2D4 with a Compex WLE200NX

      If you need more infos or screens let me know.

      Thanks in advance

      V 1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann @cITs 0
        last edited by

        @cits-0
        Traffic within a network segment does not pass pfSense. So it cannot be blocked by pfSense.

        However, access between wifi devices may be blocked on your access point. You have to allow access between connected stations on the AP.

        C 1 Reply Last reply Reply Quote 0
        • C Offline
          cITs 0 @viragomann
          last edited by cITs 0

          @viragomann
          That's the thing. I can connect to other devices from that network and to this network, from other networks, both wired and wireless configured on the pfsense. My AP is the pfsense itself, i don't have any other hardware managing wifi. I mention in my initial post that even an any-any network rule ("wifi with printer to wifi with printer" or "wifi with printer to everywhere else") doesn't enable communication to this device just in this "wifi with printer network", while all other networks have no issue.

          I don't even know how to debug this further because literally everything works, just not this one thing.
          ping from the pfsense works
          ping from admin lan works
          ping from admin wifi works
          ping from guest wifi works (just as a test)
          ping from office lan does not work

          I disabled static dhcp mapping, i disabled the static IP on the printer itself, i resetted the printer (just to make sure that i didn't forget anything), i ran a packet capture to see that only for this device the request is resolved from any other configured network but not the one it is in, i have only one rule "from wifi with printer to "anywhere" that worked with every other basic wifi or lan configuration but does not with this one.

          I don't understand why it behaves like this.

          V 1 Reply Last reply Reply Quote 0
          • V Offline
            viragomann @cITs 0
            last edited by

            @cits-0 said in Can't reach printer from 1 network out of 3:

            My AP is the pfsense itself, i don't have any other hardware managing wifi.

            So go to the wifi settings and check "Allow intra-BSS communication".

            C 1 Reply Last reply Reply Quote 0
            • C Offline
              cITs 0 @viragomann
              last edited by

              @viragomann
              Alright, that did it. I'll have to read up on that because i never heard of it before.
              Thanks for your help, i really appreciate it

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