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

    Still, no second WAN / OPT1 DynDNS support?

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 3 Posters 1.7k 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.
    • T Offline
      tekoholic
      last edited by

      Having already posted this issue, I went back to update my thread (http://forum.pfsense.org/index.php/topic,13126.0.html) after having discovered that it has not improved, only to find it locked by admin.

      Things have changed slightly, at this point:  Currently running WAN with Public IP over cable, OPT1 with PPPoE and Public IP over DSL.  Both are dynamic.  Being as cable is port-blocked, I attempted to activate DynDNS services on a FRESH LOAD:
      2.0-ALPHA-ALPHA
      built on Sat Dec 5 23:50:02 EST 2009
      FreeBSD 8.0-RELEASE-p1

      Things hung for 2-3 minutes, and then my OPT1 account with DNS-O-Matic was updated with my WAN IP address.  Odd, but at least the update occurred.  So, I added an account for the WAN iface, assuming that they might just be somehow reversed, but the result was 2 accounts updated with the same WAN IP…

      Are we getting anywhere on this?

      Running 2.0-ALPHA, updated almost daily on
      Athlon 1.4Ghz, 768MB PC100, 3 NIC's (2x10/100, 1xGB), 20G HDD,
      Currently Dual-WAN (1 cable 6M/512K, 1 DSL 7M/768K), Single LAN
      Working on adding 1 WiFi WAN and 2 cellular (when we're home with our phones)

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

        Try the latest snapshot.

        https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/55bd0d738cc14358031e57fd14ccfd9064a5eded

        1 Reply Last reply Reply Quote 0
        • T Offline
          tekoholic
          last edited by

          Thank you, I appreciate seeing some progress on this.

          However, at this point, it seems to be further broken.  Currently, I've got 3 WAN's, all of which are DHCP, and each have their own respective subdomains with DynDNS (currently not used, while troubleshooting this) and OpenDNS/DNS-O-Matic.  After updating to newest snapshots, only OPT2 is able to update, but does so with THE WRONG IP.  I've no idea where the IP address it's been updated wih came from, but it surely isn't one that ANY of my interfaces holds…

          The others are coming back with the error (on the DNS-O-Matic site), "!yours".  This error seems, according to their site, to come from either of 2 problems:  1. Someone else already has that IP address registered with their hostname, or 2. The IP update is not being sent from it's own IP address.

          That said, it might be necessary, for multiwan setups, to make sure that a policy-based route is automatically created for each WAN IP to be updated via it's own gateway.  I'm not sure how to go about this, as the updates all go to the same host, from the same host...

          Running 2.0-ALPHA, updated almost daily on
          Athlon 1.4Ghz, 768MB PC100, 3 NIC's (2x10/100, 1xGB), 20G HDD,
          Currently Dual-WAN (1 cable 6M/512K, 1 DSL 7M/768K), Single LAN
          Working on adding 1 WiFi WAN and 2 cellular (when we're home with our phones)

          1 Reply Last reply Reply Quote 0
          • E Offline
            eri--
            last edited by

            Actually just today i fixed a problem with dyndns+dhcp setups.
            For the other cases i am not sure other that it needs more debugging!
            Try a new snapshot and report what you found.

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