wireless, Broadcom & jaunty

[Joep L. Blom]

As so many on this list I finally found the courage to upgrade one of my 
systems - a 64-bit AMD 3000 - to jaunty. Although rather cumbersome 
(first upgrading to Intrepid which took 5 hours over a slow wireless 
link in Hardy) and then using wired (as wireless didn't work) I upgraded 
to jaunty. This went rather well to my surprise.
However, my Broadcom BCM4306 won't work as expected.
Yes, I can see many routers (including my own), however, wicd tries to 
connect but can't.
dmesg tells me:
____________________________________________________
[   16.070566] b43-phy0: Broadcom 4306 WLAN found
[   16.117038] phy0: Selected rate control algorithm 'pid'
[   16.187063] Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: 
FW13 ]
[   16.193112] udev: renamed network interface wlan0 to eth0
........

So the driver is loaded and apparently without problems.
However on a later moment it says
[   45.808146] eth0: authenticate with AP 00:c0:49:54:77:9e
[   45.809516] eth0: authenticated
[   45.809519] eth0: associate with AP 00:c0:49:54:77:9e
[   45.811826] eth0: RX AssocResp from 00:c0:49:54:77:9e (capab=0x431 
status=0 aid=9)
[   45.811829] eth0: associated
[   45.811924] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
............
So it looks alright
however,
[   55.860018] eth0: no IPv6 routers present
it says no IPv6 routers present which is correct. but when I try to 
connect it doesn't and in dmesg I get the following lines:

[  580.835711] Registered led device: b43-phy0::tx
[  580.835748] Registered led device: b43-phy0::rx
[  580.835784] Registered led device: b43-phy0::radio
[  580.863025] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  581.496790] eth0: direct probe to AP 00:c0:49:54:77:9e try 1
[  581.506815] eth0: direct probe to AP 00:c0:49:54:77:9e try 1
[  581.512389] eth0 direct probe responded
[  581.512402] eth0: authenticate with AP 00:c0:49:54:77:9e
[  581.515413] eth0: authenticated
[  581.515420] eth0: associate with AP 00:c0:49:54:77:9e
[  581.517722] eth0: RX AssocResp from 00:c0:49:54:77:9e (capab=0x431 
status=0 aid=9)
[  581.517727] eth0: associated
[  581.517968] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

So at 580.8 it tells me eth0 is not ready and at 581.5 it says it is ready.
My wired connection - also managed by wicd - runs without a problem.
I am on a IPv4 network only. I have the idea that the wireless wants to 
connect over IPv6 but where does he get that information?

(As another problem sound doesn't work but I think I could expect that).
Hope somebody can give me some directions.
Joep