PDA

View Full Version : [ubuntu] Ubuntu 10.04 has shut down all network communication



flopwich
May 1st, 2010, 10:00 PM
I upgraded to 10.04 yesterday and Firefox, or rather something I don't know that's replaced it called "Namoroku", worked fine. Today Firefox won't work and Thunderbird and Evolution won't work, either with wifi or with a direct Ethernet link. When I did the System Test, it claimed that the internet connection was fine, but I can't get anything in or out. This is on an Acer Aspire One that I have configured as dual boot with Windows 7. Under Windows Firefox works fine on the wifi. I haven't checked on the Ethernet connection, but assume it works if the wifi does.

Ubuntu also tells me that my battery is "broken", although that's a lesser problem. I can ignore that. Windows has no problem with the battery, either.

Any help for the communications problems would be appreciated.

Here's the sudo lshw -c net output...

*-network
description: Ethernet interface
product: Atheros AR8132 / L1c Gigabit Ethernet Adapter
vendor: Atheros Communications
physical id: 0
bus info: pci@0000:01:00.0
logical name: eth0
version: c0
serial: 70:5a:b6:21:f3:fd
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=atl1c driverversion=1.0.0.1-NAPI firmware=N/A latency=0 link=no multicast=yes port=twisted pair
resources: irq:27 memory:57000000-5703ffff ioport:5000(size=128)
*-network
description: Wireless interface
product: AR9285 Wireless Network Adapter (PCI-Express)
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan0
version: 01
serial: c4:17:fe:62:77:06
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath9k ip=192.168.2.100 latency=0 multicast=yes wireless=IEEE 802.11bgn
resources: irq:17 memory:56000000-5600ffff

flopwich
May 2nd, 2010, 05:53 PM
I just discovered that I am able to PING my email server, so I'm not sure what's going on. Communications continue to work fine in Windows, however.

udippel
May 4th, 2010, 07:54 AM
I just discovered that I am able to PING my email server, so I'm not sure what's going on. Communications continue to work fine in Windows, however.

Yes. Make this a Ubuntu bug. I use to experience the same; read the short version up here:
http://ubuntuforums.org/showthread.php?p=9232313#post9232313

Uwe

flopwich
May 5th, 2010, 01:56 AM
Thank you for pointing me to that information. The process describes looks a little over my head and I wouldn't have a clue how to "put things back" if it didn't work. Also, the symptoms my computer shows are a little different. For example, it won't work any better with an Ethernet connection to my router any better than with wireless. Last night the wireless started working just fine, for a while. Tonight it will connect to some sites, like the National Weather Service, but not Google, regardless of whether it's a wireless or a wired connection. Update Manager and System Testing can both connect just fine, wirelessly.

Everything continues to work just fine in Windows. As much as I like Ubuntu and would prefer to use it, and most especially delight in being able to cut the cord connecting me to the Borg (Microsoft), this one's a show-stopper. I must once more accept that resistance is futile and be assimilated, hoping that if I check upgrades in Ubuntu once in a wile, one of the upgrades will fix this bug.

Thanks again for your help.

flopwich
May 12th, 2010, 11:59 PM
For whatever it's worth, the problem with Firefox had to do with IPv6.

First, I downloaded the latest version of Firefox, then hunted down that Namoroka thing and deleted it and the directory it was in and installed Firefox.

From a suggestion found elsewhere on here, you open Firefox, enter "about:config" and it pulls up all the configuration parameters for Firefox. Search for "IPv6disable" and set it to "true". Firefox worked perfectly. Now if I could just find the same fix for Thunderbird I'd be on a roll. So the problem is half-solved.

I don't know if this is a bug in Ubuntu or in Firefox, but it happened with the upgrade from Ubuntu 8 to 9 and now again from 9 to 10. It never happens in Windows. It'd be nice if somebody would fix it. It looks like the routines to handle IPv6 aren't working very well, where ever it is.

The problem with the battery seems to have fixed itself. (?)