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

    Upgraded to 2.1.1 -> internet not working anymore

    Scheduled Pinned Locked Moved NAT
    12 Posts 4 Posters 2.3k 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.
    • L
      luckylinux
      last edited by

      Since the upgrade from Pfsense 2.0.3 to 2.1.1 internet connection is not working anymore from my LAN clients.
      At the moment I fall back to a backup router but I want to get back to Pfsense ASAP  ;)

      Basically this is what I get:

      • From LAN clients I can PING 192.168.1.1 (Pfsense Router) successfully
      • From Pfsense router I can PING google.com successfully
      • From LAN clients I cannot PING google.com successfully

      This really seems odd. What could be wrong? DNS doesn't seem an issue to me because I tried using Google's DNS servers with no avail.
      DHCP shouldn't matter either because LAN clients are configured as static IP addresses.

      Any tips / solutions to this problem?
      Thank you for your help  ;)

      ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
      NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
      NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Does google.com resolve to an IP address from the client? (It sounds like it does, so your DNS is working)
        System->Routing - is there a LAN gateway there - it should not be, and if so change Interfaces->LAN gateway to none, from System->Routing delete LAN gateway. Make sure WAN gateway is selected as default.
        Do you have multi-WAN with policy-based routing?
        Post your LAN… subnet details and rules...

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • L
          luckylinux
          last edited by

          @phil.davis:

          Does google.com resolve to an IP address from the client? (It sounds like it does, so your DNS is working)

          Yes  ;)

          @phil.davis:

          System->Routing - is there a LAN gateway there - it should not be, and if so change Interfaces->LAN gateway to none, from System->Routing delete LAN gateway.

          There is no LAN gateway  ;).

          @phil.davis:

          Make sure WAN gateway is selected as default.

          It is

          @phil.davis:

          Do you have multi-WAN with policy-based routing?

          I'm almost certain that I don't since I only have 1 ISP. I connect the cable modem to the Pfsense box.

          @phil.davis:

          Post your LAN… subnet details and rules...

          I'm not sure I understand. What commands should I run / where should I take the screenshot from?

          Again the problem appeared when I upgraded Pfsense to 2.1.1. Couldn't this be a bug?
          I see lots of error messages (see attached screenshot) generated about every minute. I can't see the details though (when I click I'm redirected to the Dashboard). Is it related to my problem?
          Thank you  ;)

          pfsense_error.png
          pfsense_error.png_thumb

          ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
          NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
          NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            The problem is in the rules somewhere. The packet filter (pf) is choking on something in the rule set. It ends up with no rules, and nothing being passed.
            We need to see what rule has a problem. It could be in Firewall->Rules or in Firewall->NAT section.
            Post screen shots of your Firewall Rules and any NAT (port forwards, manual outbound NAT or…)or traffic shaping that you have.
            Also, the content of /tmp/rules.debug would be useful - that has the rules that pfSense generated and tried to apply.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • L
              luckylinux
              last edited by

              @phil.davis:

              Also, the content of /tmp/rules.debug would be useful - that has the rules that pfSense generated and tried to apply.

              I can't load it from the WEB interface. It says:

              File does not exist or is not a regular file.

              @phil.davis:

              The problem is in the rules somewhere. The packet filter (pf) is choking on something in the rule set. It ends up with no rules, and nothing being passed.
              We need to see what rule has a problem. It could be in Firewall->Rules or in Firewall->NAT section.
              Post screen shots of your Firewall Rules and any NAT (port forwards, manual outbound NAT or…)or traffic shaping that you have.

              See attached screenshots below  ;) I'm a bit surprised by the duplicated entry for server 192.168.1.40 on port 22 (SSH) although that shouldn't be the cause of the issue I'm currently experiencing  :o

              pfsense_firewall_rules_LAN.png
              pfsense_firewall_rules_LAN.png_thumb
              pfsense_firewall_rules.png
              pfsense_firewall_rules.png_thumb
              pfsense_NAT.png
              pfsense_NAT.png_thumb

              ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
              NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
              NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by

                why do you have 6 copies of the same rule for 1194 udp (openvpn)

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                • L
                  luckylinux
                  last edited by

                  @johnpoz:

                  why do you have 6 copies of the same rule for 1194 udp (openvpn)

                  No idea  :-[
                  I doubt that's the cause of the problem though …

                  ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
                  NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
                  NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

                  1 Reply Last reply Reply Quote 0
                  • S
                    Supermule Banned
                    last edited by

                    Why are you not routing port 53 UDP outbound?

                    1 Reply Last reply Reply Quote 0
                    • L
                      luckylinux
                      last edited by

                      @Supermule:

                      Why are you not routing port 53 UDP outbound?

                      Why should I / what is that port used by Pfsense for?

                      ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
                      NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
                      NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        "I doubt that's the cause of the problem though .."

                        Well it points to not having a clue to how to setup rules ;)  Or maintaining them - and your error is some rule can not load is it not?

                        I would wipe your rules and start over..  Its not like you have very many.  If your 1194 is any indication you prob don't need most of the rules on there ;)

                        Do you want the block private on your wan?  Do you happen to be behind a NAT on pfsense wan?

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • P
                          phil.davis
                          last edited by

                          Just guessing - normally the port forwards on WAN would have destination WANaddress (or some other virtual IP on WAN) rather than destination IP any.

                          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                          1 Reply Last reply Reply Quote 0
                          • L
                            luckylinux
                            last edited by

                            @johnpoz:

                            I would wipe your rules and start over..  Its not like you have very many.  If your 1194 is any indication you prob don't need most of the rules on there ;)

                            Well at this point I could also reinstall Pfsense 2.1.1 on new hardware since one disk failed  ;)

                            @johnpoz:

                            Well it points to not having a clue to how to setup rules ;)  Or maintaining them - and your error is some rule can not load is it not?

                            You're right. No clue about that.

                            @johnpoz:

                            Do you happen to be behind a NAT on pfsense wan?

                            No. Pfsense if my NAT/Firewall/Router.

                            ASUS E35M1-M PRO (AMD E-350), 8GB RAM, 2x500GB GEOM GMIRROR
                            NIC DETECTED: 1 x PCI INTEL PWLA8391GT , 1 x OnBoard REALTEK 8111E, 1 x PCIe INTEL EXPI9301CTBLK , 1 x PCI PLANET ENW-9605
                            NIC UNDETECTED: 1 x INTEL EXPI9301CTBLK

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