When internet disconnection occurs, it is not possible to connect again

please attach your /var/log/syslog to this bug as soon as you see this problem again.

Thanks,
 - Alexander

Same problem here: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) using ndiswrapper, Linksys WRT54G router.

The router frequently crashes (signal strength meter normal but no internet, trying to ping router reports 'host unreachable') and has to be reset; if this is done fairly quickly then it reconnects fine, but if it is left off for long enough for network-manager to report no connection (not just zero signal strength), it often won't reconnect; when told to do so, sometimes it shows the 'trying to connect' animation then fails to connect, sometimes it doesn't do anything visible at all.

The router crashes (a known issue with this type of router, http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&thread.id=19685&view=by_date_ascending&page=1 ) also seem to have got more frequent (from about one to several per day) since I got a new computer and switched from wired Ubuntu 6.10 to wireless Ubuntu 7.10-amd64. There are also 3 wireless Windows XP computers on the router, and when it goes down it goes down for everyone at once.

Happens at about 08:20 and 10:20 in attached log.

This appears to be fixed in the latest update: reconnection by clicking on the icon then network name now works. I suggest that this bug be closed.

(It does however seem to be necessary to reboot once after installing the update-it repeatedly asked for the network key when I didn't.)

This bug reappeared when I returned to wireless after a few weeks on wired (without having knowingly changed any network settings), with the same symptoms: when told to reconnect after the router has been turned off and on again, it shows the 'trying to connect' animation with both 'lights' out, and fails to connect. sudo /etc/init.d/networking restart has no effect, only cure I know is to reboot. Around 20:10 to 20:15 (two connection attempts) in attached log.

Can anyone confirm that this bug has reappeared?

On my system (amd64 Gutsy) it's completely reproducible by switching off the router for a minute or so.

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

It's been quite a while I did not experience any disconnection. It seems to
work quite well now.
I'm not going to be at my apartment for a while, I can't test what you
suggest. Sorry for this.

Sylvain

2008/3/20, Basilio Kublik <email address hidden>:
>
> Hi there
> do you still experience this issue with the current version of the
> application?, could you please try to reproduce this using the live
> environment of the Desktop CD of the development release - Hardy Heron.
>
> Thanks in advance
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
>
> --
> When internet disconnection occurs, it is not possible to connect again
> https://bugs.launchpad.net/bugs/153839
> You received this bug notification because you are a direct subscriber
> of the bug.
>

In current Gutsy, it's no longer 100% reproducible but does still seem to happen: only once out of 3 attempts just now (encrypted wireless network). I haven't tested Hardy.

broadcom drivers might have improved in hardy/intrepid. If possible verify that you still have this problem there.

I did a fresh install of Intrepid on my laptop.

I have the BCM4312 card in my laptop and tried to use the restricted driver from the restricted driver manager. I would get SLOW download speeds and the connection would time out and then spend minutes clicking okay repeatedly to get it to reconnect.

My other laptop is not having any issues and it is using the ipw2200 driver.

I just switched to ndiswrapper with the bcmwl5 driver and have not had any issues yet.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!