Did not know about the -t. thx!<br><br>Here's what I wish to do:<br><br>(all different identities and passwords and each stored correctly in the config file).<br><br>Case A.<br>connect to AP1, then connect to AP2, then connect to AP3.
<br><br>or<br>
<br>
Case B.<br>connect to AP1, then connect to AP2, then connect to AP1.<br>
<br>or<br>
<br>
Case C.<br>connect to AP1, change identify and password, then connect to AP1, change identify and password, then connect to AP1.<br><br>combinations like that.<br><br>I believe I've tried select_network 0, then select_network 1 and even select_network 0, then select_network 0 and that didn't even go through the process of connecting to the second attempt...just sat there.
<br><br>I'll do exactly whatever you advise me to do... if Network 0 and 1 are properly setup (and for different APs), how exactly -command by command- does one properly connect to AP0 (using network 0) then connect to AP1 (using network 1)??
<br><br>also someone wrote that html emails clutter the forum is that true?<br><br>thanks for you suggestions,<br><br>george<br>
<br><span class="gmail_quote"></span><div><span class="gmail_quote">On 8/8/06, <b class="gmail_sendername">Jouni Malinen</b> <<a href="mailto:jkmaline@cc.hut.fi">jkmaline@cc.hut.fi</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Aug 08, 2006 at 05:01:38PM -0700, George S. Lockwood wrote:<br><br>> As requested here is a log of a case of it not connecting to a network after<br>> a connection is established. In fact this is trying to connect to the very
<br>> same network that it was connected to just before. Sorry couldn't get all<br>> the console msgs but you can see that the connection is authenticated.<br><br>This does not match with what I understood you were trying to do,
i.e.,<br>moving between two different APs and neither does this do just the<br>select_network command. Disconnect command is requesting wpa_supplicant<br>to disconnect from all networks, you will need to use reassociate to get
<br>it connected again. If that does not work, please send a debug log that<br>continues further after the wpa_cli command.<br><br>> Please note: I've added the time to the console msgs, and yes I see that<br>> sometimes it get written twice, not sure why at this moment, but that is not
<br>> my concern just now.<br><br>-t command line option in wpa_supplicant should add the timestamp<br>correctly without any modification needed for this..<br><br>> 2. through wpa_cli I send a ap_scan=2 command. (because it is
<br>> hidden).<br><br>> 5. Then through wpa_cli I send a disconnect command.<br><br>> 6. through wpa_cli I send another ap_scan=2 command.<br><br>This should not be needed since ap_scan=2 was already configured in step
<br>2.<br><br>> 8. through wpa_cli I send another select_network "FeatherSecure"<br>> command<br><br>Since you used disconnect in step 5, this should be replaced with<br>reassociate command. select_network can be used to move between two
<br>networks when disconnect command is not used.<br><br>--<br>Jouni Malinen PGP id EFC895FA<br>_______________________________________________<br>HostAP mailing list<br><a href="mailto:HostAP@shmoo.com">
HostAP@shmoo.com</a><br><a href="http://lists.shmoo.com/mailman/listinfo/hostap">http://lists.shmoo.com/mailman/listinfo/hostap</a><br></blockquote></div><br>