Michael Warmuth wrote:

But I really think that this is the correct
sequence: Because it is possible to start a process then which strikes
when the interface is fully configured by XWLAN. But it's a bit hard to
code to step back in time when xwlan.cmd is started after configuring
the interface. ;-)

I doubt that the xwlan script should be run before the WLAN interface is configured. The purpose of the script is to run additional commands depending on the _configured_ WLAN interface, for this the WLAN interface must already be configured. The only thing that I could think of is to redesign the script interface and add two more events. SO it would not only be

CONNECT (run after WLAN is configured)
DISCONNECT (run before WLAN is unconfigured)

but as well

CONNECTPENDING (run before WLAN is configured)
DISCONECTCOMPLETED (run after WLAN is unconfigured)

I would not so so before there is a serious used case for that, because I would not want to make the whole thing too complex.