Phone Command "WLAN ON" not working

[Nobody/Anonymous]

The telephone command for "WLAN ON" isn't responding. And after it is shut down by phone-command, even the Web-Gui cannot start WLAN.
You have to reboot the router and it's O.K. again.

[Nobody/Anonymous]

Hello,

i tested the telephone command "WLAN OFF" and "WLAN ON" too and all works fine. But sometimes the Wifi driver hangs while load or reload the driver.

[Patrick Schmidt]

There is no solution to this hangup, because the Broadcom driver is the reason for this behaviour. We cant do anything about this buggy module. The only thing you can do is to define a custom telephone command (look at howto on bitswitcher web seite) which doesnt call '/etc/start_scripts/wlan.sh stop' to stop wlan, but does execute smth. like this:

wlctl down
wlctl disassoc
ifconfig wl0 down

But this doesnt disable the WLAN hardware really and only disables sending of frames.

[Nobody/Anonymous]

Hallo,

i use the following "custom_call_event.sh"-skript to start and stop Wifi:
---------------------------------------------------------------------------
#!/bin/sh

[ "$#" -lt "5" ] && exit 1
echo "Call custom event..."

if [ "$EVENT" == "CALL" ]
then
case "$CALLER" in
   "55*0")
      nvram set wl_up=0
      wlctl down
      killall -9 nas
      wlctl disassoc
      ifconfig wl0 down
   ;;
   "55*1")
      nvram set wl_up=1
      /etc/start_scripts/wlan.sh restart
      nvram set wl_up=0
   ;;
   *)
      # sonst nix
   ;;
   esac

exit 0
fi
---------------------------------------------------------------------------

I can now Wifi start with "#55*1#" and stop with "#55*0#" phone-code. This script does not unload the wifi-driver! So the buggy Wifi driver does not hang. With my normal settings WLAN is off. This script regards this behavior due to setting the "wl_up" NVRAM variable to "0" after starting Wifi.

For more information about custom call events follow this link
http://bitswitcher.sourceforge.net/howto.html#call_mon