can not connect access point (Michael Renner)

[Brian Wootton]

On 07/09/11 13:00, kubuntu-users-request at lists.ubuntu.com wrote:
> Send kubuntu-users mailing list submissions to
> 	kubuntu-users at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
> or, via email, send a message with subject or body 'help' to
> 	kubuntu-users-request at lists.ubuntu.com
>
> You can reach the person managing the list at
> 	kubuntu-users-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kubuntu-users digest..."
>
>
> Today's Topics:
>
>     1. Re: can not connect access point (Michael Renner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 6 Sep 2011 18:21:55 +0200
> From: Michael Renner<michael.renner at gmx.de>
> To: Waleed Hamra<kubuntu-users at whamra.com>,	Kubuntu user technical
> 	support<kubuntu-users at lists.ubuntu.com>
> Subject: Re: can not connect access point
> Message-ID:<201109061822.07622.michael.renner at gmx.de>
> Content-Type: Text/Plain;  charset="iso-8859-15"
>
> On Saturday 27 August 2011, Waleed Hamra wrote:
>> On 08/25/2011 08:05 PM, Michael Renner wrote:
> [...]
>
>> this problem is one of those elusive nasty ones. there's no one reason
>> why it would happen.
>> as you suggested, yes, DHCP can very well be the problem sometimes, if
>> the network fails to receive an IP address from the access point, NM
>> disconnects it. you can try setting up manual IPs, and connect. if it
>> stays connected, then try out the network. many times, DHCP wouldnt be
>> working not due to a configuration error, but rather because the
>> interface isnt receiving packets due to a driver problem.
>>
>> some people report that wpa_supplicant is the culprit, i suggest you try
>> this command in a terminal:
>>
>> ps -Af | grep wpa_supplicant
> well, I tried many things: applying the IP by hand, setup an ad hoc network
> with an other notebook: no luck. I tried to setup the ad hoc network with the
> build in WLAN interface (801.1b only): no luck.
>
>> and see if more than one instance of this program are running. if just
>> one, keep it, if more, kill them all, then start the program again by:
> I tested my USB-Stick with the other notebook: this works. It seems to me that
> his is maybe, or not, a probem with the installation.
>
>> sudo /sbin/wpa_supplicant -u -s
>>
>> let's just test these 2 theories for now, and we'll see what happens :)
> After all I decided to setup the machine from scratch (a simple task due the
> fact that I can recover my backup after that). Than we will see.
>
> CU
I had a fair bit of trouble setting up my completely wi-fi connected 
network.
I finally disabled DHCP in my router and made sure DHCP wasn't running
anywhere else and used static addresses throughout. My router allowed
me to do this, I created my own /etc/hosts and set up my printer with a
static address. The only bit that bothered me was the Windows 7 machine
I'm running, but it seems to cope without putting the boot in, this has 
stably
worked for some years but I'm a little bothered by the change from IPV4
to IPV6, cos I know zilch about IPV6.
brian