On Thu, 2009-01-22 at 13:53 -0500, Derek Atkins wrote: > Dan Williams <d...@redhat.com> writes: > > >> Here's what mine currently looks like (it looks somewhat different than > >> yours): > >> > >> <!-- Samsung SGH-A707 (AT&T Sync) --> > >> <match key="@info.parent:usb.vendor_id" int="0x04e8"> > >> <match key="@info.parent:usb.product_id" int="0x6601"> > >> <match key="@info.parent:usb.interface.number" int="0"> > >> <append key="modem.command_sets" > >> type="strlist">GSM-07.07</append> > >> <append key="modem.command_sets" > >> type="strlist">GSM-07.05</append> > >> </match> > >> </match> > >> </match> > >> > >> Should I just swap both of those "GSM-*" entries to IS-707-A? > >> Or should I add an info.capabilities line and make it look like yours? > > > > Remove one of the "modem.command_sets" items, and change the other one > > to "IS-707-A". > > BTW, I had a chance to test this out yesterday and it worked > perfectly. Yay! And I can even start the VPN over it. Yay! > > Now if only I could figure out why my work wifi keeps disconnecting. > I see things like this in my dmesg logs: > > ... > wlan0: authenticate with AP 00:1f:9e:ce:b3:21 > wlan0: authenticated > wlan0: associate with AP 00:1f:9e:ce:b3:21 > wlan0: RX ReassocResp from 00:1f:9e:ce:b3:21 (capab=0x421 status=0 aid=1) > wlan0: associated > wlan0: deauthenticated > wlan0: authenticate with AP 00:1f:9e:ce:c2:71 > wlan0: authenticate with AP 00:1f:9e:ce:c2:71 > wlan0: authenticate with AP 00:1f:9e:ce:c2:71 > wlan0: authenticate with AP 00:1f:9e:ce:c2:71 > wlan0: authentication with AP 00:1f:9e:ce:c2:71 timed out
Driver or AP problem... Heavy RF environment? Dan _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list