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

    Upgrade issue (LAN has no internet access), DNSMASQ not working

    Problems Installing or Upgrading pfSense Software
    4
    7
    2.6k
    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.
    • J
      jan.gestre
      last edited by

      Hi,

      It's been a while since I've touched our 1.2.3 box, upgraded it to 2.0RC3 using console, removed first all packages as suggested (NAT and Rules are the only thing remained) unfortunately, after the upgrade, the internet connection was lost. I've found out that DNSMASQ is not working as it should i.e. does not forward DNS request to outside (OpenDNS). Already tried enabling/disabling the service, to no avail, still doesn't work. At one point, the web configurator was not accessible so I had no other recourse but to wipe everything, good thing though is that I have a backup.

      Tried this procedure twice and end up with the same not working box.

      Anyone here experienced this?

      What about a clean 2.0RC3 install, would my working config 1.2.3 config work? I don't want to disturb people working anymore that is why I haven't tried this one yet.

      TIA

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

        does i work when you enter a different dns server into the pfsense general settings ? one like 8.8.8.8 ?

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          There are many builds labelled "RC3". It might be useful if you could identify more specifically the build(s) you have attempted to use; full name of the file or the build id from the web GUI home page.

          There have been a number of reports of people having problems with upgrades because their 1.2.3 configuration files have contained "international" characters. I have no idea whether that could cause the sort of problem you are reporting. You might get some clues by searching the "2.0" forum for something like "international character".

          1 Reply Last reply Reply Quote 0
          • J
            jan.gestre
            last edited by

            @wallabybob:

            There are many builds labelled "RC3". It might be useful if you could identify more specifically the build(s) you have attempted to use; full name of the file or the build id from the web GUI home page.

            There have been a number of reports of people having problems with upgrades because their 1.2.3 configuration files have contained "international" characters. I have no idea whether that could cause the sort of problem you are reporting. You might get some clues by searching the "2.0" forum for something like "international character".

            The one from the upgrade mirrors –> pfSense-Full-Update-2.0-RC3-i386-20110621-1542.tgz

            AFAIK, there is no international characters in my configuration.

            1 Reply Last reply Reply Quote 0
            • J
              jan.gestre
              last edited by

              Here's what I've done today:

              Re-installed version 2.0 from scratch, everything seems to be working fine when only the default rule is set i.e. LAN to Any is allowed. If I restrict the ports e.g. only allowed ports 25, 80… then the internet stops working, it will only work if I allowed everything.

              Any ideas?

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @madapaka:

                everything seems to be working fine when only the default rule is set i.e. LAN to Any is allowed. If I restrict the ports e.g. only allowed ports 25, 80… then the internet stops working, it will only work if I allowed everything.

                Which interface has the firewall rules you mention?

                Firewall rules have a number of parameters: it is not sufficient to provide only one ambiguously identified parameter (which port: source port or destination port?)

                What are you attempting to block or allow?

                1 Reply Last reply Reply Quote 0
                • M
                  Metu69salemi
                  last edited by

                  blocking 80 and 443 to any is somewhat enough to block browsing totally

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