1 Jun 2010 04:17
1 Jun 2010 10:39
Re: Problem with b43
Also me... I sent a message about this problem but it was blocked.
I have this problem olny with multi-AP networks, in dmesg I can see that it continue to changes the AP until they ends to responds. (At my home, with a digicom ADSL router, the wifi works)
Martino
--
Remember: with great power comes great current squared times resistance.
2010/6/1 William Bourque <william.bourque-scC8bbJcJLCw5LPnMra/2Q@public.gmane.org>
Just saying, I have a similar problem... I tried to post twice about it
on the list since 2 weeks but the mails keep getting moderated (and
never unmoderated) because of "suspicious content".
- William
_______________________________________________
b43-dev mailing list
b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
http://lists.infradead.org/mailman/listinfo/b43-dev
--
Remember: with great power comes great current squared times resistance.
_______________________________________________ b43-dev mailing list b43-dev@... http://lists.infradead.org/mailman/listinfo/b43-dev
6 Jun 2010 10:02
BCM4318 Airforce one
Hi ,
I had my wireless card working nicely since the first installation (i just remember that i had to do some stuff, which i cant remember now but once i did i got it working). I have more then 8 months and never had problems. Yesterday i installed the following, to try to get some other application working:
sudo apt-get install linux-headers-`uname -r` linux-source kernel-package libncurses5-dev fakeroot wget bzip2
I realized after that my wireless card stopped working, after this command.
Then i tried to rollback with the command:
sudo apt-get remove linux-headers-`uname -r` linux-source kernel-package libncurses5-dev fakeroot wget bzip2
Still no sucess. My card is still not working. I tried to reinstall b43-fwcutter, and still no sucess....
Does anyone have a suggestion?
Thanks,
Felipe
_______________________________________________ b43-dev mailing list b43-dev@... http://lists.infradead.org/mailman/listinfo/b43-dev
6 Jun 2010 10:08
BCM4318 Airforce one
Hi,
I forgot to mention on my last email that after removing that packages, network manager now finds a strange inexistent wireless network called ( Áý).
Thanks,
Felipe
_______________________________________________ b43-dev mailing list b43-dev@... http://lists.infradead.org/mailman/listinfo/b43-dev
6 Jun 2010 16:18
Re: BCM4318 Airforce one
On 06/06/2010 03:08 AM, Felipe J wrote: > Hi, > > I forgot to mention on my last email that after removing that packages, > network manager now finds a strange inexistent wireless network called ( > Áý). Please post the entire dmesg output on pastebin and post a link. Installing new packages on whatever distro uses apt-get should cause no problems with b43, but you may have messed up some component that is needed for networking. That strange network name may be a clue. Larry
7 Jun 2010 12:21
Re: BCM4318 Airforce one
Thanks for your reply! Right after sending the email, I manage to solve
it, by uninstalling the driver and reinstalling again...
Felipe
Em 06/06/2010 04:18 PM, Larry Finger escreveu:
Felipe
Em 06/06/2010 04:18 PM, Larry Finger escreveu:
On 06/06/2010 03:08 AM, Felipe J wrote:Hi, I forgot to mention on my last email that after removing that packages, network manager now finds a strange inexistent wireless network called ( Áý).Please post the entire dmesg output on pastebin and post a link. Installing new packages on whatever distro uses apt-get should cause no problems with b43, but you may have messed up some component that is needed for networking. That strange network name may be a clue. Larry
_______________________________________________ b43-dev mailing list b43-dev@... http://lists.infradead.org/mailman/listinfo/b43-dev
7 Jun 2010 20:33
BCM5354
Hello all, I currently work for a company that is using OpenWRT, with linux 2.4, on a BCM5354. We really want to move to OpenWRT with linux 2.6 using the b43 driver on this chip. Initial test results show that b43 seems to work in client / Adhoc mode, but not in AP mode. Unfortunately, I have been unable to ascertain the status of the b43 driver with respect to this chip. Can anyone confirm whether it's fully functional under this platform? If not, what's left to be done ? Thanks, Robert Hazbun
7 Jun 2010 20:48
Re: BCM5354
On 06/07/2010 01:33 PM, Robert Hazbun wrote: > Hello all, > > I currently work for a company that is using OpenWRT, with linux 2.4, on > a BCM5354. We really want to move to OpenWRT with linux 2.6 using the > b43 driver on this chip. Initial test results show that b43 seems to > work in client / Adhoc mode, but not in AP mode. Unfortunately, I have > been unable to ascertain the status of the b43 driver with respect to > this chip. > > Can anyone confirm whether it's fully functional under this platform? If > not, what's left to be done ? I believe the BCM5354 has an LP PHY. As such, it should be supported by any 2.6.32, or later, kernel. AFAIK, no such device has been tested by a developer. My tests with a BCM4312, which also has an LP PHY, show that b43/mac80211 will function as an AP using recent versions of hostapd. Larry
7 Jun 2010 21:00
Re: BCM5354
On 06/07/2010 08:48 PM, Larry Finger wrote: > On 06/07/2010 01:33 PM, Robert Hazbun wrote: >> Hello all, >> >> I currently work for a company that is using OpenWRT, with linux 2.4, on >> a BCM5354. We really want to move to OpenWRT with linux 2.6 using the >> b43 driver on this chip. Initial test results show that b43 seems to >> work in client / Adhoc mode, but not in AP mode. Unfortunately, I have >> been unable to ascertain the status of the b43 driver with respect to >> this chip. >> >> Can anyone confirm whether it's fully functional under this platform? If >> not, what's left to be done ? > > I believe the BCM5354 has an LP PHY. As such, it should be supported by > any 2.6.32, or later, kernel. AFAIK, no such device has been tested by a > developer. My tests with a BCM4312, which also has an LP PHY, show that > b43/mac80211 will function as an AP using recent versions of hostapd. OpenWRT uses compat-wireless, so it should actually work out of the box with current OpenWRT SVN trunk. I didn't try that yet, however. It is possible that the PHY has a special revision which is not fully implemented in the driver, yet. -- -- Greetings Michael.
7 Jun 2010 21:42
Re: BCM5354
On 06/07/2010 01:56 PM, Robert Hazbun wrote:
> Interesting. So, this give me hope that I've done something wrong. When
> I try to enable AP mode using iwconfig, I simply get an error.
>
> Larry, the company I work for is willing to fund b43 work on the BCM5354
> and have it released to the public. Do you know who has done the initial
> work on the 5354, and who would be the right person to contact?
As Michael Buesch says, there may be parts of the 5354 spec that have
not yet been implemented in b43. I am the person that did most of the LP
PHY reverse engineering. The person that did the coding from the
resulting "specs" was Gabor Stefanik, who reads this list. I will review
the 5354-specific code in the latest driver to see if changes are needed.
I suspect that the problem is with iwconfig, which uses the WEXT
interface that is only partially implemented. I wrote the following for
the openSUSE Wireless Forum. It will not wok directly with openWRT, but
it should give you the idea.
=================================================
This article might be entitled "How to convert an $800 laptop into a $40
wireless router", which indicates why doing this might not be desirable.
There are, however, at least two cases where this might make sense: (1)
You want to provide or test some feature that is not supplied by your
AP. One example is 802.11a (5 GHz) channels. (2) your need for an AP is
temporary such as network sharing of a 3G broadband modem.
To accomplish the task, several pieces of software will be needed
including hostapd, a DHCP server for the AP's clients, and an iptables
rules for Network Address Translation (NAT). The requirements for these
are discussed in turn.
I. Hostapd
Hostapd runs in user space and interacts with the device driver to
handle most of the things that an AP does, such as transmitting of
beacons, authentication, etc. The version included with the "hostapd"
package of openSUSE 11.1 (0.5.10) works with a limited number of devices
and drivers. For modern drivers that use mac80211, a newer version is
needed, which can be downloaded from hostapd: IEEE 802.11 AP, IEEE
802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Building this will require
that the make, libnl, libnl-devel, openssl-devel and gcc packages are
installed. I recommend installing the package from the repository and
then doing a download, make and install of the later version. If your
kernel is older than 2.6.28 (check uname -r), then you will need the
compat-wireless code that is downloaded from Download - Linux Wireless.
For this option, you will also need to install the kernel source, and
prepare it for use.
To prepare the source, issue the following commands:
Code:
cd /usr/src/linux
sudo cp /proc/config.gz .
sudo gunzip config.gz
sudo cp config .config
sudo make prepare
Configuration of hostapd is accomplished with a configuration file named
hostapd.conf. There are a number of options in that file, but a working
AP with WPA2 encryption can be setup with the following:
Code:
interface=wlan0
driver=nl80211
hw_mode=g
channel=1
ssid=test
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_passphrase=123456789
II. Dhcpd
The standard dhcpd package in openSUSE 11.1 works just fine. To use it,
you need to modify its configuration file dhcpd.conf. Again, there are a
number of options available, but you can get a working DHCP server with
the following:
Code:
option domain-name-servers 192.168.1.1;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none; ddns-updates off;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.200 192.168.0.229;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
}
The above configuration assumes that the AP will be connected to the
outside world with an IP address of 192.168.1.X and that the AP's
clients will have addresses 192.168.0.X. If other addresses are used,
adjust the above info accordingly.
III. Iptables Network Address Translation rules
For this example, the NAT rules will be only those necessary to get the
AP operational. Although iptables is used to write firewalls, the only
protection in this code is to allow only established connections. The
rules are shown in the script below.
IV. A script to start and stop the Access Point
The following code will start and stop the AP. To make any changes
easier, the locations of the various utilities, the interface names, and
the IP address to be used are defined by symbols at the start of the
script. I also use configuration files that are stored in root's home
directory, not in /etc as would normally be done. This script must be
executable and be run as root.
Code:
#!/bin/sh
# Script to start/stop a hostapd-based access point
#
# Symbols for needed programs
IPTABLES=/usr/sbin/iptables
IFCONFIG=/sbin/ifconfig
DHCPD=/usr/sbin/dhcpd
HOSTAPD=/usr/local/bin/hostapd
# Symbols for internal and external interfaces
NET_INT=wlan0
NET_EXT=eth0
# IP address for the AP
INT_ADDR=192.168.0.1
case "$1" in
start)
echo "Starting AP mode for $NET_INT at address $INT_ADDR"
# Disable packet forwarding
echo 0 > /proc/sys/net/ipv4/ip_forward
# Stop any existing hostapd and dhcpd daemons
killproc hostapd
killproc dhcpd
#Set up forwarding
$IPTABLES -t nat -A POSTROUTING -o $NET_EXT -j MASQUERADE
$IPTABLES -A FORWARD -i $NET_EXT -o $NET_INT -m state \
--state RELATED,ESTABLISHED -j ACCEPT
$IPTABLES -A FORWARD -i $NET_INT -o $NET_EXT -j ACCEPT
# Enable packet forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
# Get the internal interface in the right state
$IFCONFIG $NET_INT down
$IFCONFIG $NET_INT up
$IFCONFIG $NET_INT $INT_ADDR
# dhcpd needs to have a leases file available - create it if needed
if [ ! -f /var/lib/dhcp/db/dhcpd.leases ]; then
touch /var/lib/dhcp/db/dhcpd.leases
fi
# Bring up the DHCP server
$DHCPD -cf /root/dhcpd.conf $NET_INT
# Bring up hostapd
$HOSTAPD -B /root/hostapd.conf
;;
stop)
echo "Stopping AP mode on $NET_INT"
# Stop hostapd and dhcpd daemons
killproc hostapd
killproc dhcpd
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
=================================================
Larry
RSS Feed