** Changed in: linux (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/89160
Title:
Cannot connect to router/server/proxy with bad TCP Wscale
implementation
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
I has been solved by me.
After checking my firewall I noticed it was complaining about a syn flood when
I was unable to connect to a website. In my setup at home this firewall is not
really needed so I turned it off. All the problems are gone since that moment.
So, obviously Ubuntu makes my
Still present in karmik alpha 2 live cd.
As said above, the problem is not in Linux/Ubuntu, but in some routers. However
for a novice, this is a big problem, difficult to understand, and is perceived
as a Linux/Ubuntu bug. A workaround would be very useful.
--
Cannot connect to
I have noticed this problem for a few months and finally tracked down
this bug report. Doing echo 4096 65536 65536
/proc/sys/net/ipv4/tcp_rmem did resolve it for me. Please let me know
if there is any thing else you need.
--
Cannot connect to router/server/proxy with bad TCP Wscale
I have had the same problem here.
I do not know when it started exactly (it wasn't the when I first installed
Ubuntu but suddenly some websites (like google maps) started to display half
maps. Then I was able to pinpoint to a problem with wireshark.
First I added the line
Well,
Having a second look it seems it is not completely gone (actually, the
https connection to this website still shows the checksum errors but at
least the problem is now not noticeable any more
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue
This bug still exists in Jaunty
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Lionel
Ok, please run this command from a Jaunty terminal:
apport-collect -p linux-image-2.6.28-11-generic 89160
Thanks in advance.
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification because you
Sergio unfortunately, apport-collect doesn't work behind a proxy
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The 18 month support period for Feisty Fawn 7.04 has reached it's end of
life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result
we are closing the linux-source-2.6.20 task. However, this will remain
open against the actively developed kernel. Thanks.
** Changed in:
This bug is not new and -from what i gather- stricty speaking it is not a
bug of linux (or Vista) it is a bug with cheap (read crappy) modems/routers,
such as my D-Link DSL-502T. It would be nice if they provided us with a
firmware upgrade that supports window scaling.
Ubuntu 8.04 LTS (Hardy)
I tried to use the Firestarter application as suggested above, and it
worked for me. Then, I saved its configuration files, purged
Firestarter, restarted my system, and started to execute the commands
from its /etc/firestarter/sysctl-tuning script in sequence, at each step
checking wget
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
This bug is not new and -from what i gather- stricty speaking it is not a
bug of linux (or Vista) it is a bug with cheap (read crappy) modems/routers,
such as my D-Link DSL-502T. It would be nice if they provided us with a
firmware upgrade that supports window scaling.
2008/8/20 Bug Watch Updater
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401435
Importance: Unknown
Status: Unknown
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification
** Changed in: linux (Debian)
Status: Unknown = New
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same problem running Vista Basic OS...Can not surf or use email after
Inside Windows installation with ADSL modem and router attached. Also on
Ubuntu boot some white screen stuff where it should be black. Acer AMD
Athalon with ATI graphics card.
--
Cannot connect to router/server/proxy with bad
Adding the lines
net.ipv4.tcp_wmem = 4096 16384 131072
net.ipv4.tcp_rmem = 4096 87380 174760
net.ipv4.tcp_window_scaling=0
and doing a sysctl -p
doesn't work for me.
Ubuntu 8.04, upgraded from previous release.
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
the error remains into ubuntu 8.04 amd64 2 year!!! with the same
shit! again to edit /etc/sysctl.conf
to include this line
net.ipv4.tcp_window_scaling=0. I´M SICK!
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You
Well, my problem was solved with a reset.
What I can say...
Follow in attachment the last email I sent.
** Attachment added: email-to-buffalo.txt
http://launchpadlibrarian.net/13831413/email-to-buffalo.txt
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
My problem was solved when I
edited /etc/sysctl.conf
and added the following two lines
net.ipv4.tcp_wmem = 4096 16384 131072
net.ipv4.tcp_rmem = 4096 87380 174760
This seems a little geeky, and I would hope that the Ubuntu developers
somehow address this issue in future releases. (It wasn't a
After configure kernel parameters as you had tell
sysctl -p
kernel.printk = 4 4 1 7
kernel.maps_protect = 1
fs.inotify.max_user_watches = 524288
vm.mmap_min_addr = 65536
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.tcp_wmem = 4096 16384 131072
net.ipv4.tcp_rmem =
Follow wireshark (ethereal) log files of a failed connection using wget to try
retrieve skydrive.live.com
Relevant frames: 1-42
(Follow in plain text and also a wireshark/tcpdump file to open with the
appropriate tools.)
Hope you can help me debug this network issue
$ cat
Follow wireshark (ethereal) log files of a failed connection using wget to try
retrieve skydrive.live.com
Relevant frames: 1-42
Follow also current ipv4 configs.
(Log files, follow in plain text and also in wireshark/tcpdump format to
open with the appropriate tools.)
Hope you can help me
The two lines below solved my problem. THANK YOU!
On Thu, Apr 17, 2008 at 11:58 PM, Jojo [EMAIL PROTECTED] wrote:
Please try
=
vi /etc/sysctl.conf
add the following two lines
net.ipv4.tcp_wmem = 4096 16384 131072
net.ipv4.tcp_rmem = 4096 87380 174760
save and reset
echo 0 /proc/sys/net/ipv4/tcp_window_scaling
OR
echo 4096 65536 65536 /proc/sys/net/ipv4/tcp_rmem
wcho 4096 65536 65536 /proc/sys/net/ipv4/tcp_wmem
OR
ip route add $THEIR_IP/32 via $MY_GATEWAY window 65535
OR
sudo iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS
Please try
=
vi /etc/sysctl.conf
add the following two lines
net.ipv4.tcp_wmem = 4096 16384 131072
net.ipv4.tcp_rmem = 4096 87380 174760
save and reset sysctl
sysctl -p
===
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
As discussed at Bug 209359, this bug also affects Hardy
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Confirmed
--
Cannot connect to
** Summary changed:
- cannot get an HTTP response from some sites
+ Cannot connect to router/server/proxy with bad TCP Wscale implementation
--
Cannot connect to router/server/proxy with bad TCP Wscale implementation
https://bugs.launchpad.net/bugs/89160
You received this bug notification
31 matches
Mail list logo
