Re: bcm43xx finally working, with encryption too!!!

2006-01-23 Thread Erik Chakravarty 
Broadcom 43xx driver & softmac working here on a 2004 Albook 15"

I had to set 'iwconfig eth1 rate 11M' to even ping my router - it seems
that this card will not operate at full 54M speed.

DHCP does not seem to be working - I read reports of people running
scans before running dhclient eth1 but this does not seem to work for
me. I am using a static IP.

Also - I had to manually set my AP MAC with iwconfig ap XX:XX:XX:XX:XX
because some how iwconfig eth1 reported Access Point: Invalid, although
the ESSID was correctly set.

PROBLEM - connection drops every few minutes - i have to ifdown / ifup
eth1 and add a default route back into my routing table to get my
internet connection back online. Anyone noticed this? Suggestions?

I have not tested WEP / WPA.




On Sun, 2006-01-15 at 23:24 +0200, Emmanuel Galatoulas wrote:
> Ruben wrote:
> 
> >At Wed, 11 Jan 2006 09:39:01 +1100, Aaron Kerr wrote:
> >  
> >
> >>Thanks. I will try waiting a few minutes after setting up the connection.
> >>
> >>
> >
> >I timed it this morning, and it only worked after 4 minutes.  It's
> >possible this has something to do with my access point.
> >Authentication and association with the AP happens almost immediately.
> >
> >  
> >
> >>Your delays when running route or netstat could be a DNS lookup failure.
> >>Try "netstat -rn" which will not try to translate IP addresses to names.
> >>
> >>
> >
> >Thanks (and thanks to Michael)... that was indeed the reason.
> >
> >Ruben
> >
> >Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
> >
> >
> >  
> >
> well i have got eventually the AirPort card working WITH WEP SECURITY ON!!!
> i guess it  was basically a driver issue cos using the latest bcm43xx driver
> (actually  bcm43xx-20060115.tar.bz) as welll as today's softmac-snapshot
> both the driver and the modules were compiled smoothly (despite some
> warning messages in bcm43xx!)
> Perhaps it was also a matter of the AppleAirport2 firmware file
> ie. the MacOS X file 
> /System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2
> the latest one from MacOS X 10.4.4 did not produce the error messages 
> that earlier version did
> when running fwcutter!
> 
> At any rate, the thing is that the modules run OK, encryotion does work
> (at the moment using WEP key 64-bit hex)
> and also without the nasty hang ups and so on that  I observed  with the 
> earlier versions
> (eg, if  you were  deactivating the wired interface eth0 and then were 
> trying to activate
> the wireless one, the system could hang, or  evev if you were just 
> unplugging the ethernet plug!!!)
> 
> so a big thanks to the community serving this wonderful work
> one more proof of what a power the community is!!!
> 
> (and yes this was the last main reason for still using MacOS X , sorry)
> (OK, if only the sound drivers was working fully too)
> 
> (PS. this mail is of course being sent wirelessly!!!)
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-22 Thread Aaron Kerr 

I have found that scanning before dhcp is vital to having a working
bcm43xx interface. When I try to bring up my bcm43xx interface without
scanning (until I see a network) dhclient fails to get an IP address. If
I scan until I see my network dhclient works every time (well almost
every time). Like a lot of my pre-up script I do not know why it is
needed but it seems to make it work (see: modprobe -r, ifconfigs and scans).

Aaron


Johannes Berg wrote:
> On Fri, 2006-01-20 at 08:01 -0500, Shreyas Ananthan wrote:
> 
> 
>>I tried this approach, it seems, at least from the behavior in my
>>ibook, that the commands with "post-up" run after the dhcp command. So
>>it still doesn't do the iwlist scanning before dhcp command.
> 
> 
> I don't really understand why you all want to scan before doing stuff.
> It isn't necessary. softmac scans automatically before associating.
> 
> johannes




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-20 Thread Johannes Berg 
On Fri, 2006-01-20 at 08:01 -0500, Shreyas Ananthan wrote:

> I tried this approach, it seems, at least from the behavior in my
> ibook, that the commands with "post-up" run after the dhcp command. So
> it still doesn't do the iwlist scanning before dhcp command.

I don't really understand why you all want to scan before doing stuff.
It isn't necessary. softmac scans automatically before associating.

johannes


signature.asc
Description: This is a digitally signed message part

Re: bcm43xx finally working, with encryption too!!!

2006-01-20 Thread Shreyas Ananthan 
Bin Zhang <[EMAIL PROTECTED]> writes:

> Try not run dhclient directly. You can configure all you need in
> /etc/network/interfaces:
> For example:
> iface eth1 inet dhcp
>   pre-up modprobe ..
>   post-up iwlist eth1 scan
>   post-up iwconfig eth1 rate 11M
>   post-up iwconfig eth1 essid ..
>   #post-up iwconfig eth1 key ..
> 
> Use "ifup eth1" and "ifdown eth1".
> 
> Bin


I tried this approach, it seems, at least from the behavior in my
ibook, that the commands with "post-up" run after the dhcp command. So
it still doesn't do the iwlist scanning before dhcp command.

Shreyas. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-20 Thread Bin Zhang 
On 20 Jan 2006 00:30:26 -0500, Shreyas Ananthan
<[EMAIL PROTECTED]> wrote:
> Aaron Kerr <[EMAIL PROTECTED]> writes:
>
> 
>
> > While my script is some overly complicated perl that tries to find one
> > of my preferred networks here is what it would look like as simple
> > bourne shell script (last two lines optional depending on network and
> > use as pre-up script or standalone script):
>
> 
>
> > #iwconfig $INTERFACE key 0a1b2c3d4e
> > #dhclient $INTERFACE
> > 
>
> 
>
> My script works exactly the way you described. My problem is with the
> last line, when I try dhclient. It seems to do an ifconfig down/up
> again, which means I have to run iwlist scan again to get the wireless
> working again. What I want is a way to disable dhclient from doing its
> own ifconfig down/up on eth1 (or eth2 sometimes!), so that the iwlist
> command doesn't have to be run separately on another xterm/console.
>
Try not run dhclient directly. You can configure all you need in
/etc/network/interfaces:
For example:
iface eth1 inet dhcp
  pre-up modprobe ..
  post-up iwlist eth1 scan
  post-up iwconfig eth1 rate 11M
  post-up iwconfig eth1 essid ..
  #post-up iwconfig eth1 key ..

Use "ifup eth1" and "ifdown eth1".

Bin

> Shreyas.
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Shreyas Ananthan 
Aaron Kerr <[EMAIL PROTECTED]> writes:



> While my script is some overly complicated perl that tries to find one
> of my preferred networks here is what it would look like as simple
> bourne shell script (last two lines optional depending on network and
> use as pre-up script or standalone script):



> #iwconfig $INTERFACE key 0a1b2c3d4e
> #dhclient $INTERFACE
> 



