Your message dated Sun, 26 Aug 2007 22:27:00 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fwd: Bug#438686: azureus: Azureus not honouring mtu setting in
options
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: azureus
Version: 2.5.0.4-1
Severity: important
I have setup my local lan to allow large size packet, the mtu for the local
interface is set to 9100
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 9100 qdisc pfifo_fast qlen 10000
link/ether 00:30:1b:b8:93:3d brd ff:ff:ff:ff:ff:ff
my routing though is setup for mtu 1500
192.168.11.1 dev eth0 scope link mtu 1500
192.168.11.10 dev eth0 scope link mtu 9100
192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.11.11 mtu 1500
default via 192.168.11.1 dev eth0 mtu 1500
I have set in the options for azureus
mtu=1500
but when i tcpdump on my firewall i notice that azereus is using 9100 as a mss
08:44:28.110700 IP 192.168.11.11.42461 > 85.49.238.247.6881: SWE
2171850278:2171850278(0) win 18120 <mss 9060,sackOK,timestamp 1352887192
+0,nop,wscale 6>
08:44:28.110759 IP 192.168.11.11.42461 > 194.144.78.125.62732: SWE
2171134690:2171134690(0) win 18120 <mss 9060,sackOK,timestamp 1352887192
+0,nop,wscale 6>
08:44:28.110799 IP 192.168.11.11.42461 > 203.144.160.12.16882: SWE
2182956894:2182956894(0) win 18120 <mss 9060,sackOK,timestamp 1352887192
+0,nop,wscale 6>
I can work around this by setting the mss in routing, but azureus should be
setting it from its options page!
Alex
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (100, 'unstable'), (50,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages azureus depends on:
ii gij [java-virtual-machine] 4:4.1.1-15 The GNU Java bytecode interpreter
ii gij-4.1 [java2-runtime] 4.1.1-20 The GNU Java bytecode interpreter
ii java-gcj-compat 1.0.65-10 Java runtime environment using GIJ
ii libcommons-cli-java 1.0-8 API for working with the command l
ii liblog4j1.2-java 1.2.13-3 Logging library for java
ii libseda-java 3.0-3 the Staged Event-Driven Architectu
ii libswt-gtk-3.2-java 3.2.1-5 Standard Widget Toolkit for GTK Ja
ii sun-java5-jre [java2-runtime] 1.5.0-11-1 Sun Java(TM) Runtime Environment (
ii sun-java6-jre [java2-runtime] 6-00-2 Sun Java(TM) Runtime Environment (
azureus recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
package azureus
tag 438686 wontfix
thanks
Closing this bug as it seems beyond the control of the application software.
Cheers,
Shaun
On 8/26/07, Alon Rohter <[EMAIL PROTECTED]> wrote:
> We dont actually have the ability to set real tcp MTU/MSS in our java
> code. The config setting is just a suggestion to Az as to how it should
> try and group messages together for sending out to the OS (i.e. in
> groups of MSS-sized bytes). But at the end of the day, it's up to the
> OS tcp stack to determine final wire output, which looks like it's being
> combined into your large mtu in your case.
>
> -Alon
--- End Message ---
