1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

NAS time problem with this firmware

Discussion in 'HyperWRT Firmware' started by robertw, Aug 1, 2006.

  1. robertw

    robertw LI Guru Member

    Hi all. I flashed my new WRTSL54GS with the Thibor 15c firmware. It's working well for me, except the time set on files created on the attached USB drive. I formated (claimed) the drive, set the time zone, etc, etc. The time setting on any files created / modified is off by four hours. I'm in the US Eastern time zone. btw -- the time on the status page is correct, but when i telnet into the router it shows UTC. TIA!
     
  2. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    Your post was moved to its own thread.
     
  3. Thibor

    Thibor Super Moderator Staff Member Member

    this is a samba bug, it's already been reported and will be fixed.
     
  4. robertw

    robertw LI Guru Member

    Thanks to both you.
     
  5. plugh

    plugh Network Guru Member

    It's a bit more complicated than being a samba bug. There are a set of interactions at play, including what looks to me like a problem with the ntpclient related changes tofu added (also incorporated in thibor).

    For those interested, I posted a partial analysis of the problem in the hyperwrt forum. I'm kind of waiting to see the sources for latest linksys release for the sl54 (beta available in downloads section) before I dig into it further. I've created and am using a hack that gets things working with fat32 disks and the tofu ntp code, but it is NOT a 'correct' fix.

    The 'correct' setup would be for the sl54 clock to be set to gmt via ntpclient and both the kernel sys_tz cells and the tz environment variables (or a tz file) be defined with the appropriate local offsets. If this were done, both on-disk timestamps AND remote smb timestamps would be correct for all file system types.

    The current linksys sl54 code's time handling in some respects is more correct than tofu/thibor but has its own set of problems with the ntpclient. If the new code base addresses *those* problems, it may be appropriate to undo the tofu ntpclient changes and then add in the tz variable "stuff".

    Pardon the pun, but "Time will tell"
     
  6. robertw

    robertw LI Guru Member

    I noticed the TZ missing telneted into the router. the stock firmware (both what came on the router and that downloadable from Linksys) don't set the time at all. the router always goes back to 12/31/69. The Thibor firmware is very nice, adds options to port forwarding, reserved dchp, etc. but ... the real reason i tried it was for the usb disk support. is there any firmware out there that will properly support the disk? it's currently formated fat32, but i don't care what the format is. is was previously connected to a XP Pro SP2 machine formated as NTFS. I have a Mandrake box that i will reformat to either Fedora Core 5 or Ubuntu in the next few weeks. the usb disk is for backing up. since the speed isn't so hot, i'm using syncback to copy only changed files. needless to say, that's not working at the moment.
     
  7. plugh

    plugh Network Guru Member

    >>I noticed the TZ missing telneted into the router.

    Yes. tofu (thibor) attempted to address this; see the description of the "tz" NVRAM variable on the tofu/thibor websites. Specifically,
    -set the time zone in the GUI to GMT+0 and disable daylight savings time.
    -set the NVRAN "tz" variable to a gnu timezone string
    Problem is, this doesn't propogate to all processes, and the sys_tz kernel cell used by the fat fs driver isn't initialized by their code.

    >>the stock firmware (both what came on the router and that downloadable from Linksys) don't set the time at all. the router always goes back to 12/31/69.

    Yes - same for me, though I have not tested the V2.02.1 linksys beta posted here
    http://www.linksysinfo.org/portal/forums/downloads.php?do=file&id=5
    My hope is that linksys will have corrected THAT problem in THEIR code, which could then serve as the basis for an updated Hyperwrt release.

    >>The Thibor firmware is very nice, adds options to port forwarding, reserved dchp, etc. but ... the real reason i tried it was for the usb disk support. is there any firmware out there that will properly support the disk?

    The beta is an unknown - try it out and report your findings. Thibor 15c has fat32 size fixes but timestamp handling is as discussed above and in my post here
    http://www.hyperwrt.org/forum/viewtopic.php?id=1756

    >>it's currently formated fat32, but i don't care what the format is. is was previously connected to a XP Pro SP2 machine formated as NTFS. I have a Mandrake box that i will reformat to either Fedora Core 5 or Ubuntu in the next few weeks.

    You could try ext2/ext3 in conjunction with the nvram variable method. On-disk timestamps with those filesystems are supposed to be UTC and do not use the sys_tz kernel cell; thus setting the GUI to GMT+0 with DST off gets that part right, and perhaps the tz variable will catch other parts in that config. (I have not tried this as I also use fat32 for portability.)

    >>the usb disk is for backing up. since the speed isn't so hot, i'm using syncback to copy only changed files. needless to say, that's not working at the moment.

    Yeah, I'm doing something similar, but with xp 'synctoy' utility (though I'm thinking of trying out syncback). However, I found I ALSO needed to twiddle some OTHER samba parameters (in addition to tz offset issues) to get it working - and I had to create my own firmware image to do it.

    Bottom line is it is going to take some time and effort and experimentation to get timestamp handling "right" in Hyperwrt. You could also check out Openwrt firmware if you are comfortable with linux command line, but I don't know what (if any) issues there may be with that firmware.
     

Share This Page