My script works exactly the way you described. My problem is with the
last line, when I try dhclient. It seems to do an ifconfig down/up
again, which means I have to run iwlist scan again to get the wireless
working again. What I want is a way to disable dhclient from doing its
own ifconfig down/up on eth1 (or eth2 sometimes!), so that the iwlist
command doesn't have to be run separately on another xterm/console.

Shreyas. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Aaron Kerr 

I have bcm43xx semi-reliably working on my iBook G4 12".

I am using 2.6.15.1 kernel, bcm43xx and softmac snapshots (from 15 Jan
06), some dodgy scripts and IEEE80211 compiled in the kernel as a module.

DODGY SCRIPTS - To get the wireless to reliably associate to an AP (with
or without WEP) I have a pre-up script that does the following:
1. unload and reload the bcm43xx module
2. ifconfig down and up the interface (it seems to help?!?)
3. Scan until we see the wireless network (this can take several tries)
4. Set the rate to 11M and the ESSID to the local network ESSID.

While my script is some overly complicated perl that tries to find one
of my preferred networks here is what it would look like as simple
bourne shell script (last two lines optional depending on network and
use as pre-up script or standalone script):


#!/bin/sh

modprobe -r bcm43xx
modprobe bcm43xx
ifrename   # Needed because I rename the interface to bcm0
INTERFACE=`iwconfig 2>&1 | fgrep "broadcom 4318" | cut -f1 -d" "`
ifconfig $INTERFACE down
ifconfig $INTERFACE up
ESSID=""
while [ -z "$ESSID" ]
do
   ESSID=`iwlist $INTERFACE scan | fgrep ESSID | cut -f2 -d'"'`
   sleep 1
done
iwconfig $INTERFACE rate 11M
iwconfig $INTERFACE essid $ESSID
#iwconfig $INTERFACE key 0a1b2c3d4e
#dhclient $INTERFACE




Shreyas Ananthan wrote:
> Bin Zhang <[EMAIL PROTECTED]> writes:
> 
> 
> 
>>Try dscape/bcm43xx. It needs only one second to get connected.
>>http://svn.berlios.de/wsvn/bcm43xx/branches/dscape/driver/HOWTO?op=file&rev=1027&sc=1
>>
>>Bin
> 
> 
> 
> 
> Hi,
> 
> I tried to make dscape+bcm43xx work and haven't succeeded. This is
> with 2.6.15 kernel with the unofficial patch applied. The sta_up.sh
> script causes the kernel to crash and I have to reboot. I traced the
> kernel panic to the following command in sta_up.sh
> 
> ifconfig wlan0.11 up 
> 
> and the xmon exception information at this point shows the following
> message...
> 
> vector: 300 at pc=f26b33b8: ieee80211_master_start_xmit+0x6c/0x4bc
> [80211], lr=f2b3378: ieee80211_master_xmit+0x2c/0x4bc [80211]
> msr=9032, sp = ef4b3a00 [ef4b3950]
> dar = 8, dsisr = 4000
> current = ef58e770, pid = 3151, comm = bash
> 
> I am not sure what this means or what other information (from xmon
> dump) that I need to post for someone to be able to help me. 
> 
> 
> I tried posting to the bcm43xx-dev mailing list, but since I am not
> subscribed to the list the message is waiting for moderator approval
> for over three days now. I had also posted about this in debian-ppc
> mailing list a few days ago and there were no responses, so I gave up
> on the dscape+bcm43xx route and went with softmac+bcm43xx. 
> 
> I will give the dscape+bcm43xx route a try again if someone can help
> me with this. Any help will be appreciated. 
> 
> Shreyas. 
> 
> 


-- 

Aaron Kerr
-
Engagement Architect
Sun Microsystems


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Emmanuel Galatoulas 

Shreyas Ananthan wrote:


Bin Zhang <[EMAIL PROTECTED]> writes:



 


Try dscape/bcm43xx. It needs only one second to get connected.
http://svn.berlios.de/wsvn/bcm43xx/branches/dscape/driver/HOWTO?op=file&rev=1027&sc=1

Bin
   





 


I will give the dscape+bcm43xx route a try again if someone can help
me with this. Any help will be appreciated. 

 



Hm, bcm43xx-dscape was the next challenge to take indeed, but pardon me
the HOWTO itself look quite intimitating I am going to try it 
anyway  (even just of curiosity!)


Shreyas. 



 

i coule refer to quite a few fine details about using the driver! For 
instance, some times

I have to repeatedly
#ifdown , #ifup
the interface to get it working (getting at that time an "error"
that the "link is not yet ready")
also some times activating the interface via kwifimanager corrects that 
issue of

not recognising the Access Points IP giving an FF:FF instead!
What I have ended with is to put the relevant information in
my /etc/network/interfaces, which looks like:


auto eth1
iface eth1 inet static
   address 192.168.1.5
   netmask 255.255.255.0
   network 192.168.1.0
   gateway 192.168.1.7
   broadcast 192.168.1.255
   wireless-mode managed
   wireless-essid quadnrg
   wireless-key xx
==

where someone of course may change auto to noauto
and static to dhcp (and commenting the address, netmask etc)
Using this make usually unnecessary the use of iwconfig at all!
(and minding that sometimes even the device interface changes
say from eth2 to eth1! but most of the times sets to eth1 in my case!)

So I think that obviously the state of things regarding
Airport is not yet perfect but certainly has improved dramatically!
Even working with MacOS X, using Airport is not flawless (quite often I have
to reset my access point/router and so on).
So all we need is still more experimentation (and a bit of patience)

emmanuel


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Shreyas Ananthan 
Bin Zhang <[EMAIL PROTECTED]> writes:



> Try dscape/bcm43xx. It needs only one second to get connected.
> http://svn.berlios.de/wsvn/bcm43xx/branches/dscape/driver/HOWTO?op=file&rev=1027&sc=1
> 
> Bin



Hi,

I tried to make dscape+bcm43xx work and haven't succeeded. This is
with 2.6.15 kernel with the unofficial patch applied. The sta_up.sh
script causes the kernel to crash and I have to reboot. I traced the
kernel panic to the following command in sta_up.sh

ifconfig wlan0.11 up 

and the xmon exception information at this point shows the following
message...

vector: 300 at pc=f26b33b8: ieee80211_master_start_xmit+0x6c/0x4bc
[80211], lr=f2b3378: ieee80211_master_xmit+0x2c/0x4bc [80211]
msr=9032, sp = ef4b3a00 [ef4b3950]
dar = 8, dsisr = 4000
current = ef58e770, pid = 3151, comm = bash

I am not sure what this means or what other information (from xmon
dump) that I need to post for someone to be able to help me. 


I tried posting to the bcm43xx-dev mailing list, but since I am not
subscribed to the list the message is waiting for moderator approval
for over three days now. I had also posted about this in debian-ppc
mailing list a few days ago and there were no responses, so I gave up
on the dscape+bcm43xx route and went with softmac+bcm43xx. 

I will give the dscape+bcm43xx route a try again if someone can help
me with this. Any help will be appreciated. 

