After spending few hours (not intensive work, I was doing also other stuff) with duplicty and dropbear, I finally got the idea to enter magic words to Google to find solution.
Those words were excitingly "openwrt sftp" where first link points to sftp with Dropbear howto.
Next time I should start with looking for documentation, most likely somebody already had same issue…
The OpenWrt toy is doing more and more work for me. I just connected USB/LPT adaptor and my printer and setup printing in few seconds. Hardest and longest part was to follow howto and click in windows on correct buttons :-).
Cups also speaks well with this device, so I'm definitely convinced it was a good buy.
Last thing which was missing was to add new router to monitoring using Munin which I use for this purpose. The only reasonable way seemed to be SNMP so I installed it to OpenWrt.
And the rest was incredibly simple! Just add snmp host to munin.conf:
[openwrt.lan]
address localhost
And run SNMP discovery on monitoring host (the one which runs munin-node):
munin-node-configure-snmp openwrt.lan | sh
It automatically creates symlinks for everything it detects (network interfaces, load, disk space and users) and only remaining thing is to restart munin-node.
I'm starting to love this distribution. After few hours I've setup everything I needed including OpenVPN to other locations. Most of things were pretty easy to configure and basic settings can done as well over web interface.
The only thing I don't understand is that for some reason I don't see WAN IP address settiongs (I'm using static IP) and same way I lost WEP/WPA key configuration. Those parts of dialog simply do not appear on page while HTML is still there. I didn't yet have time to debug, but maybe later.
Today my new toy arrived. I originally wanted to stay with ASUS firmware for a while, but I started to hate it too quickly so OpenWrt was installed just half an hour after unpacking the device :-).
Installation via tftp as described in documentation went smoothly, now I'm looking at web interface and finding possibilities of this box.
I desperately need quiet wireless router. Currently old Pentium does the work, but it's too noisy and power consuming to be still on. The problem is that I use it for another things as backup, file and print server and those things can't be easilly moved to some generic router.
I thought about buying some VIA EPIA board with fanless power supply or some router supported by OpenWRT which could be later expanded to do at least part of jobs currently done by "router".
At the end I've chosen ASUS WL-500g Deluxe which is reported to be fully supported by OpenWRT. For now it will live with generic firmware, later I will start to experiment with OpenWRT to get out of this hardware as much as possible.
If you want to know more about world domination, kernel myths and how to contribute to Linux kernel, Myths, Lies, and Truths about the Linux kernel written by Greg Kroah-Hartman is good starting point for you. There is not much new information, but nice summary about various aspects of Linux kernel.
When I today first saw this, I really liked that. I saw various useless USB toys, but this one is the best of them. And it even works fine from Linux!
I'm talking about USB Misille Launcher. You can control it using keyboard or even combine it with webcam and use motion together with small script to automatically aim it (no auto fire yet :-)).
Yesterday Google released beta version of Google Earth which runs natively on Linux. As it is great toy I wanted to immediatelly test it :-). However it ran damn slow and libgl was complaining about wrong structure sizes:
ERROR! sizeof(I830DRIRec) does not match passed size from device driver
After some Googling I found bug #359328 which tells to use CVS snapshot of Mesa from experimental. Any yay, it works then. Now back to work let's contiue with playing later.
I'm sorry for outage of this server. It was caused by short power down in serverhouse, which lead to server reboot. Unfortunately network interface didn't reset properly and thus computer was unreachable.
Everything looked fine, except it was not able to enable link intreface. PHY was somehow confused and it reported different state than usual (0x786d vs 0x7869). I will try investigate details later to avoid repeating this.