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

    3100 tries to configure WAN before fiber modem has uplink

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 523 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.
    • B
      bson
      last edited by

      I have a problem where my NetGate 3100 running 22.05-RELEASE (arm) fails to obtain a WAN lease on power cycle. It's attached to an AT&T BGM320-505 modem and AT&T FTTH 1g/1g service.

      The problem is if power goes when it returns it fails to set up the WAN port with a DHCP lease. I believe this is because the NG 3100 starts up faster than the modem and tries to configure the interface before the modem is ready. It never recovers from this and if it tries again I see no indication of this anywhere. I consistently have to reboot the router (Diagnostics->Reboot (Normal)) after which it's resolved. I suspect the modem gbe port establishes a link shortly after power-on, long before it actually has an proper uplink. Maybe the router DHCP client has a retry timer that's way too long for this application (it could really keep trying every 10 seconds, forever).

      Any thoughts on how I might configure the NG 3100 to get around this issue?

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

        You might be hitting this: https://redmine.pfsense.org/issues/13671
        Do you see the WAN interface show link UP after dhclient has run?

        The easiest fix there is just to delay the 3100 boot as shown in the note:
        https://redmine.pfsense.org/issues/13671#note-2

        Though the patch shown there should also work. If that's what you're seeing.

        Steve

        1 Reply Last reply Reply Quote 1
        • B
          bson
          last edited by

          Thanks! I added a delay to /boot/loader.conf.local, seems like that should take care of it. Appreciate the issue link.

          1 Reply Last reply Reply Quote 1
          • V viragomann referenced this topic on
          • V viragomann referenced this topic on
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.