You're right. I've never roamed without shutting down ;-) The point is I often ifdown...rmmod...insmod...ifup in order to update to latest CVS for my Ralink based card. I now understand better the wpa_action infrastructure and admit my patch will not fit in it.
Regards, Cedric 2006/11/27, kelmo <[EMAIL PROTECTED]>: > > What happens when you roam from network A to network B with this patch > applied? Or an intermittent loss or re - connection to any network? > > When leaving a network, wpa_cli daemon will invoke wpa_action after > recieving the disconnected signal via the control socket: > `wpa_action $IFACE DISCONNECTED' > > wpa_action will then call ifdown: > `ifdown $IFACE' > > At this point, the code from the above patch will then terminate the > wpa_* daemons, via wpa_action, due to the logical mapping having a `wpa- > roam slave' line in its stanza. Network B is now out of reach, or your > connection is lost if you experience a DISCONNECTED event for whatever > reason. > > Please correct me if wrong. > > Thanks, Kel. > > -- > ifupdown script fails to terminate wpasupplicant > https://launchpad.net/bugs/72152 > -- ifupdown script fails to terminate wpasupplicant https://launchpad.net/bugs/72152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
