NTP not updating - DDWRT V24 Mini - Blocked on L Port 2049

Discussion in 'DD-WRT Firmware' started by rbngan, Sep 8, 2008.

  1. rbngan

    rbngan LI Guru Member

    I have a strange thing that I can't figure out. I've search several hours and have not have had any luck.

    I have several router that are set for updating their time. Two are running Thibor15c firmware, two with DDWRT (One has Mini V24, the other Micro V23). they are all set up on a WDS with Tibor15c as the backbone. All of them execpt the DDWRT Mini V24 is updating the NTP correctly.

    Problem: WallWatcher shows that the NTP request from the DDWRTMiniv24 is being blocked on L Port 2054, 2055 or 2049. The NTP is set to "clock.via.net".

    I also tried the following NTP's
    time.nist.gov - blocked is 2049.
    ntp.nasa.gov - blocked on L Port 2049
    time-b.nist.gov - blocked on L Port 2049
    time-a.nist.gov - blocked on L Port 2049

    The DDWRTMicro V23 is using "clock.via.net" and it is not being blocked, but the L prot is 3073. I don't see any settings, to adjust. Not sure why one is being blocked and the other is not.

    My servers are using time.nist.gov and they are not being blocked.

    Any help would be appreciated. (FYI - Access to these routers are only through remote. I will be on site in 2 weeks, but looking for solution that I can complete remotely).
  2. HennieM

    HennieM Network Guru Member

    What is an "L port"?

    Where exactly is this port being blocked - on which device/node? If it's being blocked on the DDWRTMiniv24 itself, it means you have a firewall rule that is either preventing the NTP protocol or the relevant ports from going out of that router; i.e. you may have an OUTPUT rule, or a FORWARD rule (or may even a PREROUTING rule) that's not allowing the request NTP through.
  3. rbngan

    rbngan LI Guru Member

    L Port - I think it means Listening port as reported by WallWatcher.

    HennieM thank you for getting my head out of the sand:redface:. I knew that my paranoia of unused IPs gaining access to the network got the best of me.

    I never thought the request was being block from going out. I though it was stopped from coming in (on the listening port). I have my network locked up by having the backbone WDS router blocking all IPs not assigned to a computer or allowed to be assigned by the DCHP. Well when I add a new device I have to remember to remove that new IP from the restrictive list. This would have been one of those time I wish I had a check list for "Adding device to Network" so I would not have missed that. I will put that on my to do list and get right to it.

    Thanks again for getting me thinking. The router picked up its time and is running fine.:smile:
  4. HennieM

    HennieM Network Guru Member

    Happy you got sorted.
  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