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

    [SOLVED] LAN #2 not working

    Scheduled Pinned Locked Moved Routing and Multi WAN
    14 Posts 3 Posters 2.6k 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.
    • K
      kjgas
      last edited by

      Hi,

      I use pfSense 2.3.2 on an Pentium Dual-Core CPU E5300. I'm pretty new to pfSense, but I have it up and running ok.
      My problem is that I can not get my LAN2 to work. WAN and LAN is on my Intel PRO/1000 card, and LAN2 on the build in ethernet port. WAN and LAN on the Intel card is working ok.

      On my LAN2 I get my IP, but no internet and I'm not able to ping pfSense.
      I have enable LAN2 interface, configured DHCP server and added a rule in firewall, see attachments, but no luck.

      Does any have an idea whats wrong?

      Interfaces.JPG
      Interfaces.JPG_thumb
      LAN2.JPG
      LAN2.JPG_thumb
      ![DHCP LAN2.JPG](/public/imported_attachments/1/DHCP LAN2.JPG)
      ![DHCP LAN2.JPG_thumb](/public/imported_attachments/1/DHCP LAN2.JPG_thumb)
      Firewall.JPG
      Firewall.JPG_thumb

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

        Yeah. The source network on your LAN2 rule should be LAN2 net not LAN net

        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
        • K
          kjgas
          last edited by

          Thanks, I'm getting closer.. :)
          Now I'm able to ping pfSense, but I still don't have internet access.

          What am I missing?

          Firewall.JPG
          Firewall.JPG_thumb

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

            Check the outbound NAT settings. Is it set to automatic rule generation? And is there a rule for the LAN2 subnet in place on WAN interface?

            1 Reply Last reply Reply Quote 0
            • K
              kjgas
              last edited by

              Yes it's set to automatic rule generation. I suppose that's the correct setting?

              There is no rules on the WAN interface. Do I need that?

              ![WAN rules.JPG](/public/imported_attachments/1/WAN rules.JPG)
              ![WAN rules.JPG_thumb](/public/imported_attachments/1/WAN rules.JPG_thumb)

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

                I meant the outbound NAT rules. Though it is set to automatic mode, there are shown rule below. Please post these.

                1 Reply Last reply Reply Quote 0
                • K
                  kjgas
                  last edited by

                  These?

                  ![NAT rules.JPG](/public/imported_attachments/1/NAT rules.JPG)
                  ![NAT rules.JPG_thumb](/public/imported_attachments/1/NAT rules.JPG_thumb)

                  1 Reply Last reply Reply Quote 0
                  • K
                    kjgas
                    last edited by

                    In these rules the LAN2 IP adress say the same as my LAN subnet.

                    LAN is 192.168.30.x
                    LAN2 is 192.168.40.x

                    Can that be the problem?

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

                      Yeah, that would be the issue.
                      Maybe pfSense can generate the correct rules automatically. To do so try switch the rule generation to manual and hit save, then delete all rules, save it and switch back to automatic mode.

                      1 Reply Last reply Reply Quote 0
                      • K
                        kjgas
                        last edited by

                        Tried to do that. Deleted everthing in manual, switched back to auto and the same rules where generated. Still the same IP adress..

                        Also tried to set it in manual and changed the IP to 192.168.40.0/24, but then I lost the connection on my LAN subnet. It did't work on LAN2 either.

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

                          That rules are not correct for two LANs and should have a reason.
                          Have you set gateway in LAN2 interface settings?

                          Otherwise you can switch outbound NAT to hybrid mode and add the LAN2 rule manually.
                          But you have also rules for LAN2 interface there which are presumable not wanted. These rules translate packets source address to LAN2 address when packets leave pfSense on this interface.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kjgas
                            last edited by

                            No, I have not set an gateway in LAN2 interface settings. I tried to set it once while faultfinding, but it didn't work.

                            Do I have to make the new rules on LAN or LAN2? There is already automatic rules for LAN2.
                            Should there be rules for LAN shown here as well?

                            LAN2.JPG
                            LAN2.JPG_thumb

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

                              No, if the is no special reason for that, you need neither an outbound NAT rule for LAN interface nor for LAN2.

                              Presumably the gate is still set in pfSense, but not assigned to LAN2. Check and delete it in System > Routing > Gateways.

                              If the LAN2 rules are not gone, switch your outbound NAT to manual rule generation, then delete it.
                              Add a new rule, select WAN interface and at source enter your LAN2 subnet, leave the other settings to its defaults and save it. Now you should have internet access.

                              1 Reply Last reply Reply Quote 0
                              • K
                                kjgas
                                last edited by

                                Finally  :D :D

                                It was the gateway that caused this problem. I deleted it and turned back the automatic outbound rules.

                                Then it worked as it should

                                Thanks a lot viragomann!!

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