Christian Langanke wrote:

I use XWLAN 2.14 and when I turn on the WLAN it does:
1) Turns on the card
2) Searchs for a WLAN
3) Connects to the WLAN
4) Does run xwlan.cmd
5) Configures the IP interface
  

Correct. First of all the online help was incorrect. To reflect the current implementation, it would read like this

This script is executed
- after the TCP/IP interface has been configured  or
- before it is unconfigured

I cannot remember when I modified the code to execute the script on disconnect before XWLAN unconfigures the WLAN device, but it seems that I forgot to update the docs as well.

IMPORTANT:

I just thought about if the order makes sense on dsconnect, and think it may be better to call the script on disconnect after XWLAN unconfigured the WLAN interface. Please tell me what you think, I have no idea what is really better.

Moreover,  Michael is correct: the script is called before DHCP finished configuration - this is a bug, thanx for the hint!

I once have added code to call the script on connect under certain circumstances on reenablement of radio, but _before_ the DHCP request is issued. I don't recall why, although the code part was commented (otherwise I would not even have known why I added it...). Now I just commented out this part, and the script is properly called on disconnect - it seems that I once had a problem hat I somehow accidentally fixed, and so did not remove the obsolete code.

Next version will have that fix, and if we think that the disconnect script call should be executed after XWLAN unconfigured the WLAN interface, I will also change this.