#9211: 3G connection doesn't start at boot.
---------------------+---------------------------
  Reporter:  Crazy   |      Owner:  developers
      Type:  defect  |     Status:  reopened
  Priority:  lowest  |  Milestone:  Bugs Paradise
 Component:  other   |    Version:  Trunk
Resolution:          |   Keywords:
---------------------+---------------------------

Comment (by anonymous):

 This is, what I like on Linux development: Once one found a solution to a
 problem, someone wants to improve things and f*** it up all over again...
 *sigh*.

 Why do we need json and fancy webinterfaces on a router os anyway? I
 remember times, when a was happy with nvram variables and a small and
 simple php-webif. I had less problems by then.
 Ok, I won't change the direction...back to the renewed problem:

 In http://wiki.openwrt.org/doc/recipes/3gdongle?s[]=ma260 I described how
 to initialize TP-Link's MA260 stick. I needs some special treatment and a
 standard eject never worked for me on this device.
 Neither the product nor vendor id's I described in the wiki, are sent over
 by usb-mode.json.


 BTW: an usbreset does not require the usbreset utility. usb_modeswitch has
 a parameter "-R" which is to be combined with -p and -v -b and -g.

 The initialisation messages for MA260 (storage mode ids 2357:f000) are:

 "5553424312345678000000000000061e000000000000000000000000000000"
 "5553424312345678000000000000061b000000020000000000000000000000"

 A standard eject won't fully initialize the device, but leave it in a
 state in between.

 The vendor and product ID for the 3G-mode of dongle should be 2357:9000
 after the mode switch.

 I am not yet fully familiar with the usb-mode.json, but I'll try to make
 guess on how it should work. Please test the file attached, but make a
 backup before that.

 I'll attach them a patch and full version above, as soon as I figured it
 out.
 I apologize, that I can test it myself, since my only MA260 is connected
 to a router quite a few miles away from my whereabouts.

 BTW: an usb reset does not require the presence of the usbreset binary -
 alternative ways exist:
 * echo 0 > /sys/bus/usb/devices/[enumeration]/authorized" && echo 1 >
 /sys/bus/usb/devices/[enumeration]/authorized"

 and usb_modeswitch can be invoked with -R -p [prodid] -v  [vendid] -b [bus
 ]-g [device]
 please refer to man usb_modeswitch for details.

--
Ticket URL: <https://dev.openwrt.org/ticket/9211#comment:36>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to