Ticket #236 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

WPA and bridge

Reported by: wbx Assigned to: dnehring
Priority: critical Milestone:
Component: brcm-2.4 Version: 1.0
Keywords: wpa br0 bridge Cc:

Description

There is a problem if you configure WPA and Bridging.

See following interfaces file: # WLAN with WPA2, MAC-Filter and WLAN-Speedup auto eth1 iface eth1 inet manual

wireless-type broadcom wireless-country DE wireless-mode ap wireless-ssid FreeWRT wireless-channel 11 wireless-security wpa-psk wireless-authorization psk psk2 wireless-encryption aes+tkip wireless-wpa-key xxxxxxx

# Bridging WLAN<->LAN auto eth0.0

iface eth0.0 inet manual

switch-ports 1 2 3 4 5*

# should be always the last configured interface, it depends # on interfaces in bridge-ifaces auto br0 iface br0 inet static

bridge-ifaces eth0.0 eth1 address 192.168.1.1 netmask 255.255.255.0 broadcast +

Nas does not start correctly, because the bridge does not exist at the moment the eth1 interface is bring upped. It is not possible to setup /etc/network/interfaces to setup WPA and Bridge.

Attachments

Change History

03/13/07 21:29:03 changed by thengineer

this is just a workaround, that did it for me:

in the /etc/network/if-pre-up.d/wireless-broadcom: overwrite the $ifname so that it always contains "br0". (this way nas will fail to start at boot-time.)

after configuring the network interfaces, a simple # ifdown eth2 # ifup eth2 is enough to get the wlan with bridging and wpa running correctly.

03/15/07 14:30:35 changed by tha

  • status changed from new to closed.
  • resolution set to fixed.

The bug you have reported has been closed with svn changeset #2167.

The bugfix will be part of the freewrt 1.0.3 release. Please be aware, that you have to configure a new interface-option for your wireless interface to get it working correctly.

auto eth1 iface eth1 inet manual

wireless-type broadcom ... wirelress-bridge-if br0

03/26/07 18:11:01 changed by pylon@koeln.ccc.de

  • status changed from closed to reopened.
  • resolution deleted.

There is still a race-condition somewhere.

nas gets started, but it will be stopped soon after, when something changes the interfaces.

That's my quick capture on a serial console (some messages are messed up…):

root@(none):/# eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0 ps ax | grep nas

199 root 284 S grep nas

root@(none):/# ps ax | grep nas

202 root 368 R /usr/sbin/nas -P /var/run/nas.lan.pid -l br0 -H 34954 242 root 284 S grep nas

root@(none):/# eth0.0: dev_set_promiscuity(master, 1) device eth0 entered promiscuous mode device eth0.0 entered promiscuous mode device eth1 entered promiscuous mode root@(none):/# ps ax | grep nas

260 root 284 S grep nas

root@(none):/#

03/26/07 18:18:24 changed by anonymous

I "fixed" it with changing the order of the scripts if-pre-up.d:

FreeWRT:/# ls /etc/network/if-pre-up.d/ 000-watchdog 02wireless-broadcom 01vlan 03bridge root@FreeWRT:/#

This makes sure, the bridge-script is called as the last one, so that nas will be started for sure and will not be stopped by some other script.

03/28/07 23:11:37 changed by wbx

  • status changed from reopened to closed.
  • resolution set to fixed.

thx. added in 2305.

Add/Change #236 (WPA and bridge)




Action