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

Printer on Separate VLAN Issue

Scheduled Pinned Locked Moved Routing and Multi WAN
26 Posts 4 Posters 1.5k 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.
  • G
    Gertjan @stevencavanagh
    last edited by May 27, 2024, 4:54 PM

    @stevencavanagh said in Printer on Separate VLAN Issue:

    The pfblocker logs appear to be all empty!

    What log ?

    Goto this page :

    03e2b6f3-92da-4290-8000-db5463541f7f-image.png

    and hit Ctrl-F, type in the IP LAN of the printer, and see what pops up.

    Also check the "Unified" log, look under "SRC".

    @Popolou said in Printer on Separate VLAN Issue:

    squid, squidGuard,

    Now all bets are off .... you just opened up a whole swimming pool full of potential issues 😊

    No "help me" PM's please. Use the forum, the community will thank you.
    Edit : and where are the logs ??

    S 1 Reply Last reply May 27, 2024, 5:39 PM Reply Quote 0
    • S
      stevencavanagh @Gertjan
      last edited by May 27, 2024, 5:39 PM

      @Gertjan

      Checked logs as described and nothing at all with the printer ip address

      T 1 Reply Last reply May 27, 2024, 5:43 PM Reply Quote 0
      • T
        the other @stevencavanagh
        last edited by May 27, 2024, 5:43 PM

        @stevencavanagh
        well, tried to disable snort and co for a test to be sure THAT is not interfering?
        Are (after that change from Vlan IoT to Vlan Printer) the printer's DNS settings okay? In case DNS info is not sent by dhcp...

        the other

        pure amateur home user, no business or professional background
        please excuse poor english skills and typpoz :)

        S 1 Reply Last reply May 27, 2024, 5:49 PM Reply Quote 0
        • S
          stevencavanagh @the other
          last edited by May 27, 2024, 5:49 PM

          @the-other

          DNS settings seem fine.........

          9ee49ff3-7eda-490c-b0fe-6347c398c389-image.png

          P 1 Reply Last reply May 27, 2024, 5:55 PM Reply Quote 0
          • P
            Popolou @stevencavanagh
            last edited by May 27, 2024, 5:55 PM

            @stevencavanagh If the printer is set to DHCP but it is getting those DNS, you got other more fundamental problems to investigate tbh.

            S 1 Reply Last reply May 29, 2024, 11:18 PM Reply Quote 0
            • S
              stevencavanagh @Popolou
              last edited by May 29, 2024, 11:18 PM

              @Popolou

              Such as?

              G 1 Reply Last reply May 30, 2024, 5:47 AM Reply Quote 0
              • G
                Gertjan @stevencavanagh
                last edited by May 30, 2024, 5:47 AM

                @stevencavanagh said in Printer on Separate VLAN Issue:

                DNS settings seem fine.........

                No, your handing over all DNS request to "who ever" and not to pfSense (by default 192.168.1.1 - no second DNS needed). All DNS traffic from the printer totally bypasses pfSense.

                If you have to give 8.8.8.8 or 1.1.1.1 your DNS requests by contract (they pay you for that info ?) then ok, you do you.
                Normally, DNS should be set up per DHCP info received, so DNS is 192.168.1.1 (pfSense LAN IP by default, or whatever you've set up)

                You can leave all DNS fields empty (and not 0.0.0.0 !)

                Test also with "Enable Auto IP" not checked.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                S 1 Reply Last reply May 30, 2024, 1:10 PM Reply Quote 0
                • S
                  stevencavanagh @Gertjan
                  last edited by May 30, 2024, 1:10 PM

                  @Gertjan

                  So had a quick look at how the DHCP server is currently set up and changed it so it uses DNS resolver and the DHCP server now shows the server options as blank (DNS Server 1 now has the gateway in automatically ie. 192.168.0.1) for the LAN. I assume this is now correct?

                  G 1 Reply Last reply May 30, 2024, 1:15 PM Reply Quote 0
                  • G
                    Gertjan @stevencavanagh
                    last edited by May 30, 2024, 1:15 PM

                    @stevencavanagh

                    If 192.168.0.1 is your pfSense LAN IP, then, IMHO, 👍

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

                    S 2 Replies Last reply May 30, 2024, 1:19 PM Reply Quote 0
                    • S
                      stevencavanagh @Gertjan
                      last edited by May 30, 2024, 1:19 PM

                      @Gertjan

                      Yes it is, so will update the VLANs accordingly and then try the other things you suggested ie. Not auto ip etc and see what happens.

                      1 Reply Last reply Reply Quote 0
                      • S
                        stevencavanagh @Gertjan
                        last edited by May 30, 2024, 7:22 PM

                        @Gertjan

                        Didn't seem to make any difference unticking "enable Auto IP" unfortunately.

                        1 Reply Last reply Reply Quote 0
                        • S
                          stevencavanagh
                          last edited by Jun 7, 2024, 1:01 AM

                          Just in case anyone else ends up in the same place as me..............

                          I managed to solve the issue and found there was no access to the internet on the PRINTERS VLAN, despite having the firewall rules allowing it!

                          Eventually I stumbled upon the Firewall NAT Outbound rules, which was populated with 2 rules per VLAN (had been done automatically, presumably when setting up the VLANs).

                          These rules did not exist for the PRINTERS VLAN. Added these rules manually and all sprung into life!

                          43fb5a5f-11d8-437e-b9a7-dabcee21984d-image.png

                          What I cannot understand is why these had not been created in the first place!! The outbound NAT mode was showing 'manual outbound NAT rule generation'.

                          492154ac-6783-4375-9f47-bc2b5809d6c9-image.png

                          Thought this would have been set to Auto??

                          Never mind, all working now but at least I've picked up some extra knowledge. Thanks to everyone for helping me sort this out, it is greatly appreciated.

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                            This community forum collects and processes your personal information.
                            consent.not_received