Shreyas. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Bin Zhang 
On 19 Jan 2006 14:45:12 -0500, Shreyas Ananthan
<[EMAIL PROTECTED]> wrote:
>
> Hi Milan,
>
> I am using Airport wireless card on an iBook 12" G4 and I have managed
> to get bcm43xx driver working both with WEP and WPA, using the default
> debian kernel. I downloaded the softmac-snapshot and bcm43xx snapshots
> (Jan 15, 2006 snapshots) and compiled the ieee80211 modules from the
> softmac-snapshot and use them instead of the ones in the
> kernel. Giuseppe has a good summary of the procedure we followed to
> get it working at http://www.fisica.unipa.it/~lavaget/ubuntuae/
>
> I have found that iwlist scanning isn't very reliable. I sometimes
> have to scan a couple of times before setting the essid using iwconfig
> or wpa_supplicant.

Try dscape/bcm43xx. It needs only one second to get connected.
http://svn.berlios.de/wsvn/bcm43xx/branches/dscape/driver/HOWTO?op=file&rev=1027&sc=1

Bin


> This brings me to my problem... I cannot get an IP
> address using dhclient...
>
> the procedure I follow is
>
> modprobe ieee80211_crypt ieee80211 ieee80211_crypt_wep
> ieee80211_crypt_ccmp ieee80211_crypt_tkip ieee80211softmac bcm43xx
>
> ifconfig eth1 up
> iwlist eth1 scan
>
> dhclient eth1
>
> When I run dhclient it seems to do an ifconfig eth1 down followed by
> an ifconfig eth1 up, which means that the iwlist scan results are lost
> and dhclient keeps searching for the dhcp server.
>
>
> I found that if I let dhclient run on one console and run iwlist eth1
> scan in another console then the dhclient immediately is able to get
> an IP address. So my question is... is there any option that I can
> pass to dhclient that will disable the up/down of interface if it is
> already up? Can someone please help?
>
> Shreyas.
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Shreyas Ananthan 

Hi Milan,

I am using Airport wireless card on an iBook 12" G4 and I have managed
to get bcm43xx driver working both with WEP and WPA, using the default
debian kernel. I downloaded the softmac-snapshot and bcm43xx snapshots
(Jan 15, 2006 snapshots) and compiled the ieee80211 modules from the
softmac-snapshot and use them instead of the ones in the
kernel. Giuseppe has a good summary of the procedure we followed to
get it working at http://www.fisica.unipa.it/~lavaget/ubuntuae/

I have found that iwlist scanning isn't very reliable. I sometimes
have to scan a couple of times before setting the essid using iwconfig
or wpa_supplicant. This brings me to my problem... I cannot get an IP
address using dhclient...

the procedure I follow is

modprobe ieee80211_crypt ieee80211 ieee80211_crypt_wep
ieee80211_crypt_ccmp ieee80211_crypt_tkip ieee80211softmac bcm43xx 

ifconfig eth1 up 
iwlist eth1 scan 

dhclient eth1 

When I run dhclient it seems to do an ifconfig eth1 down followed by
an ifconfig eth1 up, which means that the iwlist scan results are lost
and dhclient keeps searching for the dhcp server.


I found that if I let dhclient run on one console and run iwlist eth1
scan in another console then the dhclient immediately is able to get
an IP address. So my question is... is there any option that I can
pass to dhclient that will disable the up/down of interface if it is
already up? Can someone please help?

Shreyas. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Milan Toth 
heh guys,

progress there.

here are me steps:

1. because i was running 2.6.15 I do
$rm -rf /lib/modules/2.6.15-krachsna-2
2. configure kernel with IEEE80211
3. compile and install softmac-snapshot
4. compile and install bcm43xx

no progress

5. configure kernel without IEEE80211
6. compile and install softmac-snapshot
7. compile and install bcm43xx, but i have to disable
checking for IEEE80211 in bcm43xx.h

And wow, no problem with loading module.

But in most cases I have problem with scanning for AP.
Sometimes iwlist show me AP sometimes no. Any ideas? 
And I have one question it is posible to use WPA with
bcm43xx?

M.

p.s.: many thanks to all who developing this driver :)

