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

Pfsense 2.4.4 no internet access! Help please! (Solved)

Firewalling
4
13
18.2k
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.
  • S
    smrehan00
    last edited by smrehan00 Mar 8, 2019, 5:17 AM Mar 4, 2019, 8:13 PM

    Hello Everyone,

    I am having problems accessing the internet from LAN side. I have a very simple setup.

    Cable Net Router (tplink) - > Pfsense - > PC

    The cablenet router uses a PPPOE connection to grant internet access to the devices on LAN. The Wan connection has a subnet of 192.168.0.x as defined on tplink router. I have configured WAN as DHCP (private ip) and lan interface as 172.22.101.1. The problem is that I am unable to access internet from LAN no matter what I do. The default allow to any rule is present. I have no other rule configured. I have a doubt that my internet connection may be restricted as internet works fine when I connect my laptop to it directly.
    I am attaching the firewall logs for reference.
    I am also attaching the configuration xml file that I backed up.

    Kindly let me know if you find any errors. Thank you in advance.0_1551730337227_config-pfSense.test-20190304171039.xml
    0_1551730361032_logs.xls

    The check mark is next to all entries in the excel file for logs except for one which has an x mark next to it.

    S G 2 Replies Last reply Mar 4, 2019, 9:04 PM Reply Quote 0
    • K
      KOM
      last edited by Mar 4, 2019, 8:39 PM

      Have you gone through the Connectivity guide? It should just work right out of the box.

      https://doc.pfsense.org/index.php/Connectivity_Troubleshooting

      1 Reply Last reply Reply Quote 0
      • S
        smrehan00 @smrehan00
        last edited by smrehan00 Mar 4, 2019, 9:05 PM Mar 4, 2019, 9:04 PM

        @KOM

        I tried those steps but it didn't work.I can't get to the internet. Did you check the logs and configuration file?

        1 Reply Last reply Reply Quote 0
        • K
          KOM
          last edited by KOM Mar 4, 2019, 9:32 PM Mar 4, 2019, 9:32 PM

          I tried those steps but it didn't work

          If I had a dollar every time I heard that one...

          Did you check the logs and configuration file?

          Nope. Trying to decipher a mishmash of xml isn't what I call fun.

          From Diagnostics - Ping, can you ping 8.8.8.8?

          S 1 Reply Last reply Mar 5, 2019, 4:23 AM Reply Quote 1
          • S
            smrehan00 @KOM
            last edited by Mar 5, 2019, 4:23 AM

            @kom I tried to ping 8.8.8.8 from diagnostics but it didn't work. What I found out is that the monitor IP (8.8.8.8) which I use to check the status of the default gateway is showing down. I just got to work. Let me post the screenshots for a better understanding.

            S 1 Reply Last reply Mar 5, 2019, 6:54 AM Reply Quote 0
            • S
              smrehan00 @smrehan00
              last edited by smrehan00 Mar 5, 2019, 7:20 AM Mar 5, 2019, 6:54 AM

              @KOM Here are the screenshots!
              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              login-to-view

              1 Reply Last reply Reply Quote 0
              • K
                KOM
                last edited by Mar 5, 2019, 2:19 PM

                Hmmm. You have some weirdness going on. Unbound (DNS Resolver) not being to bind to a socket, and the WAN gateway showing offline.

                Has this ever worked or is it a new installation? Whats on the WAN side, just a cable modem? If so, you should see if your ISP can flip it to bridged mode so that you're not double-NATing.

                1 Reply Last reply Reply Quote 0
                • G
                  Gertjan @smrehan00
                  last edited by Gertjan Mar 5, 2019, 2:56 PM Mar 5, 2019, 2:56 PM

                  You said your WAN IP is a 'private IP' :
                  @smrehan00 said in Pfsense 2.4.4 no internet access! Help please!:

                  I have configured WAN as DHCP (private ip)

                  192.168.0.x, right ?

                  Now, check your first rule on the WAN interface :

                  @smrehan00 said in Pfsense 2.4.4 no internet access! Help please!:

                  login-to-view

                  You're blocking private networks - such as, for example 192.168.0.x.

                  It's time to make a choice ^^

                  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
                  • K
                    KOM
                    last edited by Mar 5, 2019, 2:58 PM

                    That RFC block on WAN would only affect incoming traffic to any NATs he might define. It's not going to affect outgoing LAN traffic and their replies.

                    G 1 Reply Last reply Mar 5, 2019, 3:03 PM Reply Quote 0
                    • G
                      Gertjan @KOM
                      last edited by Mar 5, 2019, 3:03 PM

                      @kom said in Pfsense 2.4.4 no internet access! Help please!:

                      That RFC block on WAN would only affect incoming traffic to any NATs he might define

                      Such as the third WAN firewall rule ?

                      Any, I stand corrected, just checked mine, using a 192.168.10.5 WAN IP : nothing changed (could post this message).

                      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
                      • A
                        akuma1x
                        last edited by akuma1x Mar 5, 2019, 4:08 PM Mar 5, 2019, 3:16 PM

                        A couple of observations...

                        1. You're probably double-NAT'ed by using a cable modem that is already running NAT. That could potentially cause trouble, unless you know how to work around it. Like has been said above, see if you can get your cable modem put into bridge mode, that makes setting up your WAN interface a lot less trouble-free when it comes to overlapping or conflicting network address space and NAT rules.
                        2. I don't think you need to set the Gateway addresses under System -> General Setup -> DNS Server Settings. In my several pfsense installs, these fields are always empty.
                        3. On your LAN General Config page, you've got a /16 subnet mask. That's a pretty big range, allowing you to have 65,000 plus host machines on that network. Do you need a network that big for this project?
                        4. Your WAN is using a private IP address of 192.168.0.106, normally this doesn't cause a problem, unless your ISP modem is also using the same network space somewhere in it's network settings.

                        Jeff

                        S 1 Reply Last reply Mar 5, 2019, 5:52 PM Reply Quote 0
                        • S
                          smrehan00 @akuma1x
                          last edited by Mar 5, 2019, 5:52 PM

                          @akuma1x
                          @KOM

                          I was able to resolve the issue.It was because of the internet connection as it was blocking dns and moreover the internet connection had asymmetric routing done.
                          I tested the same scenario remotely from my UK office and it worked without a problem.

                          S 1 Reply Last reply Mar 5, 2019, 5:55 PM Reply Quote 0
                          • S
                            smrehan00 @smrehan00
                            last edited by Mar 5, 2019, 5:55 PM

                            @akuma1x
                            @KOM

                            Thanks guys for your help.

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