On Sunday 07 May 2006 11:16, Constantine A. Murenin wrote: > On 07/05/06, dave feustel <[EMAIL PROTECTED]> 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 > > Clearly, it's OpenBSD's fault. Try downgrading to 3.8, or 3.7, or > better yet 3.6. Or 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. Only 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? Or 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? > > Other 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 [EMAIL PROTECTED], not offtopic@, and not > [EMAIL PROTECTED] Understood. Thanks for your help.
