Your message dated Sat, 28 Oct 2006 12:17:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line It's not related to fiaif
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fiaif
Version: 1.20.1-2
Severity: critical
Justification: breaks unrelated software
With fiaif, outgoing TCP connections will typically stall
after a megabyte of data transfer. I run the 2.6.17-2 kernel,
running Debian testing distribution.
My Debian box is behind a SpeedTouch ADSL router, connected to
British Telecom via PlusNet.
A typical SCP run is as follows:
$ time scp foo mint.phon.ox.ac.uk:/tmp
foo 36% 1140KB 0.0KB/s - stalled -
real 2m0.535s
user 0m0.204s
sys 0m0.056s
$
Now, I can prevent stalls by running
$ sudo ifconfig eth0 mtu 576
but, interestingly, not with either
$ sudo ifconfig eth0 mtu 1450
gpk:gpk$ sudo ifconfig eth0 mtu 1400
or
$ sudo ifconfig eth0 mtu 1400
I can also prevent stalls by throttling the data rate via the following
lines in /etc/fiaif/zone.ext:
TC_ENABLE=1
TC_TYPE=HTB
TC_DOWNLINK=2000
TC_UPLINK=230
(My downlink speed is slightly above 2Mbit/s and my upload speed is
perhaps 260kbit/s.)
I thought at first it was related to Path MTU discovery,
and the problem might be in fiaif's configuration. Fiaif
seems to block most ICMP packets, and path MTU discovery
requires the ICMP datagram too big message.
So, I tried to turn that on as follows, but got no improvement:
INPUT[1]="ACCEPT icmp ALL 0.0.0.0/0=>0.0.0.0/0"
(in zone.ext).
Anyhow, somewhere, either in fiaif, the kernel, iptables,
my ADSL router, or perhaps some local configuration I've forgotten
about, there's a problem.
-- Package-specific info:
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages fiaif depends on:
ii bash 3.1-5 The GNU Bourne Again SHell
ii coreutils 5.97-5 The GNU core utilities
ii cron 3.0pl1-97 management of regular background p
ii debconf [debconf-2.0] 1.5.6 Debian configuration management sy
ii debianutils 2.17 Miscellaneous utilities specific t
ii dnsutils 1:9.3.2-P1-2 Clients provided with BIND
ii grep 2.5.1.ds2-5 GNU grep, egrep and fgrep
ii iptables 1.3.5.0debian1-1 Linux kernel 2.4+ iptables adminis
ii logtail 1.2.47 Print log file lines that have not
ii net-tools 1.60-17 The NET-3 networking toolkit
ii sed 4.1.5-1 The GNU sed stream editor
ii wget 1.10.2-2 retrieves files from the web
fiaif recommends no packages.
-- debconf information:
* fiaif/cron_logfile:
* fiaif/warning:
* fiaif/enable_cron: true
* fiaif/enable_initd: true
--- End Message ---
--- Begin Message ---
Sorry. I've been able to reproduce the same stalling problem
when fiaif is turned off. It seems to stall more often and
more easily and faster with fiaif, but the problem does not
seem to be caused by fiaif.
--- End Message ---
