Comments on: LinkSys NSLU2 (slug) http://blog.2sparrows.org/2006/02/17/linksys-nslu2-slug/ Wed, 08 Feb 2012 14:40:32 +0000 hourly 1 http://wordpress.com/ By: Sean Butler http://blog.2sparrows.org/2006/02/17/linksys-nslu2-slug/#comment-34 Tue, 21 Feb 2006 13:11:57 +0000 http://www.2sparrows.org/blog/?p=66#comment-34 The hardest part was getting permissions correct between the windows boxes, rsync, and the ftp server. Windows tends to chop off most of the bits of the unix permissions, and having a linux box allow ftp to get files w/o the right permissions is tough (impossible?). I tried all sorts of things including forcing the umask of rsync, chmod -R on the directories, changing the options on the rsync command, etc. What is really bad is I can’t remember right now what I did to get it all to work, since I went through so many iterations. I’m sure i can figure it out if/when you need the info.

The other thing that was hard was getting passive ftp to work. The slug sits behind a firewall, and I had port forwarding for 21 and 45000 – 45100 set, and then set proftpd to use 45000-45100 to be the only passive ports it would use. It would work for a few transactions per session, and then fail. When I put the slug on the dmz it worked fine, or if I turned off passive on the ftp client it worked fine. I finally changed the passive ports from 45000 – 100 to some other range on both the ftp daemon and the firewall, and it started working.

The slug is the rsync server (daemon).

]]> By: breeves_2000 http://blog.2sparrows.org/2006/02/17/linksys-nslu2-slug/#comment-33 Fri, 17 Feb 2006 23:46:21 +0000 http://www.2sparrows.org/blog/?p=66#comment-33 That’s AWESOME!!! So you got all that set up the right way now eh? What was the hardest to configure? The SLUG is acting as the RSYNC server and the other devices are RSYNC clients? Very COOL! I’ll be picking your brain for config tips later.

]]>