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

    Cogeco Connection Issue

    DHCP and DNS
    2
    6
    1.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.
    • C
      cgrichard
      last edited by

      My ISP is Cogeco, and I currently use a TP-Link wireless router.  It acts as a DHCP client and dynamically gets an IP of 2xx.xxx.xxx.145, a netmask of 255.255.255.128, and a gateway of 2xx.xxx.xxx.129.  (An IP from a split C-Class - ie /25). I am in the process of replacing the old router with a pfSense installation [2.2.5] on an older spare computer.

      The pfSense box, with the WAN interface (nfe0) set up as a DHCP client will not pick up this information.  I thought it might be a faulty interface, but if I plug the pfSense WAN interface into the above mentioned TP-Link router, it is given an IP with no problem, (192.168.1.112)  So, I believe the interface works properly.  The ethernet cable being used has been tested and is working.

      I believe I may be doing something wrong, or am missing some setting?  Has anyone had a similar problem?  Amy suggestions?

      Thanks

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Reconnect pfSense to WAN and then bounce your cable modem at least once.  On a lot of ISP gear, you have to reboot the unit for it to bind to a new MAC address presented by your router.

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

          Thanks for your reply.

          What do you mean by Bounce?

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            To bounce: make it go down, then back up.  In other words, do a power-cycle.  Turn it off, wait, turn it on.

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

              Thanks

              1 Reply Last reply Reply Quote 0
              • KOMK
                KOM
                last edited by

                I think I remember someone saying that some modems needed to be off for at least 30 seconds to properly reset them, so take that into account as well.

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