I just upgraded to 3.9 yesterday and today I am having
severe network problems. This has been happening for the
past week, but is now much worse. Browser requests take forever
to complete, I can't ping verizon.com, traceroute doesn't
work through the new verizon dsl modem which assigns
a local address of 192.168.1.47 to my computer. The
modem has address 192.168.1.1. Here is some sample console
log showing the ping and traceroute problems.
I called Verizon technical support, but it is useless.
Any ideas about how to fix this?

Thanks,
Dave Feustel

/home/daf}ping mindspring.com
PING mindspring.com (207.69.189.28): 56 data bytes
64 bytes from 207.69.189.28: icmp_seq=0 ttl=246 time=80.915 ms
64 bytes from 207.69.189.28: icmp_seq=1 ttl=246 time=81.187 ms
64 bytes from 207.69.189.28: icmp_seq=2 ttl=246 time=80.871 ms
64 bytes from 207.69.189.28: icmp_seq=3 ttl=246 time=83.075 ms
64 bytes from 207.69.189.28: icmp_seq=4 ttl=246 time=82.433 ms
64 bytes from 207.69.189.28: icmp_seq=5 ttl=246 time=82.232 ms
64 bytes from 207.69.189.28: icmp_seq=6 ttl=246 time=81.964 ms
mindspring.com ping statistics
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 80.871/81.811/83.075/0.780 ms
/home/daf}traceroute mindspring.com
traceroute: Warning: mindspring.com has multiple addresses; using
207.69.189.28
traceroute to mindspring.com (207.69.189.28), 64 hops max, 40 byte packets
1 dslrouter (192.168.1.1) 0.632 ms 0.601 ms 0.464 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 smtpsvc8.mindspring.com (207.69.189.28) 79.695 ms * 105.213 ms
/home/daf}traceroute verizon.com
traceroute to verizon.com (192.76.85.245), 64 hops max, 40 byte packets
1 dslrouter (192.168.1.1) 0.602 ms 0.555 ms 0.483 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
^C
/home/daf}

/home/daf}ping verizon.com
PING verizon.com (192.76.85.245): 56 data bytes
verizon.com ping statistics
170 packets transmitted, 0 packets received, 100.0% packet loss

Sunday 07 May 2006 10:28, Jason Dixon wrote:
May 7, 2006, at 9:21 AM, dave feustel wrote:
I just upgraded to 3.9 yesterday and today I am having
severe network problems. This has been happening for the
past week, but is now much worse. Browser requests take forever
to complete, I can't ping verizon.com, traceroute doesn't
work through the new verizon dsl modem which assigns
a local address of 192.168.1.47 to my computer. The
modem has address 192.168.1.1. Here is some sample console
log showing the ping and traceroute problems.
I called Verizon technical support, but it is useless.
Any ideas about how to fix this?

1) Your ping to mindspring.com succeeds.
2) Your traceroutes to verizon.com and mindspring.com fail. These
are being blocked by your DSL modem.
3) Pings to verizon.com are being filtered by Verizon.

I wondered about this.

So where are the "severe network problems" you allude to?

Konqueror is unusable this morning because almost no web accesses
other than those to my local webpages are completing.

And why does your email suggest any of this is related to BSD?

As I mentioned, while I was having slow response in Konqueror on 3.8 last
week, the response times have become MUCH worse in the last three days, which
is roughly the time that I have had 3.9 installed. I did not mean to suggest
that BSD is causing these delays. The length of time it takes to get no
new messages from verizon mail server suggests strongly that it is a problem
with the verizon network. (I *am* having a number of problems with kde
3.5.1, but that is not an BSD issue). I was looking for either 'Me too'
or 'No problem here' responses from other BSD users with respect to
network throughput problems. Your response seems to fall in the latter
category. Thanks for the feedback.

07/05/06, dave feustel <dfeustel (AT) mindspring (DOT) comwrote:
I just upgraded to 3.9 yesterday and today I am having
severe network problems. This has been happening for the
past week, but is now much worse. Browser requests take forever

Clearly, it's BSD's fault. Try downgrading to 3.8, or 3.7, or
better yet 3.6. do a clear install.

to complete, I can't ping verizon.com, traceroute doesn't

As Jason has mentioned, no-one can ping verizon.com.

work through the new verizon dsl modem which assigns
a local address of 192.168.1.47 to my computer. The

I assume it worked before the incident? you didn't test if it worked before?

modem has address 192.168.1.1. Here is some sample console
log showing the ping and traceroute problems.
I called Verizon technical support, but it is useless.

Try to email KDE mailing list, maybe it's just that your computer
doesn't have enough memory or something

Any ideas about how to fix this?

than calling verizon, -- no.

Thanks,
Dave Feustel

Seriously, what do you think will happen if everyone would start
posting questions here about Sprint, Verizon, BT, Telstra, GMX,
Corbina? This is misc@openbsd, not offtopic@, and not
broadbandreports@.

