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

    Autoupdate of WAN address doesn't seem to work

    Firewalling
    4
    17
    5.8k
    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.
    • H
      hoba
      last edited by

      I'm in germany too on dynamic IP with 24h forced disconnects. I don't see the problem here. Are you absolutely sure your DynDNS account updates are working?

      1 Reply Last reply Reply Quote 0
      • Y
        yoogie
        last edited by

        Yes, I did an nslookup (from an external computer) and got the actual wan address of the firewall.

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

          Can you verify by looking at /tmp/rules.debug (diagnostics>edit file) that there is a problem with the firewallrules after your IP has changed? Also please upgrade to the latest snapshot to see if the problem was not already fixed in the meantime.

          1 Reply Last reply Reply Quote 0
          • Y
            yoogie
            last edited by

            Should this file be generated each time I get a new ip address?

            The reason why I am asking is that the file is 3 days old now and I got a new address a few hours ago.

            I will try the trunk and report here.

            Thanks for your answer.

            Cheers, Manuel

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              @yoogie:

              Should this file be generated each time I get a new ip address?

              The reason why I am asking is that the file is 3 days old now and I got a new address a few hours ago.

              I will try the trunk and report here.

              Thanks for your answer.

              Cheers, Manuel

              Sounds like checkreloadstatus is exiting.  We added a fix but it requires updating to a recent snapshot, download the configuration file and in the <cron>area insert:

              <minute>/5</minute>
              <hour>
              </hour>
              <mday></mday>
              <month>
              </month>
              <wday>*</wday>
              <who>root</who>
              <command></command>/usr/local/bin/checkreload.sh

              Then re-upload the config file.</cron>

              1 Reply Last reply Reply Quote 0
              • Y
                yoogie
                last edited by

                Hm,

                I have made a backup of the configuration from within the web interface. Unfortunately there is no section called cron.

                Should I add it somewhere?

                Cheers,
                Manuel

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

                  Add it at the very bottom like:

                  
                  ...
                     <cron><minute>*/5</minute>
                           <hour>*</hour>
                           <mday>*</mday>
                           <month>*</month>
                           <wday>*</wday>
                           <who>root</who>
                           <command></command>/usr/local/bin/checkreload.sh</cron> 
                  
                  

                  You have to be at the latest snapshot version for this to work.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by

                    Try uptdaing to the latest snapshot.  This entry should be auto added when it updates the config.

                    1 Reply Last reply Reply Quote 0
                    • JeGrJ
                      JeGr LAYER 8 Moderator
                      last edited by

                      What's strange to me (as I'm in germany too and these things described work like charme in earlier versions of pfSense up until the recent snapshot without problems at all) is:

                      - Dial on demand disabled
                        - Idle timeout disabled

                      I have configured my boxes to DialOnDemand enabled with an idle timeout of 0 (as this is none at all so stay connected and redial if disconnected by provider) and with the new snapshot I added Daniels brilliant Cron Setting for disconnecting at a specific time to workaround the 24h disconnect (I set it up for 0500 every morning).

                      With this config I have pfSense running until a pre-1.0 Release and hadn't had a problem on the way with DynDNS or connecting from an external IP (setup exactly like yoogie with SSH and HTTP(s) from an external static IP).

                      Just an idea…

                      Greets Grey

                      Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                      If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

                      1 Reply Last reply Reply Quote 0
                      • Y
                        yoogie
                        last edited by

                        Hi there,

                        thanks for your help.

                        I have recently rebuilt the whole system and reconfigured all the stuff. We will see tomorrow if it is solved or not. I will report.

                        Cheers,
                        Manuel

                        1 Reply Last reply Reply Quote 0
                        • Y
                          yoogie
                          last edited by

                          Ok, another problem running "1.0.1 built on Mon Nov 13 05:22:16 UTC 2006".

                          I have configured the DSL line, the transparent squid and captive portal. The rules are set properly, but now I cannot connect from inside to outside at all. It seems that squid doesn't generate the transparent nat rule…

                          Weird.

                          Should I roll back to 1.0.1 stable and check the options, grey has suggested? What do you think?

                          Cheers,
                          Manuel

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

                            I suggest running the latest snapshot (your built time is 2006 Nov 13) which is pretty old. It should work fine with the latest snapshot I think.

                            1 Reply Last reply Reply Quote 0
                            • Y
                              yoogie
                              last edited by

                              Oh damn, my fault… I am sorry.

                              I got that image from the swiss mirror. The date on the server was 6th feb 07. I am pretty sure...

                              Well I will give it another try.

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

                                You want to use http://snapshots.pfsense.com/FreeBSD6/RELENG_1/

                                1 Reply Last reply Reply Quote 0
                                • Y
                                  yoogie
                                  last edited by

                                  Great thanks. Will do that tomorrow or friday

                                  Cheers,
                                  Manuel

                                  1 Reply Last reply Reply Quote 0
                                  • Y
                                    yoogie
                                    last edited by

                                    Hi there,

                                    it seems to work now. Thank you very much for your help.

                                    BTW: The new web-interface looks gorgeous ;)

                                    Cheers,
                                    Manuel

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