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

    PfSense with ARRIS MODEM and Linksys E900 DDWRT

    Scheduled Pinned Locked Moved General pfSense Questions
    24 Posts 6 Posters 2.9k 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.
    • N
      nycfly
      last edited by

      This behavior indeed seems strange.

      Is the WAN interface on pfSense set to DHCP?

      1 Reply Last reply Reply Quote 0
      • A
        AnointedOne
        last edited by

        This behavior indeed seems strange

        Yes it is and annoying. But I just decided to use what I have rather than trying to re-establish what was there before. I port forwarded with the public ip and it works now. Thanks a bunch. Would like for it to be how it was but time is a factor. :) But now i have another problem. Will start a separate post for that one x.x

        1 Reply Last reply Reply Quote 0
        • N
          nycfly
          last edited by

          DDNS clients that run on Windows/Mac/Linux client machines will use an external website to verify your public IP (there may also be such a client available as a package for pfSense as I don't think the built-in client does this). You could use one of those to update your DDNS so that your cameras or VPN can be used if your public IP changes, even if it doesn't change on pfSense.

          1 Reply Last reply Reply Quote 0
          • MikeV7896M
            MikeV7896
            last edited by

            Some ISPs require that you use their gateway (modem + router in one) in order to get a static public IP address. They run a routing protocol on their router that communicates with their upstream routers, telling them to route data for your static IP address to your gateway. They don't allow third-party devices to run the same routing protocol because there is significant potential for abuse by giving out the key(s) needed for the routing protocol to function.

            So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.

            The S in IOT stands for Security

            1 Reply Last reply Reply Quote 0
            • A
              AnointedOne
              last edited by

              Some ISPs require that you use their gateway (modem + router in one) in order to get a static public IP address. They run a routing protocol on their router that communicates with their upstream routers, telling them to route data for your static IP address to your gateway. They don't allow third-party devices to run the same routing protocol because there is significant potential for abuse by giving out the key(s) needed for the routing protocol to function.

              So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.

              Ahhhhh, ok. Thanks for the info. Things is now that I have opened the required ports, and have access to the cameras, I don't have access from a remote location. I think when I go there for the weekend, I will reset the modem back to default and see what I can do.

              My VPN don't work remotely either. On site, all is well, offsite no connection

              1 Reply Last reply Reply Quote 0
              • A
                AnointedOne
                last edited by

                So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.

                Quick update
                Ok, here is another thing now. I got the same modem home (think it should be the same model, ISP change the models some time) and the modem in bridged and my public IP is the same as my router WAN IP.

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

                  Why aren't you  setting  pfsense to update ddns any time the IP changes ?  thats all you have to do to keep using dynamic IP

                  1 Reply Last reply Reply Quote 0
                  • A
                    AnointedOne
                    last edited by

                    Why aren't you  setting  pfsense to update ddns any time the IP changes ?  thats all you have to do to keep using dynamic IP

                    The DDNS service is from the camera manufacturer. If I can set pfSense to use the service that would be great. Is there a tutorial on how to set it up if possible?

                    https://myq-see.com/ That's the website

                    1 Reply Last reply Reply Quote 0
                    • R
                      remlei
                      last edited by

                      check your IP camera if it has something like a polling task that checks your wan ip every x minutes. if those IP cameras doesnt have that feature, those IP camera probably suck ask the manufacturer to fix that.

                      and since you paid for DDNS service (I dont know why you would since there's a lot of free DDNS service out there anyway) ask them how to integrate the DDNS service to pfsense.

                      1 Reply Last reply Reply Quote 0
                      • A
                        AnointedOne
                        last edited by

                        check your IP camera

                        Not IP cameras (sadly)

                        since you paid for DDNS service

                        The service is free with the product (but yea guess in a way it is paid for)

                        there's a lot of free DDNS service out there anyway

                        Will check online but you recommend? Desperate here.

                        UPDATE
                        For a quick fix, I reset the modem again, set in bridged mode and directly connected to the linksys. WAN IP is shown as my public IP online. Decided to work "normally" for some reason but still getting hiccups with that ddns thing. Worked fine last night when i tested it at home but now…....in and out x.x

                        UPDATE 2
                        I took the pfsense PC to my home to do further troubleshooting and diagnostics. And again my public ip matches my pfsense WAN IP. Lol This is a odd things that's happening here. Right now, I'm going to monitor it and I have isolate the issue either to the modem or linksys (thoughts are pointing to the modem for me personally)

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

                          Just setup pfsense to update you ddns account anytime the IP changes.

                          NO-IP is free https://www.noip.com/

                          Tutorial  https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense

                          ![DNS 1.PNG](/public/imported_attachments/1/DNS 1.PNG)
                          ![DNS 1.PNG_thumb](/public/imported_attachments/1/DNS 1.PNG_thumb)
                          ![DNS 2.PNG](/public/imported_attachments/1/DNS 2.PNG)
                          ![DNS 2.PNG_thumb](/public/imported_attachments/1/DNS 2.PNG_thumb)

                          1 Reply Last reply Reply Quote 0
                          • A
                            AnointedOne
                            last edited by

                            @Chrismallia:

                            Just setup pfsense to update you ddns account anytime the IP changes.

                            NO-IP is free https://www.noip.com/

                            Tutorial  https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense

                            Ok thanks. I setup pfSense already with the DDNS but I took the machine to my home to troubleshoot certain issues I was experiencing. Got one more thing to solve, then all should be good. My public IP is operating good, matching my WAN IP on pfSense. So after I resolve one more issue, I will be bringing it back. Thanks

                            1 Reply Last reply Reply Quote 0
                            • A
                              AnointedOne
                              last edited by

                              @Chrismallia:

                              Just setup pfsense to update you ddns account anytime the IP changes.

                              NO-IP is free https://www.noip.com/

                              Tutorial  https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense

                              Just wanted to say thanks for your input. I got it working properly now. It was even better than the DDNS Service the manufacturer provides.

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

                                "Just wanted to say thanks for your input. I got it working properly now. It was even better than the DDNS Service the manufacturer provides."

                                Very glad  to hear it, even happier got it working for a church  ;)

                                1 Reply Last reply Reply Quote 0
                                • chpalmerC
                                  chpalmer
                                  last edited by

                                  What model of modem?
                                  http://badmodems.com/

                                  Puma modems will bog down with lots of UDP traffic and cause issues similar to yours.

                                  Triggering snowflakes one by one..
                                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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