Sunday 07 May 2006 11:29, Jason Dixon wrote:
>So where are the "severe network problems" you allude to?
>
Konqueror is unusable this morning because almost no web accesses
other than those to my local webpages are completing.

So provide troubleshooting examples (e.g., tcpdump) that demonstrate
something is broken with your TCP/IP stack.

Actually, the problems with verizon are getting worse. Now more than
half of my outgoing emails are failing to complete and I have to retransmit
them. I am also having progressively more severe problems with Kmail
which I won't bother you with.

Sunday 07 May 2006 11:16, Constantine A. Murenin wrote:
07/05/06, dave feustel <dfeustel (AT) mindspring (DOT) comwrote:
I just upgraded to 3.9 yesterday and today I am having
severe network problems. This has been happening for the
past week, but is now much worse. Browser requests take forever

Clearly, it's BSD's fault. Try downgrading to 3.8, or 3.7, or
better yet 3.6. do a clear install.

I always do a clean install from cdrom.

to complete, I can't ping verizon.com, traceroute doesn't

As Jason has mentioned, no-one can ping verizon.com.

This is a surprise to me. Verizon has changed the modem proved
to DSL customers. It was possible to both ping and traceroute to verizon
through the old modem. Not with the new modem. I generally ping mindspring to
test connectivity. tried verizon this morning because I was running
out of ideas. Also fvwm won't start - says it can't access the display. kde
works though.

work through the new verizon dsl modem which assigns
a local address of 192.168.1.47 to my computer. The

I assume it worked before the incident? you didn't test if it worked
before?

modem has address 192.168.1.1. Here is some sample console
log showing the ping and traceroute problems.
I called Verizon technical support, but it is useless.

Try to email KDE mailing list, maybe it's just that your computer
doesn't have enough memory or something

512 MB memory.

Any ideas about how to fix this?

than calling verizon, -- no.

Tried that. Waste of time.

Thanks,
Dave Feustel

Seriously, what do you think will happen if everyone would start
posting questions here about Sprint, Verizon, BT, Telstra, GMX,
Corbina? This is misc@openbsd, not offtopic@, and not
broadbandreports@.

Understood. Thanks for your help.

dave feustel wrote:
I just upgraded to 3.9 yesterday and today I am having
severe network problems. This has been happening for the
past week, but is now much worse. Browser requests take forever
to complete,

Make sure your DNS is working and that you're using the right one. A
Domain
Namer server (DNS) map host names to ip addresses. Many network
applications
query DNS.

try :

use dig : dig @<your DNS .<some siteA

example : dig @ns1.yahoo.com www.yahoo.com

If browsers is slow but renders nevertheless. DNS could be the problem.

I can't ping verizon.com, traceroute doesn't

Can you ping using the ip address.

Try pinging : 209.125.236.3 & www.yahoo.com

It the first work and the second doesn't it could be your DNS
work through the new verizon dsl modem which assigns
a local address of 192.168.1.47 to my computer. The
modem has address 192.168.1.1. Here is some sample console

I'm not sure that the "Warning: mindspring.com has multiple addresses" is
part of the problem. Mindspring and newedge networks are merging
log showing the ping and traceroute problems.
I called Verizon technical support, but it is useless.
Any ideas about how to fix this?

Thanks,
Dave Feustel

/home/daf}ping mindspring.com
PING mindspring.com (207.69.189.28): 56 data bytes
64 bytes from 207.69.189.28: icmp_seq=0 ttl=246 time=80.915 ms
64 bytes from 207.69.189.28: icmp_seq=1 ttl=246 time=81.187 ms
64 bytes from 207.69.189.28: icmp_seq=2 ttl=246 time=80.871 ms
64 bytes from 207.69.189.28: icmp_seq=3 ttl=246 time=83.075 ms
64 bytes from 207.69.189.28: icmp_seq=4 ttl=246 time=82.433 ms
64 bytes from 207.69.189.28: icmp_seq=5 ttl=246 time=82.232 ms
64 bytes from 207.69.189.28: icmp_seq=6 ttl=246 time=81.964 ms
mindspring.com ping statistics
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 80.871/81.811/83.075/0.780 ms
/home/daf}traceroute mindspring.com
traceroute: Warning: mindspring.com has multiple addresses; using
207.69.189.28
traceroute to mindspring.com (207.69.189.28), 64 hops max, 40 byte packets
1 dslrouter (192.168.1.1) 0.632 ms 0.601 ms 0.464 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 smtpsvc8.mindspring.com (207.69.189.28) 79.695 ms * 105.213 ms
/home/daf}traceroute verizon.com
traceroute to verizon.com (192.76.85.245), 64 hops max, 40 byte packets
1 dslrouter (192.168.1.1) 0.602 ms 0.555 ms 0.483 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
^C
/home/daf}
--
/home/daf}ping verizon.com
PING verizon.com (192.76.85.245): 56 data bytes
verizon.com ping statistics
170 packets transmitted, 0 packets received, 100.0% packet loss