Kasper Jordaens at Thu, Jan 19, 2006 at 04:27:42PM CET wrote:
> same here...
> 
> are you trying an airport extreme on a powerbook 12"???
> 
> 
> Kasper
> On 1/19/06, Milan Toth <[EMAIL PROTECTED]> wrote:
> > well,
> >
> > still no luck. kernel 2.6.15 without IEEE80211, with
> > softmac-snapshot, bcm43xx from checkouted from svn and still
> > the same problem :(
> >
> > Milan
> >
> > Emmanuel Galatoulas at Tue, Jan 17, 2006 at 11:17:52PM CET wrote:
> > > Milan Toth wrote:
> > >
> > > >no luck :(
> > > >
> > > >twoo diferent kernels 2.6.15-rc5 and 2.6.15.1 also your source
> > > >of bcm43xx and sofmac and no luck. When we can expect official
> > > >module in kernel?
> > > >
> > > >thanks for your help and time Ruben :)
> > > >
> > > >
> > > >
> > > Hi Milan
> > >
> > > i got curious after reading the posts by Ruben so
> > > I experimented a bit. I built the kernel 2.6.15 without the
> > > options regarding the ieee82011 modules,
> > > (here is the diff between my two configurations)
> > >
> > > < # Linux kernel version: 2.6.15
> > > < # Tue Jan 10 01:36:09 2006
> > > ---
> > > > # Linux kernel version: 2.6.15nowifi
> > > > # Mon Jan 16 23:37:17 2006
> > > 610,611c610,611
> > > < CONFIG_IEEE80211_CRYPT_CCMP=m
> > > < CONFIG_IEEE80211_CRYPT_TKIP=m
> > > ---
> > > > # CONFIG_IEEE80211_CRYPT_CCMP is not set
> > > > # CONFIG_IEEE80211_CRYPT_TKIP is not set
> > > 1083,1093c1083,1086
> > > < # CONFIG_IPW_DEBUG is not set
> > > < CONFIG_IPW2200=m
> > > < CONFIG_AIRO=m
> > > < CONFIG_HERMES=m
> > > < # CONFIG_APPLE_AIRPORT is not set
> > > < CONFIG_PLX_HERMES=m
> > > < CONFIG_TMD_HERMES=m
> > > < # CONFIG_NORTEL_HERMES is not set
> > > < CONFIG_PCI_HERMES=m
> > > < C< CONFIG_PCI_ATMEL=m
> > > ---
> > > > # CONFIG_IPW2200 is not set
> > > > # CONFIG_AIRO is not set
> > > > # CONFIG_HERMES is not set
> > > > # CONFIG_ATMEL is not set
> > > 1098,1099d1090
> > > < # CONFIG_PCMCIA_HERMES is not set
> > > < # CONFIG_PCMCIA_SPECTRUM is not set
> > > 1101d1091
> > > < # CONFIG_PCMCIA_ATMEL is not set
> > > 1108,1112c1098
> > > < CONFIG_HOSTAP=m
> > > < CONFIG_HOSTAP_FIRMWARE=y
> > > < CONFIG_HOSTAP_PLX=m
> > > < CONFIG_HOSTAP_PCI=m
> > > < CONFIG_HOSTAP_CS=m
> > > ---
> > > > # CONFIG_HOSTAP is not set
> > >
> > > I emphasise that in both cases i use KERNEL 2.6.15 
> > > (so I can't say about -rc7 or 2.6.15.1!!!)
> > >
> > > Then I tried to built bcm43xx first against the kernel's own ieee80211 
> > > stuff
> > > and second against the softmac-snapshot. The result was that in the
> > > first case
> > > the module just doesn't build which a little search shows that is due
> > > not only that
> > > kernel-source files for ieee* are not identical with those in
> > > softmac-snapshot!
> > > For instance:
> > >
> > > diff ieee80211_crypt.h
> > > /usr/src/softmac-snapshot/include/net/ieee80211_crypt.h
> > > 26c26,28
> > > < #include 
> > > ---
> > > > #include 
> > > > #include 
> > > > #include 
> > > 31a34,36
> > > > struct sk_buff;
> > > > struct module;
> > > >
> > > 89a95,96
> > > > struct ieee80211_device;
> > >
> > > and
> > >
> > > # diff ieee80211.h /usr/src/softmac-snapshot/include/net/ieee80211.h
> > > 366,367c366,368
> > > <  *   information for frames received.  Not setting these will not
> > > cause
> > > <  *   any adverse affects. */
> > > ---
> > > >  *   information for frames received.
> > > >  *   For ieee80211_rx_mgt, you need to set at least the 'len'
> > > parameter.
> > > >  */
> > > 1090a1092
> > > > /* make sure to set stats->len */
> > > 1122a1125,1132
> > > > extern int ieee80211_wx_set_auth(struct net_device *dev,
> > > >struct iw_request_info *info,
> > > >union iwreq_data *wrqu,
> > > >char *extra);
> > > > extern int ieee80211_wx_get_auth(struct net_device *dev,
> > > >struct iw_request_info *info,
> > > >union iwreq_data *wrqu,
> > > >char *extra);
> > >
> > >
> > > but of also because ieee80211softmac.h simply does not exist at all in
> > > kernel-source.
> > > which must be also the explanation of getting various error mes

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Kasper Jordaens 
same here...

are you trying an airport extreme on a powerbook 12"???


Kasper
On 1/19/06, Milan Toth <[EMAIL PROTECTED]> wrote:
> well,
>
> still no luck. kernel 2.6.15 without IEEE80211, with
> softmac-snapshot, bcm43xx from checkouted from svn and still
> the same problem :(
>
> Milan
>
> Emmanuel Galatoulas at Tue, Jan 17, 2006 at 11:17:52PM CET wrote:
> > Milan Toth wrote:
> >
> > >no luck :(
> > >
> > >twoo diferent kernels 2.6.15-rc5 and 2.6.15.1 also your source
> > >of bcm43xx and sofmac and no luck. When we can expect official
> > >module in kernel?
> > >
> > >thanks for your help and time Ruben :)
> > >
> > >
> > >
> > Hi Milan
> >
> > i got curious after reading the posts by Ruben so
> > I experimented a bit. I built the kernel 2.6.15 without the
> > options regarding the ieee82011 modules,
> > (here is the diff between my two configurations)
> >
> > < # Linux kernel version: 2.6.15
> > < # Tue Jan 10 01:36:09 2006
> > ---
> > > # Linux kernel version: 2.6.15nowifi
> > > # Mon Jan 16 23:37:17 2006
> > 610,611c610,611
> > < CONFIG_IEEE80211_CRYPT_CCMP=m
> > < CONFIG_IEEE80211_CRYPT_TKIP=m
> > ---
> > > # CONFIG_IEEE80211_CRYPT_CCMP is not set
> > > # CONFIG_IEEE80211_CRYPT_TKIP is not set
> > 1083,1093c1083,1086
> > < # CONFIG_IPW_DEBUG is not set
> > < CONFIG_IPW2200=m
> > < CONFIG_AIRO=m
> > < CONFIG_HERMES=m
> > < # CONFIG_APPLE_AIRPORT is not set
> > < CONFIG_PLX_HERMES=m
> > < CONFIG_TMD_HERMES=m
> > < # CONFIG_NORTEL_HERMES is not set
> > < CONFIG_PCI_HERMES=m
> > < C< CONFIG_PCI_ATMEL=m
> > ---
> > > # CONFIG_IPW2200 is not set
> > > # CONFIG_AIRO is not set
> > > # CONFIG_HERMES is not set
> > > # CONFIG_ATMEL is not set
> > 1098,1099d1090
> > < # CONFIG_PCMCIA_HERMES is not set
> > < # CONFIG_PCMCIA_SPECTRUM is not set
> > 1101d1091
> > < # CONFIG_PCMCIA_ATMEL is not set
> > 1108,1112c1098
> > < CONFIG_HOSTAP=m
> > < CONFIG_HOSTAP_FIRMWARE=y
> > < CONFIG_HOSTAP_PLX=m
> > < CONFIG_HOSTAP_PCI=m
> > < CONFIG_HOSTAP_CS=m
> > ---
> > > # CONFIG_HOSTAP is not set
> >
> > I emphasise that in both cases i use KERNEL 2.6.15 
> > (so I can't say about -rc7 or 2.6.15.1!!!)
> >
> > Then I tried to built bcm43xx first against the kernel's own ieee80211 stuff
> > and second against the softmac-snapshot. The result was that in the
> > first case
> > the module just doesn't build which a little search shows that is due
> > not only that
> > kernel-source files for ieee* are not identical with those in
> > softmac-snapshot!
> > For instance:
> >
> > diff ieee80211_crypt.h
> > /usr/src/softmac-snapshot/include/net/ieee80211_crypt.h
> > 26c26,28
> > < #include 
> > ---
> > > #include 
> > > #include 
> > > #include 
> > 31a34,36
> > > struct sk_buff;
> > > struct module;
> > >
> > 89a95,96
> > > struct ieee80211_device;
> >
> > and
> >
> > # diff ieee80211.h /usr/src/softmac-snapshot/include/net/ieee80211.h
> > 366,367c366,368
> > <  *   information for frames received.  Not setting these will not
> > cause
> > <  *   any adverse affects. */
> > ---
> > >  *   information for frames received.
> > >  *   For ieee80211_rx_mgt, you need to set at least the 'len'
> > parameter.
> > >  */
> > 1090a1092
> > > /* make sure to set stats->len */
> > 1122a1125,1132
> > > extern int ieee80211_wx_set_auth(struct net_device *dev,
> > >struct iw_request_info *info,
> > >union iwreq_data *wrqu,
> > >char *extra);
> > > extern int ieee80211_wx_get_auth(struct net_device *dev,
> > >struct iw_request_info *info,
> > >union iwreq_data *wrqu,
> > >char *extra);
> >
> >
> > but of also because ieee80211softmac.h simply does not exist at all in
> > kernel-source.
> > which must be also the explanation of getting various error messages
> > (check with dmesg)
> > So it is not without reason that the README file in bcm43xx states
> > explicitly that you need to compile against
> > SOFTMAC source and not the kernel-source made respective modules!
> >
> > I tried also another combination building the kernel both WITHOUT and
> > WITH the ieee80211 modules
> > and then  built the bcm43xx against softmac-snapshot on top!!!. Then I
> > noticed that
> > in the first case (kernel WITHOUT ieee80211 related modules) compiling
> > the bcm43xx module (I repeat against softmac-snapshot!) failed (perhaps
> > due to some incompatibilities of the rest of the kernel stuff???)
> > while in the second case (kernel built WITH ieee80211 related modules)
> > the module did compile eventually
> > because the softmac stuff essentially is "overwritting" kernel's own
> > original ieee80211 stuff
> > Which means that in that case the ieee80211 modules are just the
> > softmac-snapshot's stuff and not the
> > original kernel's !!!
> >
> > As a conclusion, then, I think that if someone sticks with kernel 2.6.15
> > and the sof

Re: bcm43xx finally working, with encryption too!!!

2006-01-19 Thread Milan Toth 
well,

still no luck. kernel 2.6.15 without IEEE80211, with
softmac-snapshot, bcm43xx from checkouted from svn and still
the same problem :(

Milan

Emmanuel Galatoulas at Tue, Jan 17, 2006 at 11:17:52PM CET wrote:
> Milan Toth wrote:
> 
> >no luck :(
> >
> >twoo diferent kernels 2.6.15-rc5 and 2.6.15.1 also your source
> >of bcm43xx and sofmac and no luck. When we can expect official
> >module in kernel?
> >
> >thanks for your help and time Ruben :)
> >
> > 
> >
> Hi Milan
> 
> i got curious after reading the posts by Ruben so
> I experimented a bit. I built the kernel 2.6.15 without the
> options regarding the ieee82011 modules,
> (here is the diff between my two configurations)
> 
> < # Linux kernel version: 2.6.15
> < # Tue Jan 10 01:36:09 2006
> ---
> > # Linux kernel version: 2.6.15nowifi
> > # Mon Jan 16 23:37:17 2006
> 610,611c610,611
> < CONFIG_IEEE80211_CRYPT_CCMP=m
> < CONFIG_IEEE80211_CRYPT_TKIP=m
> ---
> > # CONFIG_IEEE80211_CRYPT_CCMP is not set
> > # CONFIG_IEEE80211_CRYPT_TKIP is not set
> 1083,1093c1083,1086
> < # CONFIG_IPW_DEBUG is not set
> < CONFIG_IPW2200=m
> < CONFIG_AIRO=m
> < CONFIG_HERMES=m
> < # CONFIG_APPLE_AIRPORT is not set
> < CONFIG_PLX_HERMES=m
> < CONFIG_TMD_HERMES=m
> < # CONFIG_NORTEL_HERMES is not set
> < CONFIG_PCI_HERMES=m
> < C< CONFIG_PCI_ATMEL=m
> ---
> > # CONFIG_IPW2200 is not set
> > # CONFIG_AIRO is not set
> > # CONFIG_HERMES is not set
> > # CONFIG_ATMEL is not set
> 1098,1099d1090
> < # CONFIG_PCMCIA_HERMES is not set
> < # CONFIG_PCMCIA_SPECTRUM is not set
> 1101d1091
> < # CONFIG_PCMCIA_ATMEL is not set
> 1108,1112c1098
> < CONFIG_HOSTAP=m
> < CONFIG_HOSTAP_FIRMWARE=y
> < CONFIG_HOSTAP_PLX=m
> < CONFIG_HOSTAP_PCI=m
> < CONFIG_HOSTAP_CS=m
> ---
> > # CONFIG_HOSTAP is not set
> 
> I emphasise that in both cases i use KERNEL 2.6.15 
> (so I can't say about -rc7 or 2.6.15.1!!!)
> 
> Then I tried to built bcm43xx first against the kernel's own ieee80211 stuff
> and second against the softmac-snapshot. The result was that in the 
> first case
> the module just doesn't build which a little search shows that is due 
> not only that
> kernel-source files for ieee* are not identical with those in 
> softmac-snapshot!
> For instance:
> 
> diff ieee80211_crypt.h 
> /usr/src/softmac-snapshot/include/net/ieee80211_crypt.h
> 26c26,28
> < #include 
> ---
> > #include 
> > #include 
> > #include 
> 31a34,36
> > struct sk_buff;
> > struct module;
> >
> 89a95,96
> > struct ieee80211_device;
> 
> and
> 
> # diff ieee80211.h /usr/src/softmac-snapshot/include/net/ieee80211.h
> 366,367c366,368
> <  *   information for frames received.  Not setting these will not 
> cause
> <  *   any adverse affects. */
> ---
> >  *   information for frames received.
> >  *   For ieee80211_rx_mgt, you need to set at least the 'len' 
> parameter.
> >  */
> 1090a1092
> > /* make sure to set stats->len */
> 1122a1125,1132
> > extern int ieee80211_wx_set_auth(struct net_device *dev,
> >struct iw_request_info *info,
> >union iwreq_data *wrqu,
> >char *extra);
> > extern int ieee80211_wx_get_auth(struct net_device *dev,
> >struct iw_request_info *info,
> >union iwreq_data *wrqu,
> >char *extra);
> 
> 
> but of also because ieee80211softmac.h simply does not exist at all in 
> kernel-source.
> which must be also the explanation of getting various error messages 
> (check with dmesg)
> So it is not without reason that the README file in bcm43xx states 
> explicitly that you need to compile against
> SOFTMAC source and not the kernel-source made respective modules!
> 
> I tried also another combination building the kernel both WITHOUT and 
> WITH the ieee80211 modules
> and then  built the bcm43xx against softmac-snapshot on top!!!. Then I 
> noticed that
> in the first case (kernel WITHOUT ieee80211 related modules) compiling 
> the bcm43xx module (I repeat against softmac-snapshot!) failed (perhaps 
> due to some incompatibilities of the rest of the kernel stuff???)
> while in the second case (kernel built WITH ieee80211 related modules) 
> the module did compile eventually
> because the softmac stuff essentially is "overwritting" kernel's own 
> original ieee80211 stuff
> Which means that in that case the ieee80211 modules are just the 
> softmac-snapshot's stuff and not the
> original kernel's !!!
> 
> As a conclusion, then, I think that if someone sticks with kernel 2.6.15 
> and the softmac-snapshot source,
> there would be no problems to encounter anymore!
> 
> (PS. sorry for the length of the reply, but I felt that I had to share 
> all that!)
> 
> best regards
> 
> Emmanuel Galatoulas

-- 
Milan Toth  .''`.
http://milan.toth-online.com   : :'  :
[EMAIL PROTECTED]  `. `'`
 `-
MATH AND ALCOHOL DON'T MIX!
Pl

Re: bcm43xx finally working, with encryption too!!!

2006-01-17 Thread Emmanuel Galatoulas 

Milan Toth wrote:


no luck :(

twoo diferent kernels 2.6.15-rc5 and 2.6.15.1 also your source
of bcm43xx and sofmac and no luck. When we can expect official
module in kernel?

thanks for your help and time Ruben :)

 


Hi Milan

i got curious after reading the posts by Ruben so
I experimented a bit. I built the kernel 2.6.15 without the
options regarding the ieee82011 modules,
(here is the diff between my two configurations)

< # Linux kernel version: 2.6.15
< # Tue Jan 10 01:36:09 2006
---
> # Linux kernel version: 2.6.15nowifi
> # Mon Jan 16 23:37:17 2006
610,611c610,611
< CONFIG_IEEE80211_CRYPT_CCMP=m
< CONFIG_IEEE80211_CRYPT_TKIP=m
---
> # CONFIG_IEEE80211_CRYPT_CCMP is not set
> # CONFIG_IEEE80211_CRYPT_TKIP is not set
1083,1093c1083,1086
< # CONFIG_IPW_DEBUG is not set
< CONFIG_IPW2200=m
< CONFIG_AIRO=m
< CONFIG_HERMES=m
< # CONFIG_APPLE_AIRPORT is not set
< CONFIG_PLX_HERMES=m
< CONFIG_TMD_HERMES=m
< # CONFIG_NORTEL_HERMES is not set
< CONFIG_PCI_HERMES=m
< C< CONFIG_PCI_ATMEL=m
---
> # CONFIG_IPW2200 is not set
> # CONFIG_AIRO is not set
> # CONFIG_HERMES is not set
> # CONFIG_ATMEL is not set
1098,1099d1090
< # CONFIG_PCMCIA_HERMES is not set
< # CONFIG_PCMCIA_SPECTRUM is not set
1101d1091
< # CONFIG_PCMCIA_ATMEL is not set
1108,1112c1098
< CONFIG_HOSTAP=m
< CONFIG_HOSTAP_FIRMWARE=y
< CONFIG_HOSTAP_PLX=m
< CONFIG_HOSTAP_PCI=m
< CONFIG_HOSTAP_CS=m
---
> # CONFIG_HOSTAP is not set

I emphasise that in both cases i use KERNEL 2.6.15 
(so I can't say about -rc7 or 2.6.15.1!!!)

Then I tried to built bcm43xx first against the kernel's own ieee80211 stuff
and second against the softmac-snapshot. The result was that in the 
first case
the module just doesn't build which a little search shows that is due 
not only that
kernel-source files for ieee* are not identical with those in 
softmac-snapshot!

For instance:

diff ieee80211_crypt.h 
/usr/src/softmac-snapshot/include/net/ieee80211_crypt.h

26c26,28
< #include 
---
> #include 
> #include 
> #include 
31a34,36
> struct sk_buff;
> struct module;
>
89a95,96
> struct ieee80211_device;

and

# diff ieee80211.h /usr/src/softmac-snapshot/include/net/ieee80211.h
366,367c366,368
<  *   information for frames received.  Not setting these will not 
cause

<  *   any adverse affects. */
---
>  *   information for frames received.
>  *   For ieee80211_rx_mgt, you need to set at least the 'len' 
parameter.

>  */
1090a1092
> /* make sure to set stats->len */
1122a1125,1132
> extern int ieee80211_wx_set_auth(struct net_device *dev,
>struct iw_request_info *info,
>union iwreq_data *wrqu,
>char *extra);
> extern int ieee80211_wx_get_auth(struct net_device *dev,
>struct iw_request_info *info,
>union iwreq_data *wrqu,
>char *extra);


but of also because ieee80211softmac.h simply does not exist at all in 
kernel-source.
which must be also the explanation of getting various error messages 
(check with dmesg)
So it is not without reason that the README file in bcm43xx states 
explicitly that you need to compile against

SOFTMAC source and not the kernel-source made respective modules!

I tried also another combination building the kernel both WITHOUT and 
WITH the ieee80211 modules
and then  built the bcm43xx against softmac-snapshot on top!!!. Then I 
noticed that
in the first case (kernel WITHOUT ieee80211 related modules) compiling 
the bcm43xx module (I repeat against softmac-snapshot!) failed (perhaps 
due to some incompatibilities of the rest of the kernel stuff???)
while in the second case (kernel built WITH ieee80211 related modules) 
the module did compile eventually
because the softmac stuff essentially is "overwritting" kernel's own 
original ieee80211 stuff
Which means that in that case the ieee80211 modules are just the 
softmac-snapshot's stuff and not the

original kernel's !!!

As a conclusion, then, I think that if someone sticks with kernel 2.6.15 
and the softmac-snapshot source,

there would be no problems to encounter anymore!

(PS. sorry for the length of the reply, but I felt that I had to share 
all that!)


best regards

Emmanuel Galatoulas


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-16 Thread Milan Toth 
no luck :(

twoo diferent kernels 2.6.15-rc5 and 2.6.15.1 also your source
of bcm43xx and sofmac and no luck. When we can expect official
module in kernel?

thanks for your help and time Ruben :)

Ruben at Mon, Jan 16, 2006 at 04:19:10PM CET wrote:
> 
> At Mon, 16 Jan 2006 14:49:41 +0100, Milan Toth wrote:
> > 
> > OK. So I download a 2.6.15.1 from kernel.org disbale Generic
> > IEEE 802.11 Networking Stack and try to compile softmac-snapshot
> > but I'v got error that I dont have IEEE 802.11 compiled into
> > kernel. So I enbale it compile softmac with this warnning: 
> 
> Ok.. I just answered your mail and then re-read this.  You got the
> error about not having IEEE 802.11 enabled in the kernel from
> compiling bcm43xx, not from the softmac-snapshot, right?  I remember
> that I needed to disable something from bcm43xx...
> 
> ah... got it.. in bcm43xx.h (at the end of the file):
> 
> /*   < need to add this line
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 15)  
> # error "The bcm43xx driver does not support kernels < 2.6.15"  
> # error "The driver will _NOT_ compile on your kernel. Please upgrade to the 
> latest 2.6 kernel."
> # error "DO NOT COMPLAIN ABOUT BUGS. UPDATE FIRST AND TRY AGAIN."
> #else
> # if !defined(CONFIG_IEEE80211_MODULE) && !defined(CONFIG_IEEE80211)
> #  error "Generic IEEE 802.11 Networking Stack (CONFIG_IEEE80211) not 
> available."
> # endif  
> #endif
> #ifdef IEEE80211SOFTMAC_API 
> # if IEEE80211SOFTMAC_API != 0  
> #  warning "Incompatible SoftMAC subsystem installed."
> # endif   
>
> #else   
> # error "The bcm43xx driver requires the SoftMAC subsystem."
> # error "SEE >>http://softmac.sipsolutions.net/<<"
> #endif
>  > need to add this line */
> 
> I commented out the checks about the softmac stuff.  Since the softmac
> stuff is compiled outside the kernel, it means it's still there, but
> the CONFIG_IEEE80211_MODULE and the CONFIG_IEEE80211 were not
> defined. I assume that's because it's compiled outside of the kernel.
> So I just commented out the whole block, since I know those conditions
> are fullfilled.
> 
> So I guess that's why it's not compiling on your system.  Just try to
> comment those out and see if you get it to work then.  The in-kernel
> IEEE80211 needs to be disabled, I assume you're using the in-kernel
> IEEE80211 instead of the one added with the softmac snapshot and
> that's the reason that the bcm43xx is not working.
> 
> I hope you get it working with that change.  Otherwise, you can read
> on and try the snapshots I used (and which compile fine as is on my
> machine).
> 
> Ruben
> 
> --
> 
> > *** Warning: "wireless_send_event"
> > *** 
> > [/home/data/src/softmac-snapshot/net/ieee80211/softmac/ieee80211softmac.ko]
> > *** undefined!
> 
> yeah, I remember I got a number of warnings in both softmac and
> bcm43xx.  I got more warnings even.
> 
> > then:
> > export SOFTMAC_DIR=/home/data/src/softmac-snapshot
> > 
> > and compile the bcm43xx driver
> > with this warnnings: 
> > *** Warning: "free_ieee80211softmac"
> > [/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
> > [...]
> 
> I did get those warnings too...
> 
> > and finaly when I try to modprobe the bcm4300 I'v got this
> > error:
> > [EMAIL PROTECTED]/home/data/src/bcm43xx/driver] sudo
> > modprobe bcm43xx 
> > WARNING: Error inserting ieee80211softmac
> > (/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/ieee80211softmac/ieee80211softmac.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> > FATAL: Error inserting bcm43xx
> > (/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/bcm43xx/bcm43xx.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> 
> well, no error here in my case.
> 
> > help me please :(
> 
> I don't know much about solving this. Maybe you just have bad luck in
> that the bcm43xx svn isn't compatible with the current softmac
> snapshot...?
> 
> I put the code I'm using right now, from 12/01, online.  I use this
> with a 2.6.15 kernel.
> http://www.student.kuleuven.ac.be/~m9505736/bcm43xx-1051.tar.bz2
> http://www.student.kuleuven.ac.be/~m9505736/softmac-120106.tar.bz2
> 
> 
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 

-- 
Milan Toth  .''`.
http://milan.toth-online.com   : :'  :
[EMAIL PROTECTED]  `. `'`
 `-
MATH AND ALCOHOL DON'T MIX!
Please don't drink and derive.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-16 Thread Ruben 

At Mon, 16 Jan 2006 14:49:41 +0100, Milan Toth wrote:
> 
> OK. So I download a 2.6.15.1 from kernel.org disbale Generic
> IEEE 802.11 Networking Stack and try to compile softmac-snapshot
> but I'v got error that I dont have IEEE 802.11 compiled into
> kernel. So I enbale it compile softmac with this warnning: 

Ok.. I just answered your mail and then re-read this.  You got the
error about not having IEEE 802.11 enabled in the kernel from
compiling bcm43xx, not from the softmac-snapshot, right?  I remember
that I needed to disable something from bcm43xx...

ah... got it.. in bcm43xx.h (at the end of the file):

/*   < need to add this line
#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 15)  
# error "The bcm43xx driver does not support kernels < 2.6.15"  
# error "The driver will _NOT_ compile on your kernel. Please upgrade to the 
latest 2.6 kernel."
# error "DO NOT COMPLAIN ABOUT BUGS. UPDATE FIRST AND TRY AGAIN."
#else
# if !defined(CONFIG_IEEE80211_MODULE) && !defined(CONFIG_IEEE80211)
#  error "Generic IEEE 802.11 Networking Stack (CONFIG_IEEE80211) not 
available."
# endif  
#endif
#ifdef IEEE80211SOFTMAC_API 
# if IEEE80211SOFTMAC_API != 0  
#  warning "Incompatible SoftMAC subsystem installed."
# endif 
 
#else   
# error "The bcm43xx driver requires the SoftMAC subsystem."
# error "SEE >>http://softmac.sipsolutions.net/<<"
#endif
 > need to add this line */

I commented out the checks about the softmac stuff.  Since the softmac
stuff is compiled outside the kernel, it means it's still there, but
the CONFIG_IEEE80211_MODULE and the CONFIG_IEEE80211 were not
defined. I assume that's because it's compiled outside of the kernel.
So I just commented out the whole block, since I know those conditions
are fullfilled.

So I guess that's why it's not compiling on your system.  Just try to
comment those out and see if you get it to work then.  The in-kernel
IEEE80211 needs to be disabled, I assume you're using the in-kernel
IEEE80211 instead of the one added with the softmac snapshot and
that's the reason that the bcm43xx is not working.

I hope you get it working with that change.  Otherwise, you can read
on and try the snapshots I used (and which compile fine as is on my
machine).

Ruben

--

> *** Warning: "wireless_send_event"
> *** 
> [/home/data/src/softmac-snapshot/net/ieee80211/softmac/ieee80211softmac.ko]
> *** undefined!

yeah, I remember I got a number of warnings in both softmac and
bcm43xx.  I got more warnings even.

> then:
> export SOFTMAC_DIR=/home/data/src/softmac-snapshot
> 
> and compile the bcm43xx driver
> with this warnnings: 
> *** Warning: "free_ieee80211softmac"
> [/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
> [...]

I did get those warnings too...

> and finaly when I try to modprobe the bcm4300 I'v got this
> error:
> [EMAIL PROTECTED]/home/data/src/bcm43xx/driver] sudo
> modprobe bcm43xx 
> WARNING: Error inserting ieee80211softmac
> (/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/ieee80211softmac/ieee80211softmac.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting bcm43xx
> (/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/bcm43xx/bcm43xx.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)

well, no error here in my case.

> help me please :(

I don't know much about solving this. Maybe you just have bad luck in
that the bcm43xx svn isn't compatible with the current softmac
snapshot...?

I put the code I'm using right now, from 12/01, online.  I use this
with a 2.6.15 kernel.
http://www.student.kuleuven.ac.be/~m9505736/bcm43xx-1051.tar.bz2
http://www.student.kuleuven.ac.be/~m9505736/softmac-120106.tar.bz2


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-16 Thread Milan Toth 
Ruben at Mon, Jan 16, 2006 at 01:01:37PM CET wrote:
> 
> At Mon, 16 Jan 2006 10:22:52 +0100, Milan Toth wrote:
> > 
> > > well i have got eventually the AirPort card working WITH WEP SECURITY 
> > > ON!!!
> > 
> > should I only update bcm43xx and softmac source and WEP will
> > work form me?
> 
> Yes, I used the svn from bcm43xx (you could also use a snapshot) and a
> snapshot of softmac.  You just need to disable ieee80211 in the
> (vanilla) kernel, since the modified ieee80211 is included in the
> softmac snapshot.  A "make install" will install the needed kernel
> modules in /lib/modules for both softmac and bcm43xx.

OK. So I download a 2.6.15.1 from kernel.org disbale Generic
IEEE 802.11 Networking Stack and try to compile softmac-snapshot
but I'v got error that I dont have IEEE 802.11 compiled into
kernel. So I enbale it compile softmac with this warnning: 

*** Warning: "wireless_send_event" 
[/home/data/src/softmac-snapshot/net/ieee80211/softmac/ieee80211softmac.ko] 
undefined!

then:
export SOFTMAC_DIR=/home/data/src/softmac-snapshot

and compile the bcm43xx driver
with this warnnings: 
*** Warning: "free_ieee80211softmac"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_stop"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_set_genie"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_set_wap"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_get_essid"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_get_rate"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_get_wap"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_set_essid"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_start"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_get_genie"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_get_scan_results"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211_wx_get_auth"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_trigger_scan"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "alloc_ieee80211softmac"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211_wx_set_auth"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!
*** Warning: "ieee80211softmac_wx_set_rate"
[/home/data/src/bcm43xx/driver/bcm43xx.ko] undefined!

and finaly when I try to modprobe the bcm4300 I'v got this
error:
[EMAIL PROTECTED]/home/data/src/bcm43xx/driver] sudo
modprobe bcm43xx 
WARNING: Error inserting ieee80211softmac
(/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/ieee80211softmac/ieee80211softmac.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting bcm43xx
(/lib/modules/2.6.15.1-krachsna-2/kernel/drivers/net/bcm43xx/bcm43xx.ko):
Unknown symbol in module, or unknown parameter (see dmesg)


help me please :(

> 
> Then you do something like the following:
> ---
> #!/bin/bash
> ifconfig eth1 down
> ifconfig eth1 up
> iwconfig eth1 rate 11M
> iwconfig eth1 essid fifi
> iwconfig eth1 key 1230123012301230123012302
> dhclient eth1
> ---
> 
> Adapt everything to your configuration of course, maybe a higher rate
> than 11M is possible according to circumstances, but it works very
> well in my case.  A higher rate gives me trouble with dhcp.  But for
> the rest it is very stable. (and now the connection works immediately)
> 

-- 
Milan Toth  .''`.
http://milan.toth-online.com   : :'  :
[EMAIL PROTECTED]  `. `'`
 `-
MATH AND ALCOHOL DON'T MIX!
Please don't drink and derive.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-16 Thread Ruben 

At Mon, 16 Jan 2006 10:22:52 +0100, Milan Toth wrote:
> 
> > well i have got eventually the AirPort card working WITH WEP SECURITY ON!!!
> 
> should I only update bcm43xx and softmac source and WEP will
> work form me?

Yes, I used the svn from bcm43xx (you could also use a snapshot) and a
snapshot of softmac.  You just need to disable ieee80211 in the
(vanilla) kernel, since the modified ieee80211 is included in the
softmac snapshot.  A "make install" will install the needed kernel
modules in /lib/modules for both softmac and bcm43xx.

Then you do something like the following:
---
#!/bin/bash
ifconfig eth1 down
ifconfig eth1 up
iwconfig eth1 rate 11M
iwconfig eth1 essid fifi
iwconfig eth1 key 1230123012301230123012302
dhclient eth1
---

Adapt everything to your configuration of course, maybe a higher rate
than 11M is possible according to circumstances, but it works very
well in my case.  A higher rate gives me trouble with dhcp.  But for
the rest it is very stable. (and now the connection works immediately)

Ruben

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bcm43xx finally working, with encryption too!!!

2006-01-16 Thread Milan Toth 
> well i have got eventually the AirPort card working WITH WEP SECURITY ON!!!

should I only update bcm43xx and softmac source and WEP will
work form me?


> i guess it  was basically a driver issue cos using the latest bcm43xx driver
> (actually  bcm43xx-20060115.tar.bz) as welll as today's softmac-snapshot
> both the driver and the modules were compiled smoothly (despite some
> warning messages in bcm43xx!)
> Perhaps it was also a matter of the AppleAirport2 firmware file
> ie. the MacOS X file 
> /System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2
> the latest one from MacOS X 10.4.4 did not produce the error messages 
> that earlier version did
> when running fwcutter!
> 
> At any rate, the thing is that the modules run OK, encryotion does work
> (at the moment using WEP key 64-bit hex)
> and also without the nasty hang ups and so on that  I observed  with the 
> earlier versions
> (eg, if  you were  deactivating the wired interface eth0 and then were 
> trying to activate
> the wireless one, the system could hang, or  evev if you were just 
> unplugging the ethernet plug!!!)
> 
> so a big thanks to the community serving this wonderful work
> one more proof of what a power the community is!!!
> 
> (and yes this was the last main reason for still using MacOS X , sorry)
> (OK, if only the sound drivers was working fully too)
> 
> (PS. this mail is of course being sent wirelessly!!!)
> 

-- 
Milan Toth  .''`.
http://milan.toth-online.com   : :'  :
[EMAIL PROTECTED]  `. `'`
 `-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

bcm43xx finally working, with encryption too!!!

2006-01-15 Thread Emmanuel Galatoulas 

Ruben wrote:


At Wed, 11 Jan 2006 09:39:01 +1100, Aaron Kerr wrote:
 


Thanks. I will try waiting a few minutes after setting up the connection.
   



I timed it this morning, and it only worked after 4 minutes.  It's
possible this has something to do with my access point.
Authentication and association with the AP happens almost immediately.

 


Your delays when running route or netstat could be a DNS lookup failure.
Try "netstat -rn" which will not try to translate IP addresses to names.
   



Thanks (and thanks to Michael)... that was indeed the reason.

Ruben

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm


 


well i have got eventually the AirPort card working WITH WEP SECURITY ON!!!
i guess it  was basically a driver issue cos using the latest bcm43xx driver
(actually  bcm43xx-20060115.tar.bz) as welll as today's softmac-snapshot
both the driver and the modules were compiled smoothly (despite some
warning messages in bcm43xx!)
Perhaps it was also a matter of the AppleAirport2 firmware file
ie. the MacOS X file 
/System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2
the latest one from MacOS X 10.4.4 did not produce the error messages 
that earlier version did

when running fwcutter!

At any rate, the thing is that the modules run OK, encryotion does work
(at the moment using WEP key 64-bit hex)
and also without the nasty hang ups and so on that  I observed  with the 
earlier versions
(eg, if  you were  deactivating the wired interface eth0 and then were 
trying to activate
the wireless one, the system could hang, or  evev if you were just 
unplugging the ethernet plug!!!)


so a big thanks to the community serving this wonderful work
one more proof of what a power the community is!!!

(and yes this was the last main reason for still using MacOS X , sorry)
(OK, if only the sound drivers was working fully too)

(PS. this mail is of course being sent wirelessly!!!)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]