Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#11291 closed defect (fixed)

WDS station bridge mode, trunk r31258 (openwrt build) on Fonera does not come up on boot

Reported by: duvi Owned by: nbd
Priority: normal Milestone: Netifd Implementation
Component: base system Version: Trunk
Keywords: Cc:


Having uploaded the trunk build from on a Fonera, and using these configs:

root@OpenWrt:~# cat /etc/config/network

config 'interface' 'loopback'
        option 'ifname' 'lo'
        option 'proto' 'static'
        option 'ipaddr' ''
        option 'netmask' ''

config 'interface' 'lan'
        option 'ifname' 'eth0'
        option 'type' 'bridge'
        option 'proto' 'static'
        option 'ipaddr' ''
        option 'netmask' ''
        option 'gateway' ''
        option 'dns' ''
        option 'accept_ra' '1'
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device  radio0
        option disabled 0
        option type     mac80211
        option channel  1
        option macaddr  00:18:84:2a:22:4d
        option hwmode   11g
        option txpower  18
        option diversity 0
        option rxantenna 1
        option txantenna 1

config wifi-iface
        option device   radio0
        option network  lan
        option mode     sta
        option wds      1
        option ssid     *
        option encryption psk2
        option key      *

Logread says:

Jan  1 01:00:38 OpenWrt sysinit: l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
Jan  1 01:00:38 OpenWrt sysinit: wlan0: Failed to open l2_packet connection for the bridge interface 'br-lan'
Jan  1 01:00:38 OpenWrt sysinit: enable_mac80211(radio0): Failed to set up wpa_supplicant for interface wlan0

and the wireless interface does not come up.

However, if I log in from ethernet after boot, and type 'wifi', the wireless interface does come up immediately.
Maybe there's some confusion with the init scripts / command order on boot?

Attachments (0)

Change History (16)

comment:1 Changed 6 years ago by duvi

Also built my own r31327 from svn, it produces the same error.

comment:2 Changed 6 years ago by jow

  • Owner changed from developers to nbd
  • Status changed from new to assigned

comment:3 Changed 6 years ago by jow

Seems to me like wifi is brought up before the bridge is ready. Quite odd but maybe a race exposed by the slowness of the classic Fonera.

comment:4 Changed 6 years ago by duvi

Do you think I should give it a try with netifd?

comment:5 Changed 6 years ago by duvi

I did, and it is ok using netifd.

comment:6 Changed 6 years ago by andrew@…

Hello, I am having the exact same problem, please could you provide more detail on the netifd solution?

comment:7 Changed 6 years ago by duvi

You can enable netifd if you build your own image from trunk.
Than you can find this option in 'Base system' when running 'make menuconfig'.

comment:8 Changed 6 years ago by Erik Fonnesbeck <efonnes@…>

I had the same thing happen on my TP-Link TL-WA901ND with an image I built from r31548 not using netifd - wireless (bridged WDS station) doesn't connect properly at boot but works if I restart wireless. I have not tested whether it occurs in any other type of wireless client mode.

comment:9 Changed 6 years ago by Nilfred <nilfred@…>

Milestone: Netifd Implementation

comment:10 Changed 6 years ago by jow

  • Milestone changed from Attitude Adjustment (trunk) to Netifd Implementation

comment:11 Changed 6 years ago by duvi

I don't see where this problem has anything to do with netifd.

comment:12 follow-up: Changed 6 years ago by anonymous

As per the advice given here I downloaded the OpenWrt source code and compiled with netifd. I can confirm netifd fixed the problem immediately.

I have a Huawei HG556a EchoLife Vodafone router, and am using WDS in bridge client mode. Without netifd this connection does not automatically resume on reboot, I had to SSH via ethernet and do "wifi up". With netifd no such action is required, the bridge comes up automatically upon reboot.

comment:13 in reply to: ↑ 12 Changed 6 years ago by marc@…

I understand that the impending move to netifd will inherently fix this, but is it possible to add an extra 'kick' to enable WiFi in current trunk builds?

I'd love to be able to keep tracking trunk, but this is a showstopper for WDS users.

Also, would it make sense to change the ticket name to reflect the scope of this as 'all' arches, rather than just 'fonera'?

comment:14 Changed 6 years ago by jow

No, we won't invest any work in the current scripts anymore.

comment:15 Changed 6 years ago by nbd

  • Resolution set to fixed
  • Status changed from assigned to closed

netifd is now enabled by default

comment:16 Changed 6 years ago by marc@…

Thanks! I'll try it out on the WNDR3700 and the WZR-HP-G450n as soon as I can. I had no idea netifd was landing so soon.

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.