[ndiswrapper] cannot get IP via DHCP

could you please try to not use ndiswrapper, but the native broadcom drivers?

that said, please test this in hardy. maybe use a livecd of the latest alpha in case you cannot upgrade your system.

Thanks a lot,

 - Alexander

I tried it before deciding to install ndiswrapper.

The connection does not beyond 6 Mbps even when I sit next to the AP.

I checked in my office and it connects without a problem. But I need to
check at home as well since the behavior differs based on wired ethernet
being connected or not at boot time.

For ex: my NIC works when I connect the cable during boot up. But if I
connect it after boot, it does not.

I will send another email once I am home.

Thanks,
Kalyan

On Tue, 2008-03-11 at 19:49 +0000, Alexander Sack wrote:

> could you please try to not use ndiswrapper, but the native broadcom
> drivers?
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>

Ok, here are the observations with b43 driver

b43 loads and sees access points. But the number of access points seen with b43 are much less than ndiswrapper.

ex: with ndiswrapper, i can see 10 APs but with b43 I can see only my own, just one.

However, no IP can be obtained on wlan0. I did not go through the steps I mentioned above to get an IP.

When I unload b43 and do the above steps, I see all APs and can get IP by following above procedure.

Hence I guess the problem is not with the wlan driver but the DHCP.

Let me know if you need any more info.

Thanks,
Kalyan

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

 apt-cache policy network-manager
network-manager:
  Installed: 0.6.6-0ubuntu1
  Candidate: 0.6.6-0ubuntu1
  Version table:
 *** 0.6.6-0ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

OK ... really starting to affect my productivity. Last two times, I was not able to get IP no matter what I did. Here is the only way I can get an IP:

1) connect the NIC
2) boot up
3) I get IP on both wlan and eth0 regardless of the driver I use if eth0 is connected.

I have to reboot to Vista to get my work done. Somehow this DHCP problem seems to be carrying from release to release. :(

Why is the bug still marked incomplete?

there are three broadcom native modules:

b43, bcm43xx, b43legacy.

Please test all.

further, in summary you said "There is an active thread on Launchpad." ... can you please provide a link?

HI,

I already tried the b43 drivers also in 7.10. Never worked properly. Well
... I am actually facing IP issues with eth0 also as described.

IP assignment is successful only when eth0 is connected during boot up.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/79626

Same issue - DHCPREQ goes out ... server responds with DHCPACK (confirmed by
looking at the log on the DHCP server), my system never gets it unless I do
some jumping through the hoops for both wirelss and wired connections ...
all drivers.

Only way I can get IP is connect eth0 during bootup.

Thanks,
Kalyan

On Mon, Mar 17, 2008 at 4:48 AM, Alexander Sack <email address hidden> wrote:

> further, in summary you said "There is an active thread on Launchpad."
> ... can you please provide a link?
>
> ** Summary changed:
>
> - [/ndiswrapper] cannot get IP via DHCP
> + [ndiswrapper] cannot get IP via DHCP
>
> --
> [ndiswrapper] cannot get IP via DHCP
> https://bugs.launchpad.net/bugs/200696
> You received this bug notification because you are a direct subscriber
> of the bug.
>

More info ....
I tried connecting to an AP with no encryption .... WLAN gets IP without any problem. However, no packets could go out to the network. Worked fine with Windows ... so the AP and the network is fine.

I`ve got the same problem. it seems to be ipv6 problem. When I`m blacklist ipv6 module the problem has gone. Does any one confirm that ?

Exactly the same problem here. It's so frustrating as the native wireless drivers (b43) work fine while I'm at home and using WPA-PSK but I can't use my laptop at university now because the b43 driver can't connect to WPA-Enterprise networks.

I have to use the crappy overcrowded university computers now I can't use ndiswrapper.

It's not an ipv6 problem for me. Although it's strange that sometimes when it doesn't get an ipv4 address, it gives it an ipv6 address. I've tried blacklisting ipv6 and no joy.

ndiswrapper driver modules are not feature complete enough for network manager - reassigning.

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

I dont seem to be having any problem these days.

On Sat, Nov 29, 2008 at 9:45 AM, JaysonRowe <email address hidden> wrote:

> Since it's been a very long time since any additional info was added to
> this bug, I'm just checking to see if this is still an issue, and find
> out what additional work should be done on this bug.
>
> --
> [ndiswrapper] cannot get IP via DHCP
> https://bugs.launchpad.net/bugs/200696
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Closing as reporter is no longer having issue.