search for: web100

...uld really make my life easier. This is important to me because I am not easily able to control which tftp server the DHCP server points to. I could, however, setup my own tftp server (for example, tftpd-hpa) on a different machine that would be right. I have gotten my machine (Dell PowerApp Web100) to grab pxelinux off the network, and then pxelinux complains about not having tsize, which makes me think that the tftp server that dhcp is pointing to sucks. Any suggestions / help appreciated. Thanks, Erik @ columbia.edu

Using stock OpenSSH 4.7 I found different behavior when trying to specify the use of the 'none' cipher depending on the command line option nomenclature. This is under linux 2.6.19-web100 using -ocipher=none [root at delta openssh-4.7p1-hpnv19]# /home/rapier/ssh47/bin/scp -S /home/rapier/ssh47/bin/ssh -ocipher=none -P 2222 ~rapier/2gb rapier at localhost:/dev/null rapier at localhost's password: 2gb 3% 74MB 32.7MB/s 01:00 ETA using -cnone [root at delta openssh-...

...de (which Dan Y. repaired via rsyncd.conf, and which was later assisted by installing a recent Linux that allowed send-buffer-autotuning), *and* 2. Too-small TCP receive-buffer on the client-side. I couldn't see how to enlarge TCP buffers from the rsync client-side. By using a web100-enabled client machine (web100.org), we managed to upsize the TCP receive buffers (and went from 20Mbps to ~400Mbps). This by grabbing the running rsync process with a web100 tool, and manually changing the buffers on-the-fly. But the process would be a *lot* simpler if the rsync tool...

Hi, There has been some recent work to improve the speed of the Message Authentication Codes (MACs) that are used in OpenSSH. The first improvement is a change from Markus Friedl to reuse the MAC context, rather than reinitialising it for every packet. This saves two calls to the underlying hash function (e.g. SHA1) for each packet. My tests found that this yielded at 12-16% speedup for bulk

We see absolutely dismal performance from Canberra to Perth via Aarnet or Grangenet (gig connections across the country). With standard rsync on a tuned tcp stack, we see about 700k/s. I started playing with the --sockopts and have increased the performance to 1.4M/s which is better, but still way off the pace. There are similar patches for ssh at

Hi All. OpenSSH 4.7 is preparing for release so we are asking for any interested folks to please test a snapshot. The main changes are: * sshd(8) in new installations defaults to SSH Protocol 2 only. Existing installations are unchanged. * The SSH channel window size has been increased, which improves performance on high-BDP networks. * ssh(1) and sshd(8) now preserve MAC