On Friday 14 November 2008, Erik-Jan Elfferich wrote: > Well, yes, 192.168.129.0/24 but that didn't work. I changed it in ANY. > Now it works! > Changed it back to 192.168.129.0/24 rebooted and ... It's still working.
Hmm, it should not behave that way. I will have a look at the code and see if I can see why. > So FTP is going al right now, but I don't understand what went > wrong. There are a lot of people fighting FTP problems like this, so I > like to know what really went wrong. Then we can help people who use ftp > for other reasons, like Opensync for instance ;-) , with a little > paragraph in the readme. Well, technically that ftp server is not really designed for uses other than synchronisation (of course there's nothing stopping you from using it for other things :) Aside from the bug you seem to have experienced there is a note in the README for the OpenSync opie-sync plugin that mentions the need to change the Security settings. > Is there a log file on the Z where I can find information? Dmesg doesn't > give a clue. Is there a sort of security log? Opie doesn't log things to the system log. If you want, you can turn on debug logging, but in versions of Opie built without debug logging enabled you won't see as much. IMHO it is worth concentrating on fixing bugs, improving associated documentation and showing appropriate error messages to the user rather than suggesting users read some log file to determine what has gone wrong (although in this case we don't show an error to the user in case they are being portscanned/attacked, which is possible if the device is connected to some kind of public network). Cheers, Paul _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
