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

    Setting up a VLAN part 2

    Scheduled Pinned Locked Moved General pfSense Questions
    110 Posts 3 Posters 40.9k 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.
    • ?
      A Former User
      last edited by

      @Metu69salemi:

      That's true until you hit unmanaged switch, then you can use only one vlan on that port of managed switch and that should be untagged

      right, if i want to do multiple vlans on other switches they need to be vlan switches.  i follow what you are saying.

      right now one of the untagged ports for vlan1 is plugged into a 16 port netgear switch, that switch can only operate on 1 subnet since it isnt vlan capable, in this case 192.168.1.x.

      1 Reply Last reply Reply Quote 0
      • ?
        A Former User
        last edited by

        finished adding some block rules to stop traffic between vlans. disabled it one way to test, enabled it again, did some more testing, the rules did exactly what they were suppose to do.

        dns question- i can ping other IPs, but i cant browse by going to \pc-name

        any idea what i need to do to get that working?

        i can access \ip-address w/o any issues, which is why i assume DNS.

        the dhcp server settings for LAN is what i used as a template for vlan100 and 200 and my LAN DNS lookups work fine.

        1 Reply Last reply Reply Quote 0
        • M
          Metu69salemi
          last edited by

          where you do have dns setup?

          @tomdlgns:

          right now one of the untagged ports for vlan1 is plugged into a 16 port netgear switch, that switch can only operate on 1 subnet since it isnt vlan capable, in this case 192.168.1.x.

          You can also use another vlan if you require

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            I assume you are using DNS forwarding on pfSense for your DNS service. That's the default.
            You can have pfSense add any client that sends it's host name to the local DNS table.
            Go to Services: DNS Forwarder: and check 'Register DHCP leases in DNS forwarder'.

            This will only kick in when clients renew their DHCP lease so you may have to force that to test.

            Steve

            1 Reply Last reply Reply Quote 0
            • ?
              A Former User
              last edited by

              @Metu69salemi:

              where you do have dns setup?

              it is the default setup.  the only thing i did was point to OpenDNS servers for lookups (and removed the first entry of 127.0.0.1).

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                @stephenw10:

                I assume you are using DNS forwarding on pfSense for your DNS service. That's the default.
                You can have pfSense add any client that sends it's host name to the local DNS table.
                Go to Services: DNS Forwarder: and check 'Register DHCP leases in DNS forwarder'.

                This will only kick in when clients renew their DHCP lease so you may have to force that to test.

                Steve

                ok, just did this, i will delete DHCP leases and remote reboot machines and see if that fixes it.

                EDIT- now that i think of it…the device i was trying to access by hostname was statically assigned, this option looks like it is only DHCP related.  that device will never ask for a new address since it is static.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  You can add static dhcp IPs with an option on that same page. Or if you have statically assigned the IP on the client itself you can add it manually in the host overrides table at the bottom.

                  If I need to have anything static I always use static DHCP rather then IPs coded at the client. It makes this sort of thing far easier. Also if I do have to change the IP ever it's all centrally stored.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User
                    last edited by

                    @stephenw10:

                    You can add static dhcp IPs with an option on that same page. Or if you have statically assigned the IP on the client itself you can add it manually in the host overrides table at the bottom.

                    If I need to have anything static I always use static DHCP rather then IPs coded at the client. It makes this sort of thing far easier. Also if I do have to change the IP ever it's all centrally stored.

                    Steve

                    makes sense and i am going to look into that, thank you.

                    ok, i did that, i added the entry for the static device.

                    when i ping it, it resolves to a public internet address not the internal IP…..hmmmm

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      You may have to clear the local dns cache. Make sure your client is using the DNS forwarder.
                      You can try using the Diagnostics: DNS Lookup: tool to check pfSense can resolve it correctly.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • ?
                        A Former User
                        last edited by

                        @stephenw10:

                        You may have to clear the local dns cache. Make sure your client is using the DNS forwarder.
                        You can try using the Diagnostics: DNS Lookup: tool to check pfSense can resolve it correctly.

                        Steve

                        DNS lookup in pfsense can see the correct name if i type in the ip and it shows the correct ip if i type in the name.

                        but it uses 127.0.0.1, then 208.67.222.222, 208.67.220.220, finally 192.168.1.1

                        i do want my machines to use openDNS server for external lookups, but obviously not for internal lookups, which is what i think it happening, but i could be wrong.

                        local cache cleared and my ipconfig looks like this

                        ip- 172.10.10.210
                        sub- /24
                        gate- 172.10.10.1

                        dns- 172.10.10.1

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          127.0.0.1 is the local machine, which it is checking first. That seems correct. I don't know why it's looking at 192.168.1.1 though, that sounds wrong.
                          See my screenshots.

                          Steve

                          dnslookup.jpg
                          dnslookup.jpg_thumb
                          pinglocaldns.jpg
                          pinglocaldns.jpg_thumb

                          1 Reply Last reply Reply Quote 0
                          • ?
                            A Former User
                            last edited by

                            i know 127 is localhost, but i removed that from the DNS page.

                            my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.

                            although, 192.168.1.1 might be wrong and i probably shouldn't keep it in there now that i no longer have a flat network.

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              @tomdlgns:

                              my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.

                              You mean in System: General Setup: DNS Servers: ?

                              That should only list external DNS servers that pfSense uses for DNS resolution.

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User
                                last edited by

                                @stephenw10:

                                @tomdlgns:

                                my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.

                                You mean in System: General Setup: DNS Servers: ?

                                That should only list external DNS servers that pfSense uses for DNS resolution.

                                Steve

                                ok, no problem, i will remove the 192 entry, if i do that, then only the openDNS servers remain, but those are in spot 1,2 right now so i dont think it will fix my issue, but i will still remove it.

                                thanks.

                                1 Reply Last reply Reply Quote 0
                                • stephenw10S
                                  stephenw10 Netgate Administrator
                                  last edited by

                                  Ok. Well yes it has to first use the local DNS table so 127.0.0.1 should show first as in my screenshot.
                                  Where exactly did you remove 127.0.0.1 from?

                                  pfSense will always use the local DNS table first unless you have checked 'Do not use the DNS Forwarder as a DNS server for the firewall' in System: General Setup: DNS Servers:

                                  Steve

                                  1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User
                                    last edited by

                                    @stephenw10:

                                    Ok. Well yes it has to first use the local DNS table so 127.0.0.1 should show first as in my screenshot.
                                    Where exactly did you remove 127.0.0.1 from?

                                    pfSense will always use the local DNS table first unless you have checked 'Do not use the DNS Forwarder as a DNS server for the firewall' in System: General Setup: DNS Servers:

                                    Steve

                                    i didnt remove it, i thought i saw an option to uncheck the use of it.

                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      Hmm, that looks fine. Exactly as I have mine set.

                                      Yet when you use Diagnostics: DNS Lookup: it doesn't use 127.0.0.1?

                                      Steve

                                      1 Reply Last reply Reply Quote 0
                                      • ?
                                        A Former User
                                        last edited by

                                        ok, i just added 127.0.0.1 as the first entry and bumped down the openDNS servers.

                                        1 Reply Last reply Reply Quote 0
                                        • ?
                                          A Former User
                                          last edited by

                                          @stephenw10:

                                          Hmm, that looks fine. Exactly as I have mine set.

                                          Yet when you use Diagnostics: DNS Lookup: it doesn't use 127.0.0.1?

                                          Steve

                                          yeah, i think i am going to take it out, if yours doesnt have 127.0.0.1 listed as the first one.

                                          1 Reply Last reply Reply Quote 0
                                          • ?
                                            A Former User
                                            last edited by

                                            this is what my settings are as of this post:

                                            C:>ping ds2411

                                            Pinging ds2411.home [192.168.1.254] with 32 bytes of data:
                                            Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
                                            Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
                                            Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
                                            Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

                                            Ping statistics for 192.168.1.254:
                                                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                                            Approximate round trip times in milli-seconds:
                                                Minimum = 0ms, Maximum = 0ms, Average = 0ms

                                            C:>

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