dyndns issues with 1.26?

Discussion in 'Tomato Firmware' started by garretwilson, Nov 28, 2009.

  1. garretwilson

    garretwilson Addicted to LI Member

    I have remotely accessed my computer for almost two years using dyndns and port forwarding with tomato. In the past I have updated my firmware over Windows Remote Desktop (uploading from the remote computer, locally connected to the router by Ethernet).

    Today I updated Tomato to 1.26 over remote desktop. After updating, I lost connection (as expected, as the router rebooted). But I could not get back in to the remote computer, nor could I access the router remotely over HTTPS.

    When I got home (luckily I wasn't in another country), the only thing that looks different is that the dyndns.org update failed with the following message:

    Friday, November 27, 2009 4:22:04 PM:
    Unknown error (-1).
    (1/3: Automatically retrying in 16 minutes)​

    I can remote desktop in using the IP address---now that I'm actually at the router and know what it is!

    So is dyndns down, or does Tomato 1.26 have issues updating dyndns? Surely after all these months using dyndns, it wouldn't coincidentally go down at the moment I upgraded to 1.26, would it?

    There are no error messages in the logs.

    Thanks for any help.
  2. TexasFlood

    TexasFlood Network Guru Member

    DynDNS isn't down for me, I just forced an update which worked (V1.25.8515 RAF ND USB Thor MOD). It's not running 1.26 yet and I can't update it right now so can't help any more for now.
  3. teddy_bear

    teddy_bear Network Guru Member

    So, does HTTPS connection to the router - from WAN or LAN - work or not? And DynDNS is configured to use https? Then I believe the problem is in MatrixSSL update to version 1.8.8 in Tomato 1.26.

    When I updated MatrixSSL in my mod from 1.8.6 to 1.8.7, it broke DDNS updates via ssl connection, as well as ssl support for Tomato web-server. I could not figure out with reasonable efforts what is it in MatrixSSL code that causes the issue, so I just downgraded it back to 1.8.6.
  4. Toastman

    Toastman Super Moderator Staff Member Member

    Just checked with my WRT54GL and 1.26 working normally with DYNDNS.org normal connection, HTTPS is indeed broken.
  5. garretwilson

    garretwilson Addicted to LI Member

    I just downgraded to 1.25 and things work again.

    This is scary. Good thing I didn't upgrade my firmware when I was out of the country, or I would have been hosed.
  6. occamsrazor

    occamsrazor Network Guru Member

    Just to clarify - is https broken only for sending updates to dyndns's servers, or it's broken for https access to Tomato remote web administration? If so that's a pretty big problem I'd think. Thanks...
  7. garretwilson

    garretwilson Addicted to LI Member

    I cannot say---I didn't test an HTTPS connection via direct IP address to the web administration page before downgrading.

    If you care about your dyndns password being sent over the clear (you want someone logging in and pointing your requests somewhere else after they snatch your password?), I'd say it's a pretty big problem either way.
  8. Morac

    Morac Network Guru Member

    Upgrading router firmware when you don't have physical access to the router is never a good idea, for this very reason.
  9. j.m.

    j.m. Network Guru Member

    DNS-O-Matic updating is also broken in 1.26--presumably it uses https as well.
  10. garretwilson

    garretwilson Addicted to LI Member

    May I suggest regression tests? :)
  11. PeterT

    PeterT Network Guru Member

    Version 1.27 is out that has one fix

    Fix DDNS "-1" error when service used HTTPS.
  12. garretwilson

    garretwilson Addicted to LI Member

    Version 1.27 fixed the DynDNS problem for me. Thanks.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice