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

    Static routes

    Scheduled Pinned Locked Moved Routing and Multi WAN
    32 Posts 3 Posters 8.1k 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
      agarrett5
      last edited by

      For the time being I am going through the NICSs (directl connecting), I do have 2 shiny Netgear switches sitting here, which at the moment I'm not using, but until I've got the VLANs sorted on firewall I was going to wait before using them.  I have 4 NICs currently.  2 Red, 1 with LAN, OPT5, Opt6, 1 with Opt5 and OPt1. Sorry I should have said earlier. Is that likely where my issue is?

      1 Reply Last reply Reply Quote 0
      • P
        podilarius
        last edited by

        So long as there are rules to allow the packets to pass (any protocol, normal is TCP/UDP) and there is an associated rule in the outbound NAT table, it should be able to get tot he internet.

        what are you trying to ping and from where?

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          Pfsense will ALLWAYS TAG the packets on vlan interfaces ….

          if you directly attach your clients, then you will need to force your network driver into the correct VLAN for this to work. (in windows this can be done in device manager when going to advanced settings of the NIC).
          Do note that this works with most Intel network cards .... not sure if all drivers are able to support VLAN's.

          1 Reply Last reply Reply Quote 0
          • A
            agarrett5
            last edited by

            is there anyway to turn off tagging in PfSense?

            1 Reply Last reply Reply Quote 0
            • P
              podilarius
              last edited by

              Yes … don't enable VLAN.

              1 Reply Last reply Reply Quote 0
              • A
                agarrett5
                last edited by

                lol, ok, ill set up my switches then now instead of going direct.  cheers :)

                1 Reply Last reply Reply Quote 0
                • A
                  agarrett5
                  last edited by

                  Ive got a vlan going through the switch, but tagging doesn't appear to be the issue as pfsense is going through a tagged port

                  1 Reply Last reply Reply Quote 0
                  • P
                    podilarius
                    last edited by

                    Yes, you just have to specify which VLAN it has access to and it should work.

                    1 Reply Last reply Reply Quote 0
                    • A
                      agarrett5
                      last edited by

                      I did :-/

                      1 Reply Last reply Reply Quote 0
                      • A
                        agarrett5
                        last edited by

                        I have the vlan tagged, but its not lagged on the switch.  Is that required?

                        1 Reply Last reply Reply Quote 0
                        • P
                          podilarius
                          last edited by

                          The switch needs to know what VLAN it has on what port. Basically, it needs a VLAN access group setup.

                          1 Reply Last reply Reply Quote 0
                          • A
                            agarrett5
                            last edited by

                            I've already done that.  So I'm assuming from that explanation I don't need to set a dedicated lag.  So that then begs the question why is my VLAN access group not doing what it should :-/  I'm sure I'm missing something blatently simple here!

                            1 Reply Last reply Reply Quote 0
                            • A
                              agarrett5
                              last edited by

                              Ive tried it through a LAG, Ive tried it with tagged ports to the pfsense box, ive tried it with untagged ports, Its giving out IPs but its not connecting to the internet (and ive setup NAT as far as I'm aware).  I cant ping pfsense from the computer I have going through the switch. I can however ping the switch

                              1 Reply Last reply Reply Quote 0
                              • P
                                podilarius
                                last edited by

                                Sorry I thought LAG was a typo for TAG. Far as I can remember LAGG is for link aggregation. Port failover or load balancing between 2 ports. That is a different setup than just VLAN and routing. If you are getting an IP from DHCP running on pfSense, but cannot even ping it, then the most likely cause is that you are missing a firewall rule to allow the traffic. In the firewall config, does each of your tabs for VLANS have a default allow rule similar to LAN?

                                1 Reply Last reply Reply Quote 0
                                • A
                                  agarrett5
                                  last edited by

                                  Theres no rule in pfsense on the private interfaces, I thought it allowed everything by default?  so I need to create an allow rule?

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    agarrett5
                                    last edited by

                                    Ive created an allow all rule on the vlan im connectign to currently, its still seems to have the same issue

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      podilarius
                                      last edited by

                                      The default action on all except floating is to deny. Without an allow rule of some kind, traffic will not pass.
                                      Are you at least able to ping the pfSense interface now?

                                      1 Reply Last reply Reply Quote 0
                                      • A
                                        agarrett5
                                        last edited by

                                        no its still timing out.  ive done a ping <ip>  /t so when it starts working ill see it :) </ip>

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          agarrett5
                                          last edited by

                                          Got it working now.  I had it to nonly allow tcp!  im now allowing all :-D  silly slip!  thankyou to everyone that has helped greatly appreciated :-D

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