Getting the drivers for my broadcom wireless installed was certainly easier this time than on any prior linux attempt (but still not close to FreeBSD, but I need flash 10 or the kids on this one . . .)
The first time I tried to connect with the manager (once I found it) worked easily. Then I powered down and tried to log in as one of my kids and the great game of peek-a-boo began.
It always sees the home network, with a signal strength ranging from 55-80. It just doesn't always connect (and I've had a couple of rounds where nm-tool sees both my network and another, but knetworkmanager only reports one or neither. Usually, though, it reports my local network with nice signal strength).
Sometimes it just comes up; other times it doesn't. This session was started by my deleting the older configuration, configuring again, and using ifconfig.
What I need is for the computer to come up connected with a static ip, without having to be told to do so by a user. Telling them to reboot, wait five minutes, and then reboot again if no network automagically appears is not going to be popular.
It's not that it loses the network once connected; that has yet to happen. It just doesn't connect!
hawk, eager to lose the white network cable down the hall
The first time I tried to connect with the manager (once I found it) worked easily. Then I powered down and tried to log in as one of my kids and the great game of peek-a-boo began.
It always sees the home network, with a signal strength ranging from 55-80. It just doesn't always connect (and I've had a couple of rounds where nm-tool sees both my network and another, but knetworkmanager only reports one or neither. Usually, though, it reports my local network with nice signal strength).
Sometimes it just comes up; other times it doesn't. This session was started by my deleting the older configuration, configuring again, and using ifconfig.
What I need is for the computer to come up connected with a static ip, without having to be told to do so by a user. Telling them to reboot, wait five minutes, and then reboot again if no network automagically appears is not going to be popular.
It's not that it loses the network once connected; that has yet to happen. It just doesn't connect!
hawk, eager to lose the white network cable down the hall
Comment