Navigation

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

    WAN Pulls DHCP - No Internet Access - Random

    General pfSense Questions
    6
    8
    713
    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.
    • D
      Detroit last edited by

      I am pulling my hair out over this one, and I dont know if its config or hardware but I am about to give up and go Edge Router Lite so the wife doesn't kill me. This is the same problem I had originally, posted here: https://forum.pfsense.org/index.php?topic=105420.msg587542#msg587542 I have just been dealing with it.

      I have this box: http://www.aliexpress.com/store/product/2015-mini-pc-Qotom-T4010P-with-core-i3-Dual-H-D-M-I-6-serial-ports/108231_32549490575.html

      Setup:
      Internet -> SB6183 Cable Modem (Comcast) -> Pfsense Router -> PC

      Pfsense:
      Version 2.3.x amd64

      Pfsense hardware:
      Qotom-T4010P (i3-4010U)
      2 * Intel 82574L - 10/100/1000 Controller
      WAN:
      DHCP External IPV4 & IPV6 – 67.x.x.x

      LAN:
      192.168.1.1/24

      Ever since the first install PfSense will randomly choose to work, or not. If I do get it working, it will be fine (usually) until a reboot, then it fails to work again. To get it working again, I generally just reset to defaults and power cycle everything over and over until it chooses to work. If I hook the modem into my PC, works fine everytime.

      Usually the WAN will pull the DHCP IPv4 (sometimes it will just pull IPv6 only, or have to go through a renew cycle to pull IPv4) but I am unable to ping out. This is on a basic default wizard install, unchecking the two "Block" boxes on WAN for good measure.

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

        This may sound obvious, but have you tried setting your WAN address statically? From what you describe, your cable modem is assigning the address to your WAN interface, is this so?

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

          so your wan has an IP, can you ping your gateway…  If you have an IP.. is your lack of internet just a dns related problem?

          1 Reply Last reply Reply Quote 0
          • D
            Detroit last edited by

            So, oddly now I can not even pull an IPV4 IP through DHCP.

            Other than that, I dont think it is DNS only because inside of the router I was unable to ping 8.8.8.8 (when I did have DHCP).

            Presently they just end up pending:

            And Gateways page:

            And WAN settings:

            I have not tried setting static, but when it pulls DHCP it appears correct.

            1 Reply Last reply Reply Quote 0
            • C
              cmb last edited by

              You're losing your IP on WAN. What logs do you have from dhclient in your DHCP log?

              1 Reply Last reply Reply Quote 0
              • D
                Detroit last edited by

                Seems pretty straightforward now for not getting a lease anyway:

                May 16 09:56:33 dhclient FAIL
                May 16 09:56:49 dhclient ARPSEND
                May 16 09:56:51 dhclient ARPCHECK
                May 16 09:58:08 dhclient FAIL
                May 16 09:59:24 dhclient FAIL
                May 16 10:00:40 dhclient FAIL

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

                  Detroit, your post is now a few years old, but I would like to know if you ever managed to solve this problem?

                  1 Reply Last reply Reply Quote 0
                  • stephenw10
                    stephenw10 Netgate Administrator last edited by

                    Start a new thread for this with a full description of your specific issue.
                    Any DHCP bug that existed in 2016 almost certainly doesn't apply in the current version.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Products

                    • Platform Overview
                    • TNSR
                    • pfSense
                    • Appliances

                    Services

                    • Training
                    • Professional Services

                    Support

                    • Subscription Plans
                    • Contact Support
                    • Product Lifecycle
                    • Documentation

                    News

                    • Media Coverage
                    • Press
                    • Events

                    Resources

                    • Blog
                    • FAQ
                    • Find a Partner
                    • Resource Library
                    • Security Information

                    Company

                    • About Us
                    • Careers
                    • Partners
                    • Contact Us
                    • Legal
                    Our Mission

                    We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                    Subscribe to our Newsletter

                    Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                    © 2021 Rubicon Communications, LLC | Privacy Policy