Re: Only some websites will open - Ubuntu

On Jun 8, 6:51 pm, The Natural Philosopher wrote:
> kubi...@gmail.com wrote:
> > Just to add a little more to this, when I submitted my bug I got a
> > message saying it was a dupe which lead me to this page
>
> >https://bugs.launchpad.net/ubuntu/+s....17/+bug/59331
>
> Well I am pleased that the discussion finally narrowed it down to what
> it was likely to be, and it turned out it was a known problem with a
> simple enough workaround.

It has been 10 days since I first posted this problem on this group,
and I finally have a solution. I don't know exactly what the cause
was, but I am so relieved to have things working.

I was contacted by another person with the same networking hardware as
myself, a Linksys RV082, who upgraded the firmware from v1.3.2 to
v1.3.5. It took 3 minutes, and everything works now.

I still don't know if this was an issue with the router, or Kubuntu
7.04, but it is resolved. If I should submit this anywhere to help
people who run into this same issue, please let me know where.

I'd like to thank everyone who suggested different solutions to me.
You have all been a great help. Thank you!

Big Dave Smith wrote:
> On Jun 8, 6:51 pm, The Natural Philosopher wrote:
>> kubi...@gmail.com wrote:
>>> Just to add a little more to this, when I submitted my bug I got a
>>> message saying it was a dupe which lead me to this page
>>> https://bugs.launchpad.net/ubuntu/+s....17/+bug/59331
>> Well I am pleased that the discussion finally narrowed it down to what
>> it was likely to be, and it turned out it was a known problem with a
>> simple enough workaround.
>
> It has been 10 days since I first posted this problem on this group,
> and I finally have a solution. I don't know exactly what the cause
> was, but I am so relieved to have things working.
>
> I was contacted by another person with the same networking hardware as
> myself, a Linksys RV082, who upgraded the firmware from v1.3.2 to
> v1.3.5. It took 3 minutes, and everything works now.
>
> I still don't know if this was an issue with the router, or Kubuntu
> 7.04, but it is resolved. If I should submit this anywhere to help
> people who run into this same issue, please let me know where.
>
> I'd like to thank everyone who suggested different solutions to me.
> You have all been a great help. Thank you!
>
It's an issue between the 2.6.17+ kernels and SOME routers that were
never designed with huge TCP windows in mind.

An INTEROPerability issue.

Em Sábado, 9 de Junho de 2007 10:16, The Natural Philosopher escreveu:

>> I still don't know if this was an issue with the router, or Kubuntu
>> 7.04, but it is resolved. If I should submit this anywhere to help
>> people who run into this same issue, please let me know where.
>>
>> I'd like to thank everyone who suggested different solutions to me.
>> You have all been a great help. Thank you!
>>
> It's an issue between the 2.6.17+ kernels and SOME routers that were
> never designed with huge TCP windows in mind.
>
> An INTEROPerability issue.

It goes beyond that... i'm not using a router and yet i can only open

http://www.everymac.com/

if i switch window_scaling to 0

could cable modems be affected to?

ArameFarpado wrote:
> Em Sábado, 9 de Junho de 2007 10:16, The Natural Philosopher escreveu:
>
>>> I still don't know if this was an issue with the router, or Kubuntu
>>> 7.04, but it is resolved. If I should submit this anywhere to help
>>> people who run into this same issue, please let me know where.
>>>
>>> I'd like to thank everyone who suggested different solutions to me.
>>> You have all been a great help. Thank you!
>>>
>> It's an issue between the 2.6.17+ kernels and SOME routers that were
>> never designed with huge TCP windows in mind.
>>
>> An INTEROPerability issue.
>
> It goes beyond that... i'm not using a router and yet i can only open
>
> http://www.everymac.com/
>
> if i switch window_scaling to 0
>
> could cable modems be affected to?
>
>
>
You are using a router. Probably up to 20-30 of them - every time you
try and contact any site on the Internet..


The point being that not all of them are under your control..;-)

>>echo 0 > /proc/sys/net/ipv4/tcp_default_win_scale

I did this to my router (linux box).

echo 0 > /proc/sys/net/ipv4/tcp_window_scaling

And now I can access tracfone with a normal 576 mtu. Maybe it was the
window scaling that was the issue, or maybe tracfone.com fixed something
on their end after I emailed webmaster-at-tracfone.com about my issue/
resolution. I guess I'll add that to my boot scripts.

Shadow_7 wrote:
>>> echo 0 > /proc/sys/net/ipv4/tcp_default_win_scale
>
> I did this to my router (linux box).
>
> echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
>
> And now I can access tracfone with a normal 576 mtu. Maybe it was the
> window scaling that was the issue, or maybe tracfone.com fixed something
> on their end after I emailed webmaster-at-tracfone.com about my issue/
> resolution. I guess I'll add that to my boot scripts.

No need - adjust the relevant config files instead,.

>> I did this to my router (linux box).
>>
>> echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
>
> No need - adjust the relevant config files instead,.

If I did that, then I might not remember what I changed and where. And
if I want to change it back, if it's in a custom boot script, I can just
comment out the line that changes it. And if I want to setup another
box, I can just ftp the custom script to that box. Sure, I could just
change the conf, but my personal preferences tend towards other methods.

Shadow_7 wrote:
>>> I did this to my router (linux box).
>>>
>>> echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
>> No need - adjust the relevant config files instead,.
>
> If I did that, then I might not remember what I changed and where. And
> if I want to change it back, if it's in a custom boot script, I can just
> comment out the line that changes it. And if I want to setup another
> box, I can just ftp the custom script to that box. Sure, I could just
> change the conf, but my personal preferences tend towards other methods.

Well haven;t you heard of renaming your previous config file to
config.old when you change it, and leaving a comment in the new one?
Also, you won't want to change it till someone fixes the kernel
behaviour that causes the problem: That will be when you upgrade the
kernel next time. That will almost certainly wipe out your change anyway.