[OpenWrt-Devel] sierra-directip howto in OpenWRT
Hi all I asked in the forums but nobody has replied so asking on here as well. I'm running a Sierra 320U which supports 3G & LTE/4G. Have compiled in the directip options as well as QMI etc so I now see the wwan0 interface and there are some generic directip scripts in /etc/gcom What is the known process to get the Sierra USB modems connected via directip & wwan0 instead of via the serial link/pppd option? Note that I have providers that both use CHAP/PAP auth and have a username/password as well as others who do not require this, so would like to configure scripts up accordingly or have a second script modified to suit both options. I'm aware there is no LuCI support (yet) for this configuration. Thanks Adam ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] what is the current state of support for MT7620A on-SoC 2.4G?
just to prove i've done my homework :-), colleague had been
downloading the alleged driver for 2.4G support for the mediatek
MT7620A from github.com:
https://github.com/wuqiong/rt2860v2-for-openwrt-mt7620
that driver clearly admits it's for the 3.10 kernel, so it was only a
matter of time before trying to use it for the 3.14 kernel was going
to break, as it did given this recent commit to openwrt:
$ git show 9d7ff9375d55822a3e4d0b35800a1ebfe938ade2
Author: blogic
Date: Wed Nov 12 14:54:50 2014 +
ralink: add support for mt7621 ethernet
... snip ...
part of that commit was to entirely remove a patch file:
diff --git
a/target/linux/ramips/patches-3.14/0036-NET-add-mt7621-ethernet-driver.patch
b/target/linux/ramips/patches-3.14/0036-NET-add-mt7621-ethernet-driver.patch
deleted file mode 100644
index c145a2f..000
---
a/target/linux/ramips/patches-3.14/0036-NET-add-mt7621-ethernet-driver.patch
+++ /dev/null
... snip ...
which, among other things, added support for routines
ra_sw_nat_hook_{rx,tx}, which now (unsurprisingly) generate undefined
symbol errors when trying to compile.
i also notice that felix's recent addition for support for the 5G
MT7612 chip deactivated 2.4G support, so ... what is the proper
approach to get 2.4G support for the MT7620A? (if it's even possible.)
BTW, i just received a buffalo airstation WHR-1166D with
MT7620A/MT7612E, so i'm more than ready to try a build and flash.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [base-files] functions.sh: default_postinst() - create user:group first
Hi Christian,
patch is correct. it does solve the problem. however, apart from you
and me there will be only a handful of people that will instantly know
why this patch is correct :) could you resubmit with a proper
description. a one liner is enough.
John
On 26/11/2014 19:38, Christian Schoenebeck wrote:
> 1.) create user:group 2.) run postinst-pkg now you can change owner
> and permission of installed files and directories in postinst-pkg
> (Makefile/postinst) otherwise you can't 3.) clear luci cache 4.)
> enable/start service
>
> Signed-off-by: Christian Schoenebeck
> ---
> package/base-files/files/lib/functions.sh | 7 +-- 1 file
> changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/package/base-files/files/lib/functions.sh
> b/package/base-files/files/lib/functions.sh index d53be3e..3d987cf
> 100755 --- a/package/base-files/files/lib/functions.sh +++
> b/package/base-files/files/lib/functions.sh @@ -173,7 +173,7 @@
> default_prerm() { default_postinst() { local name rusers
> name=$(echo $(basename $1) | cut -d. -f1) - [ -f
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] && ( .
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ) +
> rusers=$(grep "Require-User:"
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.control) [ -n "$rusers"
> ] && { local user group uid gid @@ -212,6 +212,10 @@
> default_postinst() { done done } + + [ -f
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] && ( .
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ) + [ -n
> "${IPKG_INSTROOT}" ] || rm -f /tmp/luci-indexcache 2>/dev/null + [
> "$PKG_UPGRADE" = "1" ] || for i in `cat
> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.list | grep
> "^/etc/init.d/"`; do [ -n "${IPKG_INSTROOT}" ] && $(which bash)
> ${IPKG_INSTROOT}/etc/rc.common ${IPKG_INSTROOT}$i enable; \ [ -n
> "${IPKG_INSTROOT}" ] || { @@ -219,7 +223,6 @@ default_postinst() {
> $i start } done - [ -n "${IPKG_INSTROOT}" ] || rm -f
> /tmp/luci-indexcache 2>/dev/null return 0 }
>
> ___ openwrt-devel
> mailing list openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On Nov 27 07:04 +0100, Rafał Miłecki wrote: > On 26 November 2014 at 23:41, SGT. Garcia wrote: > > On Nov 19 18:43 +0100, Rafał Miłecki wrote: > >> On 12 November 2014 21:59, Alex Henrie wrote: > >> > 2014-11-11 23:51 GMT-07:00 Rafał Miłecki : > >> >> On 11 November 2014 23:26, Alex Henrie wrote: > >> >>> Is no one interested? Come on, I'm offering free hardware to play with > >> >>> ;-) > >> >> > >> >> I already have about 10-20 Broadcom based boars in my drawer ;) Not > >> >> that excited with another one. > >> >> > >> >> However I'd be happy to help adding support for WNR1000 v3. Could you > >> >> attach serial console to it and test some patched OpenWrt builds? > >> > > >> > It sounds like a fun project, but SGT. Garcia > >> > volunteered to work on it, and I have already mailed the device to > >> > him. I'm sure SGT. Garcia will contact you for help once he receives > >> > the device. Thanks for your work on OpenWrt! > >> > >> Could you provide us NVRAM dump once you get this device? You have > >> access to "nvram show" command in both: CFE and original firmware I > >> believe. > > > > first question, do i absolutely need a serial console to get an interface > > with CFE? i tried telnetenable from NetGearTelnetEnable and it did work so > > far as establishing connection with no prompt. so i couldn't run any > > command (nvram show) at that point. > > Yes. CFE doesn't implement ssh/telnet, so serial console is the way to > talk with it. Plus you need serial console to watch OpenWrt booting > process, so we can what goes wrong. > Michael and Alex are sending me USB<->COM cable and USB port[?] to get the serial console going. > > then made a cardinal mistake of > > upgrading the firmware and now it refuses to allow telnet connection. i > > might be able to roll back the firmware. > > You mean upgrading to the latest Netgear firmware? Well, it doesn't > matter if they disabled telnet server in it. We don't really telnet > access to the Netgear's firmware. > i see... i was just going by the wiki. > > the default firmware does provide upgrading from it's GUI interface and i'm > > hoping to try the img you suggested in the thread to see if i can get a > > partially working openwrt (mainly telnet/ssh/shell prompt) and take it from > > there. > > First provide me NVRAM dump, so I can add support for WNR1000 v3. > Don't try to install OpenWrt before me doing that. > > -- > Rafał noted, sure. SG. Garcia ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [uqmi] SEGFAULT on reading Unicode sms messages
I was trying to read (by command --get-message) sms text message coded in 16 bit Unicode which is not supported yet in uqmi, but program does not end cleanly, I got segfault: Program received signal SIGSEGV, Segmentation fault. blobmsg_check_attr (attr=attr@entry=0x60d038, name=name@entry=false) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/libubox-2014-11-23/blobmsg.c:49 49 if (hdr->name[blobmsg_namelen(hdr)] != 0) (gdb) bt #0 blobmsg_check_attr (attr=attr@entry=0x60d038, name=name@entry=false) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/libubox-2014-11-23/blobmsg.c:49 #1 0x779e911b in blobmsg_format_element (s=s@entry=0x7fffea48, attr=attr@entry=0x60d038, array=array@entry=false, head=false) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/libubox-2014-11-23/blobmsg_json.c:221 #2 0x779e9609 in blobmsg_format_json_with_cb (attr=0x60d038, list=list@entry=false, cb=cb@entry=0x0, priv=priv@entry=0x0, indent=) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/libubox-2014-11-23/blobmsg_json.c:316 #3 0x00403377 in blobmsg_format_json_indent (list=false, indent=, attr=) at /home/wirouter/Projects/OpenWRT/x86/staging_dir/target-x86_64_uClibc-0.9.33.2/usr/include/libubox/blobmsg_json.h:42 #4 uqmi_print_result (data=) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/wi-uqmi-2014-11-20/commands.c:176 #5 __uqmi_run_commands (qmi=qmi@entry=0x60b580 , option=option@entry=false) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/wi-uqmi-2014-11-20/commands.c:218 #6 0x004033cb in uqmi_run_commands (qmi=qmi@entry=0x60b580 ) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/wi-uqmi-2014-11-20/commands.c:236 #7 0x004012df in main (argc=5, argv=0x7fffed58) at /home/wirouter/Projects/OpenWRT/x86/build_dir/target-x86_64_uClibc-0.9.33.2/wi-uqmi-2014-11-20/main.c:126 This is a raw message read by --get-raw-message (phone number is masked): "07 91 ** ** ** ** ** f* 04 0b 91 ** ** ** ** ** f* 00 08 41 11 02 41 42 15 40 08 01 04 01 06 01 18 01 41" I figured out that cause of this lies in function cmd_wms_get_message_cb(). There is a call for blobmsg_open_table() and blobmsg_close_table() at the end, but in meantime there is also return from function when readed data is invalid or not supported, like Unicode, so blobmsg_close_table() is not invoked. Propossed patch using "goto" follows. But still program returns 0 meaning SUCCESS, I don't known how to handle this. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH uqmi] SEGFAULT on reading Unicode sms messages
Added complementary blobmsg_close_table() before returning from function
on error.
---
commands-wms.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/commands-wms.c b/commands-wms.c
index 9b9aac3..da4aeaf 100644
--- a/commands-wms.c
+++ b/commands-wms.c
@@ -270,7 +270,7 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
cur_len = *(data++);
if (data + cur_len >= end)
- return;
+ goto error;
if (cur_len) {
wms_decode_address("smsc", data, cur_len - 1);
@@ -278,7 +278,7 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
}
if (data + 3 >= end)
- return;
+ goto error;
first = *(data++);
sent = (first & 0x3) == 1;
@@ -287,7 +287,7 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
cur_len = *(data++);
if (data + cur_len >= end)
- return;
+ goto error;
if (cur_len) {
cur_len = (cur_len + 1) / 2;
@@ -296,18 +296,18 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
}
if (data + 3 >= end)
- return;
+ goto error;
/* Protocol ID */
if (*(data++) != 0)
- return;
+ goto error;
/* Data Encoding */
dcs = *(data++);
/* only 7-bit encoding supported for now */
if (dcs & 0x0c)
- return;
+ goto error;
if (dcs & 0x10)
blobmsg_add_u32(&status, "class", (dcs & 3));
@@ -317,7 +317,7 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
data++;
} else {
if (data + 6 >= end)
- return;
+ goto error;
str = blobmsg_alloc_string_buffer(&status, "timestamp", 32);
@@ -351,6 +351,12 @@ static void cmd_wms_get_message_cb(struct qmi_dev *qmi,
struct qmi_request *req,
cur_len = *(data++);
decode_7bit_field("text", data, end - data, !!(first & 0x40));
blobmsg_close_table(&status, c);
+
+ return;
+
+error:
+ blobmsg_close_table(&status, c);
+ fprintf(stderr, "There was an error reading message.\n");
}
static enum qmi_cmd_result
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] What are the current watchdog capabilities in CC? via procd or busybox?
I understand process management is moving to procd. Few of the wiki pages suggest that procd is where watchdog capabilities are too. http://wiki.openwrt.org/doc/techref/procd I have a sunxi setup that is dying under some predictable network conditions and I need watchdog to do a few things to help me debug the situation. Is there any documentation on configuring procd and watchdog for the current/future procd in CC? Cheers Derek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] What are the current watchdog capabilities in CC? via procd or busybox?
On 27/11/2014 16:22, Derek & Vicky wrote: > I understand process management is moving to procd. Few of the wiki > pages suggest that procd is where watchdog capabilities are too. > http://wiki.openwrt.org/doc/techref/procd > > I have a sunxi setup that is dying under some predictable network > conditions and I need watchdog to do a few things to help me debug the > situation. > what do you need it to do ? > Is there any documentation on configuring procd and watchdog for the > current/future procd in CC? > > Cheers > Derek > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Changeset 43410: phydriver soft_reset availability under 3.14
Changeset 43410 modifies the ar8216 driver to use the phy_driver soft_reset callback also under 3.14. As far as I can see this callback is not available under 3.14, even in the most recent 3.14.25. Am I missing something? Heiner ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Changeset 43410: phydriver soft_reset availability under 3.14
Am 27.11.2014 um 19:50 schrieb Heiner Kallweit: > Changeset 43410 modifies the ar8216 driver to use the phy_driver soft_reset > callback also under 3.14. > As far as I can see this callback is not available under 3.14, even in the > most recent 3.14.25. > Am I missing something? > > Heiner > Sorry, missed your previous changeset with the backported soft_reset extension .. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [base-files] functions.sh: default_postinst() - create user:group first
Hi John,
sorry! What do you meed with a "proper" description ?
Christian
Am 27.11.2014 um 15:14 schrieb John Crispin:
> Hi Christian,
>
> patch is correct. it does solve the problem. however, apart from you
> and me there will be only a handful of people that will instantly know
> why this patch is correct :) could you resubmit with a proper
> description. a one liner is enough.
>
> John
>
> On 26/11/2014 19:38, Christian Schoenebeck wrote:
>> 1.) create user:group 2.) run postinst-pkg now you can change owner
>> and permission of installed files and directories in postinst-pkg
>> (Makefile/postinst) otherwise you can't 3.) clear luci cache 4.)
>> enable/start service
>>
>> Signed-off-by: Christian Schoenebeck
>> ---
>> package/base-files/files/lib/functions.sh | 7 +-- 1 file
>> changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/package/base-files/files/lib/functions.sh
>> b/package/base-files/files/lib/functions.sh index d53be3e..3d987cf
>> 100755 --- a/package/base-files/files/lib/functions.sh +++
>> b/package/base-files/files/lib/functions.sh @@ -173,7 +173,7 @@
>> default_prerm() { default_postinst() { local name rusers
>> name=$(echo $(basename $1) | cut -d. -f1) - [ -f
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] && ( .
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ) +
>> rusers=$(grep "Require-User:"
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.control) [ -n "$rusers"
>> ] && { local user group uid gid @@ -212,6 +212,10 @@
>> default_postinst() { done done } + + [ -f
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] && ( .
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ) + [ -n
>> "${IPKG_INSTROOT}" ] || rm -f /tmp/luci-indexcache 2>/dev/null + [
>> "$PKG_UPGRADE" = "1" ] || for i in `cat
>> ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.list | grep
>> "^/etc/init.d/"`; do [ -n "${IPKG_INSTROOT}" ] && $(which bash)
>> ${IPKG_INSTROOT}/etc/rc.common ${IPKG_INSTROOT}$i enable; \ [ -n
>> "${IPKG_INSTROOT}" ] || { @@ -219,7 +223,6 @@ default_postinst() {
>> $i start } done -[ -n "${IPKG_INSTROOT}" ] || rm -f
>> /tmp/luci-indexcache 2>/dev/null return 0 }
>>
>> ___ openwrt-devel
>> mailing list openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] kernel: 3.18: Fix patch 644 dependency chain
Le 07/11/2014 02:56, Maxime Ripard a écrit : > This patch introduces some code that is compiled in whenever > CONFIG_BRIDGE_NETFILTER is built, with the code called from code compiled > under > CONFIG_BRIDGE, CONFIG_BRIDGE_IGMP_SNOOPING or CONFIG_BRIDGE_NF_EBTABLES. > > Unfortunately, these options aren't setting explicitly the dependency they now > have on CONFIG_BRIDGE_NETFILTER, for obvious reasons for CONFIG_BRIDGE. > > However, this is not working really well when CONFIG_BRIDGE_NETFILTER is built > as a module, since code statically compiled will now use a function that is > not > in the kernel image, which makes the linker grumpy. > > Solve this by removing the option to build CONFIG_BRIDGE_NETFILTER as a > module, > and protect our function definition by an IS_BUILTIN instead of a IS_ENABLED > macro. This fixes the issue for CONFIG_BRIDGE and CONFIG_BRIDGE_IGMP_SNOOPING. > > Fixing CONFIG_BRIDGE_NF_EBTABLES has to be handled a bit differently, since it > directly references a variable that will not be declared if > CONFIG_BRIDGE_NETFILTER is not set. Protect the variable affectations by an > ifdef to make sure this doesn't happen. > > Signed-off-by: Maxime Ripard Applied in r43419, thanks! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 回复: O_DIRECT not supported on openwrt?
Hi, The problem is resolved. It is need to selected [make menuconfig]->[Global build settings]->[Compile the kernel with direct IO support]. zhenjun_...@icloudaegis.com 发件人： zhenjun_...@icloudaegis.com 发送时间： 2014-11-27 15:48 收件人： openwrt-devel 主题： O_DIRECT not supported on openwrt? Hi, I try to open file with O_DIRECT flag on openwrt, But error EINVAL is returned. I have selected O_DIRECT support in kernel_menuconfig. Are there any other configuration about this? Best Regards, zhenjun_...@icloudaegis.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-27 7:50 GMT-07:00 SGT. Garcia : > Michael and Alex are sending me USB<->COM cable and USB port[?] to get the > serial console going. I just sent you the following: http://www.amazon.ca/dp/B00AHYJWWG (USB/RS-232 converter with LEDs) http://www.amazon.ca/dp/B00MJUBKQ2 (cheap DB-9 cable to cut up and solder) There are obviously multiple ways to make this work, I'm just sending you the hardware that I would use if I did it myself. Happy Thanksgiving! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On 28 November 2014 at 04:39, Alex Henrie wrote: > 2014-11-27 7:50 GMT-07:00 SGT. Garcia : >> Michael and Alex are sending me USB<->COM cable and USB port[?] to get the >> serial console going. > > I just sent you the following: > > http://www.amazon.ca/dp/B00AHYJWWG (USB/RS-232 converter with LEDs) > http://www.amazon.ca/dp/B00MJUBKQ2 (cheap DB-9 cable to cut up and solder) > > There are obviously multiple ways to make this work, I'm just sending > you the hardware that I would use if I did it myself. You are not going to use RS-232 serial console with your router... right? Or are you trying to fry it on purpose? http://wiki.openwrt.org/doc/hardware/port.serial#voltage.levels You got a link to the simply & cheap USB <-> TTL UART converter on ebay... -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-27 23:55 GMT-07:00 Rafał Miłecki : > On 28 November 2014 at 04:39, Alex Henrie wrote: >> 2014-11-27 7:50 GMT-07:00 SGT. Garcia : >>> Michael and Alex are sending me USB<->COM cable and USB port[?] to get the >>> serial console going. >> >> I just sent you the following: >> >> http://www.amazon.ca/dp/B00AHYJWWG (USB/RS-232 converter with LEDs) >> http://www.amazon.ca/dp/B00MJUBKQ2 (cheap DB-9 cable to cut up and solder) >> >> There are obviously multiple ways to make this work, I'm just sending >> you the hardware that I would use if I did it myself. > > You are not going to use RS-232 serial console with your router... > right? Or are you trying to fry it on purpose? After I ordered it, I started wondering about the voltage levels...thanks for pointing out my mistake. I've canceled the order. Michael: At this point I think it would be best if you just sent SGT one of your cheap & simple converters as you suggested. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
