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

How to config the LAN interface users to Internet (Basic configuration)

Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
22 Posts 5 Posters 1.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.
  • G
    Gertjan
    last edited by Feb 20, 2019, 6:10 PM

    The only thing that needs to be setup is, is the WAN connexion.
    No need to change anything elsewhere : pfSense will work.

    A notable exception is when the upstream router - if one exists - also uses the 192.168.1.0/24 as is LAN.
    In that case you change that LAN - or you change the LAN settings on the pfSense LAN interface.

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

    C 1 Reply Last reply Feb 21, 2019, 2:33 AM Reply Quote 0
    • C
      coachever @Gertjan
      last edited by Feb 21, 2019, 2:33 AM

      @gertjan I have not changed DNS servers, Gateways on services=>DHCP server (i mean its blank). So the DNS and Default gateway is 192.168.1.1 LAN interface is 192.168.1.0/24

      0_1550716042692_ipconfig.png

      And therefore, when i using ping from client machine to yahoo.com it did not respond, but when i ping to IP address of yahoo, it replied.

      0_1550716064548_ping.png

      Also from LAN and WAN both interfaces on pfSense webGUI to yahoo.com pinging is replied. So the problem is in DNS configuration on LAN interface I guess, when I add 8.8.8.8 to services=>DHCP server=>DNS servers client machine can connect to internet. What should i do?

      1 Reply Last reply Reply Quote 0
      • G
        Gertjan
        last edited by Feb 21, 2019, 9:36 AM

        So, when you run this :

        [2.4.4-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: ping yahoo.com
        PING yahoo.com (98.138.219.232): 56 data bytes
        64 bytes from 98.138.219.232: icmp_seq=0 ttl=48 time=146.540 ms
        64 bytes from 98.138.219.232: icmp_seq=1 ttl=48 time=145.787 ms
        

        you have replies - and more important : yahoo.com resolves => the DNS works.
        But not from a device on LAN.

        This means these devices can't contact the DNS Resolver running on pfSense.
        What are your LAN firewall rules ?

        0_1550741781874_fd9b7a95-8266-457f-9866-8714ffa8abef-image.png

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

        1 Reply Last reply Reply Quote 0
        • C
          coachever
          last edited by Feb 21, 2019, 11:10 AM

          Floating rule is

          0_1550747359281_Floating.png

          WAN rule is

          0_1550747407673_WAN.png

          LAN rule is

          0_1550747420167_LAN.png

          1 Reply Last reply Reply Quote 0
          • I
            isolatedvirus
            last edited by Feb 21, 2019, 11:49 AM

            ok do a couple things and post the output:
            -ping 105.57.94.2
            -perform an nslookup for www.duckduckgo.com against that server as well with:

            nslookup
            server 105.57.94.2
            www.duckduckgo.com
            

            Post your DNS config. If you haven't modified anything, this will be the DNS Resolver.
            Also, please confirm if this firewall is running on physical, or virtual, and if its virtual confirm which virtualization tech youre using.

            1 Reply Last reply Reply Quote 0
            • C
              coachever
              last edited by Feb 21, 2019, 12:21 PM

              @isolatedvirus
              Okey, the firewall is running on VIrtualBox
              Pfsense WAN is in VirtualBox NAT mode 10.0.2.15
              LAN is in an internal mode 192.168.1.1

              So ping from client machine to 105.57.94.2 is

              0_1550751532640_ping to 105.57.94.2 from client.png

              Ping from Pfsense wan side to 105.57.94.2 is

              0_1550751570009_ping to 105.57.94.2.png

              Nslookup from client machine to 105.57.94.2 and www.duckduckgo.com is

              0_1550751665075_Nslookup.png

              No changes to DNS settings and the DNS resolver config is

              0_1550751600324_DNS Resolver1.png

              0_1550751606760_DNS Resolver2.png

              1 Reply Last reply Reply Quote 0
              • I
                isolatedvirus
                last edited by Feb 21, 2019, 12:29 PM

                ok whatever that IP is, it isnt working. Remove it from your config (Could be under the WAN configuration via allow DHCP override of DNS or something to that affect)

                Looks like pfsense is hitting 8.8.8.8 and getting results, but when it trys that IP it gets no responses.

                C 1 Reply Last reply Feb 21, 2019, 12:40 PM Reply Quote 0
                • C
                  coachever @isolatedvirus
                  last edited by Feb 21, 2019, 12:40 PM

                  @isolatedvirus
                  You mean this? I have uncheck the System=>General Setup=>Allow DNS server list to be overrided by DHCP/PPP on WAN and added 8.8.8.8 and 8.8.4.4 DNS servers.

                  0_1550752667313_PfSense1.png

                  This is the tutorial that i have followed, is it possible to using this setup to connect to Internet?

                  Thank you for your time @isolatedvirus

                  C 1 Reply Last reply Feb 21, 2019, 12:44 PM Reply Quote 0
                  • C
                    coachever @coachever
                    last edited by Feb 21, 2019, 12:44 PM

                    https://www.tecmint.com/installation-and-configuration-of-pfsense-firewall-router/
                    This is the tutorial link,

                    G 1 Reply Last reply Feb 21, 2019, 3:16 PM Reply Quote 0
                    • I
                      isolatedvirus
                      last edited by isolatedvirus Feb 21, 2019, 12:49 PM Feb 21, 2019, 12:47 PM

                      review the first screenshot in the topic (105.57.94.2) is listes as a DNS server. Yes, uncheck that, you have the firewall performing as a DNS server itself (listed as 127.0.0.1). its capable of looking up DNS itself would the use of an upstream DNS server from WAN.

                      1 Reply Last reply Reply Quote 0
                      • C
                        coachever
                        last edited by Feb 21, 2019, 1:02 PM

                        @isolatedvirus
                        Is this right?

                        0_1550754033196_PfSense2.png

                        But after that, there is no ping response from WAN side to yahoo.com

                        0_1550754069228_ping to yahoo from WAN.png

                        I think we'are very to close to succeed, but my knowledge and experience is too low, sorry

                        1 Reply Last reply Reply Quote 0
                        • I
                          isolatedvirus
                          last edited by Feb 21, 2019, 1:02 PM

                          hostname www.yahoo.com

                          C 1 Reply Last reply Feb 21, 2019, 1:09 PM Reply Quote 0
                          • C
                            coachever @isolatedvirus
                            last edited by Feb 21, 2019, 1:09 PM

                            @isolatedvirus

                            Ping to www.yahoo.com

                            0_1550754529579_ping to www.yahoo.com from WAN.png

                            1 Reply Last reply Reply Quote 0
                            • I
                              isolatedvirus
                              last edited by Feb 21, 2019, 1:25 PM

                              Before doing any of the following, perform this:
                              System->Advanced->Netowrking
                              Disable Checksum/TCP Seg/ Large Receive offloading.
                              On windows: Ping 8.8.8.8
                              On windows: Navigate to www.duckduckgo.com or perform nslookup
                              If this is working, perform a nslookup on pfsense to confirm you can resolve www.duckduckgo.com

                              what are the outgoing DNS interfaces set as in the DNS resolver?

                              Confirm the following: System-> General Setup
                              -No DNS servers configured.
                              -DNS Override UNCHECKED
                              -Disable DNS Forwarder UNCHECKED

                              Services -> DNS Forwarder
                              -Enable DNS Forwarder UNCHECKED

                              Services -> DNS Resolver
                              -Enable DNS Resolver CHECKED
                              -Network Interfaces ALL
                              -Outgoing Interfaces WAN (or whatever your uplink interface is)
                              -DNS Query Forwarding UNCHECKED

                              On windows:
                              Ping 8.8.8.8
                              In a browser, navigate to www.duckduckgo.com, or perform a nslookup

                              On pfsense
                              ping 8.8.8.8
                              perform nslookup for www.duckduckgo.com

                              1 Reply Last reply Reply Quote 0
                              • G
                                Gertjan @coachever
                                last edited by Feb 21, 2019, 3:16 PM

                                @coachever said in How to config the LAN interface users to Internet (Basic configuration):

                                https://www.tecmint.com/installation-and-configuration-of-pfsense-firewall-router/
                                This is the tutorial link,

                                That's an old version of pfSense.
                                Never ever use these kind of videos. Use the official videos first. And because you don't want to find differences, errors or whatever issue exists between old version and recent version, you should stick with the official videos.

                                If WAN is setup - then you do not need to think or do anything related to DNS.
                                It works out of the box.
                                pfSense behaves like any other router/firewall : set up WAN and you have a connection to the net.

                                By (incompletely) following some video you broke your DNS setup. (because the video isn't right, some needed settings aren't mentioned or because the situation changed).

                                It's like you're using an Windows XP tuto for Windows 10.

                                Btw : Official videos are here.

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

                                1 Reply Last reply Reply Quote 0
                                • JeGrJ
                                  JeGr LAYER 8 Moderator
                                  last edited by Feb 25, 2019, 12:37 PM

                                  @coachever

                                  In your first Post your pfSense WAN interface was configured (via DHCP?) to 192.168.1.8.
                                  In later posts it happens to be 10.0.2.15.

                                  What is your WAN connection? How do you connect pfSense to your ISP/uplink/Internet? DNS may be a problem, but I think you don't have your WAN running correct. Also if your WAN is indeed a private IP, uncheck the "block private IPs" checkbox on "Interfaces / WAN".

                                  Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                                  If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    coachever
                                    last edited by Mar 11, 2019, 8:36 AM

                                    I think the problem is on DNS Resolver, which is, when I uncheck the DNS Resolver

                                    0_1552293307706_6e24b710-49b2-4eff-8062-1ece08fc9d12-image.png

                                    then the client can connect to the internet. On the other hand, when I check (enable) the DNS Resolver

                                    0_1552293329634_4fbeb5db-ea29-41ed-a72d-6d8f5507f171-image.png

                                    0_1552293345181_5feeb2ff-c0b5-4f3d-9ce0-fe4dbaf06bbe-image.png

                                    clients then unable to connect to the internet. So the problem is DNS Resolver, i guess. What should I do?

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      Gertjan
                                      last edited by Mar 11, 2019, 9:04 AM

                                      The Resolver should be activated, or the Forwarder.
                                      One or the other.
                                      Both : impossible.

                                      Up to you to choose one.
                                      However : The Resolver (or Forwarder) has to be set up correctly.
                                      When you installed pfSense, the Resolver is activated and will work right out of the box. No changes from you are needed.

                                      Running pfSense with no Resolver neither Forwarder is no advised at all.

                                      And what about answering questions ?
                                      Like the one @JeGr asked ?

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

                                      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