Wireless Card

Wireless Card

[Mark Sibley]

Dear Sir / Madam
     I Have got an old Dell Inspirin 300 laptop running Ubuntu 14.04 32 
Bit but the wireless card does not work . I have done some research and 
found that it is pretty awkward to fix . The card in question is a 
Broardcom BCM 4318 [14e4:4318] rev 02 . I have tried various Terminal 
commands but to no avail .I have fairly basic knowledge , and would 
really appreciate some help . I am at present using a USB wireless 
adaptor . Regards Mark

Wireless Card

[Javier Domingo Cansino]

Hi Mark,

You are in the driver development list. You will find much more
support in the ubuntu user forums or in the askubuntu web page. I
would recommend you to try #ubuntu irc channel to ask for help.

Clicking on this link will let you join such support channel:
http://webchat.freenode.net/?nick=mark_sibley&channels=ubuntu

Cheers

On Tue, Sep 23, 2014 at 3:11 PM, Mark Sibley
<marksibley58@googlemail.com> wrote:
> Dear Sir / Madam
>     I Have got an old Dell Inspirin 300 laptop running Ubuntu 14.04 32 Bit
> but the wireless card does not work . I have done some research and found
> that it is pretty awkward to fix . The card in question is a Broardcom BCM
> 4318 [14e4:4318] rev 02 . I have tried various Terminal commands but to no
> avail .I have fairly basic knowledge , and would really appreciate some help
> . I am at present using a USB wireless adaptor . Regards Mark
>
> _______________________________________________
> b43-dev mailing list
> b43-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/b43-dev



-- 
Javier Domingo Cansino

Wireless Card

[Larry Finger]

On 09/23/2014 08:11 AM, Mark Sibley wrote:
> Dear Sir / Madam
>      I Have got an old Dell Inspirin 300 laptop running Ubuntu 14.04 32 Bit but
> the wireless card does not work . I have done some research and found that it is
> pretty awkward to fix . The card in question is a Broardcom BCM 4318 [14e4:4318]
> rev 02 . I have tried various Terminal commands but to no avail .I have fairly
> basic knowledge , and would really appreciate some help . I am at present using
> a USB wireless adaptor . Regards Mark

I use a BCM4318 without difficulty. If you look at the output of the dmesg 
command, you will likely see that the firmware is missing. For legal reasons, no 
distro is allowed to redistribute such firmware in the manner used by other 
manufacturers. To overcome this issue, the b43 developers have created a program 
to "cut" such firmware from a driver for some other system. I am not an Ubuntu 
user, thus I am not familiar with how this process is implement. The b43 wiki at 
http://wireless.kernel.org/en/users/Drivers/b43#Ubuntu.2FDebian says you should 
use the command:

sudo apt-get install firmware-b43-installer

It further states "In recent versions of Ubuntu and Debian, installing the 
firmware-b43-installer package will handle everything for you. You will be asked 
to automatically fetch and install the firmware into the right location. Again, 
you will need an internet connection." It sounds as if that is all you will need.

If you have already installed the firmware, and you have a different problem, 
then we will need a more complete description.

Larry

RE: wireless card

[Ian Pratt]

> I haven't done it under xen. Some (all?) wireless cards have 
> trouble sending packets with a forged MAC address (something 
> to do with association to an access point). I think the way 
> it works is that the MAC address of the wireless client is 
> associated to the AP, and so if you start sending packets 
> with a different MAC address, the AP is going to reject them, 
> and if the AP tries to send packets to the MAC of domU, it 
> won't be able to see it in its list of associated MAC addresses.

[James: well spotted!]

The easiest way to work around this is to use a routed rather than
bridged setup in dom0.

Take a look at the network-router and vif-route scripts.

Ian
 

RE: wireless card

[James Harper]

I haven't done it under xen. Some (all?) wireless cards have trouble
sending packets with a forged MAC address (something to do with
association to an access point). I think the way it works is that the
MAC address of the wireless client is associated to the AP, and so if
you start sending packets with a different MAC address, the AP is going
to reject them, and if the AP tries to send packets to the MAC of domU,
it won't be able to see it in its list of associated MAC addresses.

At home (no xen, ultrasparcII) I bridge an ethernet adapter to a
wireless card (intersil prism2.5 chipset using hostap driver) which
works fine, but the wireless card is running as an AP so the rules are
reversed.

You may be able to set up an AP to AP bridge (is it called WDS??)
between your xen box and the AP to allow what you want to do.

If you give some more information about your setup I might be able to
offer some other suggestions, eg are you bridging or natting or routing
eth1 to domU (my comments above are based on bridging).

James

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Deepak Manohar
> Sent: Friday, 10 June 2005 10:56
> To: Xen-devel@lists.xensource.com
> Subject: [Xen-devel] wireless card
> 
> Hi all,
> 
>  Has anyone setup a wireless card on xen-3.0-devel either on dom0 or
domU?
> 
>  The setup that we have
> 
>  eth0 -- Intel ProLan
>  eth1 -- Orinoco Gold Card 802.11b
> 
>  both these interfaces got IPs from the dhcp server in dom0.
> 
>  In /etc/xen/scripts/network we changed the "netdev" to "eth1".
> 
>  Now from domU we were not able to send any packets to the external
> network.
> (but we cud ping the dom0 interface).
> 
>  Any help wud be appreciated.
> 
> thanks
> deepak
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

wireless card

[Deepak Manohar]

Hi all,

 Has anyone setup a wireless card on xen-3.0-devel either on dom0 or domU? 

 The setup that we have 

 eth0 -- Intel ProLan   
 eth1 -- Orinoco Gold Card 802.11b

 both these interfaces got IPs from the dhcp server in dom0. 

 In /etc/xen/scripts/network we changed the "netdev" to "eth1". 

 Now from domU we were not able to send any packets to the external network. 
(but we cud ping the dom0 interface).

 Any help wud be appreciated.

thanks
deepak