Network timeouts on suse 9.3 after upgrade from 9.1

I upgraded to from suse 9.1 to 9.3 and after that I keep getting
network timeouts when accessing websites which inturn have referring
websites.
Example: when accessing cnn.com or similar sites which inturn refer to
the ad websites like ar.atwola.com, I get constant timeouts to these
referred sites. Consequently the pages dont complete downloading.
Reinstalled and reconfigured dhcp, network drivers, turned off ipv6,
manually restarted networking etc., but problem persists. Checked
routing tables, network config. Websites which do not refer to other
websites load fine and fast !
Same hardware when booted with windows works fine.

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed). com>,
(E-Mail Removed) wrote:

>I upgraded to from suse 9.1 to 9.3 and after that I keep getting
>network timeouts when accessing websites which inturn have referring
>websites.

Something you changed in the browser setup, though I suppose it could
possibly be a firewall configuration.

>Reinstalled and reconfigured dhcp, network drivers, turned off ipv6,
>manually restarted networking etc., but problem persists.

Of course - it's HIGHLY unlikely to have anything to do with those.

>Checked routing tables, network config. Websites which do not refer to
>other websites load fine and fast !

Try a different browser - most distributions supply at least four. Also
remember that the 'web' is only one small part of the Internet, and you
have many other tools and services you could be using. The fact that you
can connect to some sites rules out networking, hardware, and basic
operation of the O/S.

>Same hardware when booted with windows works fine.

And this might be relevant exactly how?

Old guy

If windows is ok, means that the network hardware is ok. Worked fine
with suse 9.1
Changed browser setting to disable ipv6, disabled suse 9.3 ipv6, but
network timeouts persist.
tcpdump not showing much - did not do a extensive troubleshooting here.
It is as if arbitrarily, the network just shuts down for particular
hosts, websites.

-A

Moe Trin wrote:
> In the Usenet newsgroup comp.os.linux.networking, in article
> <(E-Mail Removed). com>,
> (E-Mail Removed) wrote:
>
> >I upgraded to from suse 9.1 to 9.3 and after that I keep getting
> >network timeouts when accessing websites which inturn have referring
> >websites.
>
> Something you changed in the browser setup, though I suppose it could
> possibly be a firewall configuration.
>
> >Reinstalled and reconfigured dhcp, network drivers, turned off ipv6,
> >manually restarted networking etc., but problem persists.
>
> Of course - it's HIGHLY unlikely to have anything to do with those.
>
> >Checked routing tables, network config. Websites which do not refer to
> >other websites load fine and fast !
>
> Try a different browser - most distributions supply at least four. Also
> remember that the 'web' is only one small part of the Internet, and you
> have many other tools and services you could be using. The fact that you
> can connect to some sites rules out networking, hardware, and basic
> operation of the O/S.
>
> >Same hardware when booted with windows works fine.
>
> And this might be relevant exactly how?
>
> Old guy

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

>If windows is ok, means that the network hardware is ok. Worked fine
>with suse 9.1

In your original post you wrote:

]Example: when accessing cnn.com or similar sites which inturn refer to
]the ad websites like ar.atwola.com, I get constant timeouts to these
]referred sites.

The fact that you could access cnn.com, AND THEN FAILED to get to the
referred sites says it's not a hardware problem - nor a basic kernel or
networking problem. Were there hardware/kernel/networking problems, you
wouldn't get to the original site in the first place.

>Changed browser setting to disable ipv6, disabled suse 9.3 ipv6, but
>network timeouts persist.

Change the browser

>tcpdump not showing much - did not do a extensive troubleshooting here.

Do you see the three way handshake to the referred sites? Remember to
use the -n option to tcpdump to avoid confusion. You may need to specify
the interface (-i option) if you have more than one.

>It is as if arbitrarily, the network just shuts down for particular
>hosts, websites.

Networking doesn't work that way. Your firewall could be screwing things
up (blocking ICMP for example), but this would show up in the tcpdump
output. This would also show ECN problems, but that problem started with
a 2.4.x kernel, and should be uncommon by now. Ad sites tend to have
servers locate around the world, and they use 'pings' to see which
server is "nearest" to you, so they can deliver the garbage to you
faster. Block pings, and they may sulk in the corner. But tcpdump will
show this problem.

Old guy