[OpenWrt-Devel] Images are too big in LEDE but not in OpenWRT

[Jakub Jančo]

Hello,

is there any reason why LEDE needs more empty space in firmware for
TP-link tl-wr1043nd v3 ?

In OpenWRT 15.01 we are building 7.3MB large images and have just
enought space for configs.
In LEDE 17.01 is max size ~6.5MB and we are not able to build our
images, because we cannot strip more packages, now we are on 6.8MB.

Is it possible to configure limits?

Thanks for help.

Number of duplicate files found 281
Number of inodes 2517
Number of files 2109
Number of fragments 55
Number of symbolic links  266
Number of device nodes 1
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 141
Number of ids (unique uids + gids) 1
Number of uids 1
root (0)
Number of gids 1
root (0)
13189+1 records in
13189+1 records out
6753020 bytes (6.8 MB) copied, 0.0269157 s, 251 MB/s
[mktplinkfw] kernel length aligned to 1360344
[mktplinkfw] *** error: images are too big by 249556 bytes
cp: cannot stat
'/var/lib/jenkins/workspace/openwrt-buildbot-17-01-imagebuilder/lede-imagebuilder-ar71xx-generic.Linux-x86_64/build_dir/target-mips_24kc_musl-1.1.16/linux-ar71xx_generic/tmp/lede-ar71xx-generic-tl-wr1043nd-v3-squashfs-sysupgrade.bin':
No such file or directory
13189+1 records in
13189+1 records out
6753020 bytes (6.8 MB) copied, 0.0267773 s, 252 MB/s
[mktplinkfw] kernel length aligned to 1360344
[mktplinkfw] *** error: images are too big by 249556 bytes
cp: cannot stat
'/var/lib/jenkins/workspace/openwrt-buildbot-17-01-imagebuilder/lede-imagebuilder-ar71xx-generic.Linux-x86_64/build_dir/target-mips_24kc_musl-1.1.16/linux-ar71xx_generic/tmp/lede-ar71xx-generic-tl-wr1043nd-v3-squashfs-factory.bin':
No such file or directory
padding image to 0068
padding image to 00671000
padding image to 00672000
padding image to 00674000
padding image to 0068
52+1 records in
53+0 records out
6946816 bytes (6.9 MB) copied, 0.00822619 s, 844 MB/s



--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Only first SSID has log_level=0

[Jakub Jančo]

TP-link 1043 has only one radio.
I have more SSIDs on this radio.

--
S pozdravom Jakub Janco


On Tue, Aug 8, 2017 at 9:13 PM, Jean-Michel Lacroix
<lacr...@lepine-lacroix.info> wrote:
> Wouldn't
>
> uci set wireless.radio1.log_level=0
>
> log the one from the second SSID?
>
> Jean-Michel
>
>
> ---
> Jean-Michel Lacroix
> 3303 place de Chazel
> Montréal (Québec)  H3M 1E2
> CANADA
>
> Le 2017-08-08 15:10, Jakub Jančo a écrit :
>>
>> Hello,
>>
>> I need to debug wireless connections so I set
>>
>> uci set wireless.radio0.log_level=0
>>
>> But this is logging only debug messages from first SSID, I need this
>> for all SSID on device.
>>
>> e.g.:
>> If I connect to first SSID(wlan0):
>> all daemon.debug mesages appears
>>
>>
>> If I connect to second AP(wlan0-1):
>> only daemon.info messages
>> IEEE 802.11: authenticated
>> IEEE 802.11: associated (aid 1)
>> WPA: pairwise key handshake completed (RSN)
>>
>> My setup:
>> TP-link 1043nd
>> OpenWRT 15.01.1
>> wpad full version
>>
>> What should I set to debug all?
>>
>> Thanks.
>>
>> --
>> S pozdravom Jakub Janco
>> ___
>> 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] Only first SSID has log_level=0

[Jakub Jančo]

Hello,

I need to debug wireless connections so I set

uci set wireless.radio0.log_level=0

But this is logging only debug messages from first SSID, I need this
for all SSID on device.

e.g.:
If I connect to first SSID(wlan0):
all daemon.debug mesages appears


If I connect to second AP(wlan0-1):
only daemon.info messages
IEEE 802.11: authenticated
IEEE 802.11: associated (aid 1)
WPA: pairwise key handshake completed (RSN)

My setup:
TP-link 1043nd
OpenWRT 15.01.1
wpad full version

What should I set to debug all?

Thanks.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenVPN server doesnt send AUTH_FAILED

[Jakub Jančo]

Hello,

can someone help please? Mainly openvpn masters :) - but it can be
another problem openssl? kernel? :-/ ...

Problem is that openvpn doesnt send/receive AUTH_FAILED when
auth-user-pass fails to verify.

I created thread in OpenVPN forum with all details:
https://forums.openvpn.net/topic21397.html#p60770

--
S pozdravom Jakub Janco


On Sun, Mar 27, 2016 at 12:10 PM, Jakub Jančo <kub...@gmail.com> wrote:
> Hello,
>
> I was testing this quite of time and I thought that upgrade package to
> 2.3.10 fixes problem, but maybe I mismatch binaries, because now when
> I need it again it doesnt work :(. On my PC(openvpn from arch repo) it
> works fine.
>
> Problem is that openvpn server doesnt send AUTH_FAILED - if auth
> script return non-zero return code. And this causes problems with
> windows clients(openvpn client freeze), but it is not comfortable for
> all clients, because client doesnt know if he enter right
> username,password.
>
> I tried a lot of combinations from compile config options, but none works.
>
> Can you help me with this magic please?
>
> Thanks.
>
> --
> S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] OpenVPN server doesnt send AUTH_FAILED

[Jakub Jančo]

Hello,

I was testing this quite of time and I thought that upgrade package to
2.3.10 fixes problem, but maybe I mismatch binaries, because now when
I need it again it doesnt work :(. On my PC(openvpn from arch repo) it
works fine.

Problem is that openvpn server doesnt send AUTH_FAILED - if auth
script return non-zero return code. And this causes problems with
windows clients(openvpn client freeze), but it is not comfortable for
all clients, because client doesnt know if he enter right
username,password.

I tried a lot of combinations from compile config options, but none works.

Can you help me with this magic please?

Thanks.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Current State of NCM support

[Jakub Jančo]

For me the main problem is that even single manufactor(huawei) build
firmwares for same proto(NCM) with non consistent config.
e.g. : one NCM works with /dev/cdc-wdm0, but another only with
/dev/ttyUSB0 event if it has cdc-wdm0.

1)
Your config should be OK for NCM, you can specify preferred
mode(onlylte,prefer lte ...)
luci-proto-3g, wwan are not required

2)
comgt - comgt binary, 3g support
comgt-ncm - adds suppot for NCM protocol - you can use NCM as proto
- you dont need wwan package

wwan - adds proto wwan - it is autoconfiguration for more usb modem
technologies - autodection of used usb modem and automatically choice
of best suited proto (3g, ncm an another 4g proto choices)
- you need comgt-ncm if you want use wwan with ncm dongle
- I have problem with this that it will find serial console on NCM
device and choose 3G proto instead of NCM

4)
luci-proto-3g - not required for ncm - it turns ncm into compatible 3g mode
- I use luci-proto-ncm from
https://sites.google.com/site/variousopenwrt/huawei-e3267 - but I
think it is not in official repo

In fact ncm can work with 3g, so you can use luci-proto-3g but it
turns ncm device to ppp mode with lower speeds.









--
S pozdravom Jakub Janco


On Sat, Mar 19, 2016 at 12:19 PM, Tristan Collins
 wrote:
> Hi there,
>
> Over the last year or so there has been some communication of issues / 
> improvements to NCM support with Openwrt, e.g.:
>
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-March/032225.html
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036345.html
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030890.html
> https://lists.openwrt.org/pipermail/openwrt-devel/2016-February/039551.html
> https://lists.openwrt.org/pipermail/openwrt-devel/2016-February/039562.html
>
> Can I check what is the 'correct' way to be using an NCM dongle (specifically 
> a Huawei E3276 in my case) and what behaviour should be expected?
>
> I'll be happy to update the wiki with the output of this.
>
> I have an old CC trunk build (r44497) from last year with some modifications 
> supplied by the contributors above. The packages I ended up installing (after 
> a lot of Googling and trial / error) were:
>
> comgt - 0.32-24
> comgt-ncm - 0.32-24
> kmod-usb-net-cdc-ether - 3.18.7-1
> kmod-usb-net-cdc-ncm - 3.18.7-1
> kmod-usb-net-huawei-cdc-ncm - 3.18.7-1
> kmod-usb-serial - 3.18.7-1
> kmod-usb-serial-option - 3.18.7-1
> kmod-usb-serial-wwan - 3.18.7-1
> kmod-usb-wdm - 3.18.7-1
> luci-proto-3g - git-15.050.70406-47603a3-1
> usb-modeswitch - 2014-08-26-993a9a542791953c4804f7ddbb3a07756738e37a
> wwan - 2014-07-17-1
>
> With these packages and the configuration below I have the behaviour I would 
> expect (hotplug working _most_ of the time).
>
> config interface 'wan'
>option proto 'ncm'
>option apn 'APNNAME'
>option username 'USRNAME'
>option password 'PASSWD'
>option device '/dev/cdc-wdm0'
>option delay '30'
>
> I've just done a clean build of CC (15.05) with what I _assumed_ were the 
> required packages as above.
>
> My questions are:
>
> 1) Are all these packages required and what is the correct config?
> 2) Are multiple packages providing the same functionality? e.g, comgt-ncm & 
> wwan?
> 3) Have the patches submitted over the last year made it in to CC 15.05.1 or 
> DD?
> 4) Are we any closer to having NCM dongles configured and operating info 
> provided via Luci?
>
> With the same configuration on the latest build the dongle connects on boot, 
> but not when hotplugged - ifup wan needs issued. (This behaviour was noted by 
> Thomas Baag on an email to devel on 11/12/2015, with a workaround)
>
> Aleksandr Kolesnik submitted patches to luci-proto-wwan to allow ncm 
> configuration via the wwan package. Has this been incorporated and does it 
> fit with the 'accepted' use of NCM dongles?
>
> It seems as though there was some lost progress when certain contributors 
> left but the code is still out there in a potentially usable form if 
> documented.
>
> Tristan
> ___
> 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] Fwd: [PATCH 1/2] wwan: Add support for CDC (Huawei 'HiLink') Modems

[Jakub Jančo]

I corrected filenames.

If someone want play with it:
In unlocksim.post the PIN code is not variabled.
--- config.sh
#!/bin/sh
gateway_ip="192.168.8.1"
base_url="http://${gateway_ip};
cookie_file="/tmp/cookie"
connect_data="connect.post"
connect_url="${base_url}/api/dialup/mobile-dataswitch"
unlocksim_data="unlocksim.post"
unlocksim_url="${base_url}/api/pin/operate"

token_url="${base_url}/html/home.html"
request_token=$(wget -q -t 0 "$token_url" -O - --save-cookies
"$cookie_file" --keep-session-cookies | grep csrf_token | head -n1 |
cut -d'"' -f4)
--
--- connect.sh
#!/bin/sh

. config.sh

[ -n "$request_token" ] || {
echo No request token found
exit 1
}

wget -q -t 0 --load-cookies "$cookie_file"
--header="__RequestVerificationToken: $request_token" \
   --post-file="$connect_data" "$connect_url" -O -
--
--- unlocksim.sh
#!/bin/sh

. config.sh

[ -n "$request_token" ] || {
echo No request token found
exit 1
}

wget -q -t 0 --load-cookies "$cookie_file"
--header="__RequestVerificationToken: $request_token" \
--post-file="$unlocksim_data" "$unlocksim_url" -O -
--
--- connect.post
0
--
--- unlocksim.post
0
--

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 1/2] wwan: Add support for CDC (Huawei 'HiLink') Modems

[Jakub Jančo]

On Tue, Mar 1, 2016 at 9:43 AM, John Crispin  wrote:
> i have spent ages thinking about this. the main problem is that the unit
> wont go online unless we previously set the apn/pin, ... in the webui.
> although having a unified wwan proto is great and we should have hilink
> support in it, i fear that this will be rather ambiguous to users as
> they set the pin in uci and then it wont get applied. so i have heavy
> heartedly decided to NAK this. i wish i had more time so we could hack
> up a tiny tool to set the webui setting from uci. although that is
> really would be an ugly hack.

By the way - mikrotik devices has PIN and APN settings for hilink too.
Maybe there are some devices which support it - it didnt work for me,
I had to set up things over webif.

I have done hack with wget to set PIN(huawei 3372h), but it is
umaintained for now and I cant test it because we have device on
"production" router.
Problem can be a lot of APIs. And it needs to be able use cookies and
post data.(If I remember I had to download full wget)


If someone want play with it:
In connect.post the PIN code is not variabled.
--- config.sh
#!/bin/sh
gateway_ip="192.168.8.1"
base_url="http://${gateway_ip};
cookie_file="/tmp/cookie"
connect_data="connect.post"
connect_url="${base_url}/api/dialup/mobile-dataswitch"
unlocksim_data="unlocksim.post"
unlocksim_url="${base_url}/api/pin/operate"

token_url="${base_url}/html/home.html"
request_token=$(wget -q -t 0 "$token_url" -O - --save-cookies
"$cookie_file" --keep-session-cookies | grep csrf_token | head -n1 |
cut -d'"' -f4)
--
--- connect.sh
#!/bin/sh

. config.sh

[ -n "$request_token" ] || {
echo No request token found
exit 1
}

wget -q -t 0 --load-cookies "$cookie_file"
--header="__RequestVerificationToken: $request_token" \
   --post-file="$connect_data" "$connect_url" -O -
--
--- unlocksim.sh
#!/bin/sh

. config.sh

[ -n "$request_token" ] || {
echo No request token found
exit 1
}

wget -q -t 0 --load-cookies "$cookie_file"
--header="__RequestVerificationToken: $request_token" \
--post-file="$unlocksim_data" "$unlocksim_url" -O -
--
--- connect.post
0
--
--- connect.post
0
--










--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Where init scripts are linked to rc.d?

[Jakub Jančo]

On Sat, Feb 27, 2016 at 2:12 AM, alzhao  wrote:
> Use /etc/init.d/yourscript enable
>
> It should be enabled by default, as I know.
Where do you put this command? I dont want do any tweaks after image is built.

As I found in ImageBuilder Makefiles, init scripts are enabled in
ImageBulder instead of firstboot and only init scripts which was
installed with opkg are enabled by default.
So my solution is hardcode links to $FILES/etc/rc.d/

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Where init scripts are linked to rc.d?

[Jakub Jančo]

Hello,

Im adding some custom init script in ImageBuilder throught FILES, but
these are not linked to /etc/rc.d on first boot.

Where to hook them?

If I make package, will it be linked automatically?

Thanks.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 1/2] wwan: Add support for CDC (Huawei 'HiLink') Modems

[Jakub Jančo]

It is not true. My 3372h may need PIN. It is on me if I disable PIN
verification in modem webif. Only problem is that it is not universal
- I need send http POST request to webif to unlock SIM, instead AT
cmd.
So maybe someone implement unlocking hilink modems on every start - so
we need PIN.

--
S pozdravom Jakub Janco


On Wed, Feb 24, 2016 at 7:11 AM, Matti Laakso  wrote:
>> Subject: Re: [OpenWrt-Devel] [PATCH 1/2] wwan: Add support for CDC (Huawei
>> 'HiLink') Modems
>> To: malaa...@elisanet.fi; openwrt-devel@lists.openwrt.org
>> CC: blo...@openwrt.org
>> From: b...@einfach.org
>> Date: Tue, 23 Feb 2016 17:26:33 +
>>
>> On 02/23/2016 07:11 AM, Matti Laakso wrote:
>> >> Huawei HiLink ("h" model names) modems just provide a CDC Ethernet
>> >> interface
>> >> where we have to run DHCP to get an IP address (usually in the
>> >> 192.168.8.0
>> >> range). While this may be bad design in general it's sometimes
>> >> necessary to
>> >> support these modems.
>> >>
>> >> This adds autodetection and handling of these to wwan.
>> >>
>> >> Tested with Huawei E3030h-1.
>> >
>> > Why do you need an extra protocol for these? They work just fine with
>> > the regular DHCP protocol.
>>
>> Hi, sorry I saw this so late... (cc: please).
>>
>> The reason is that I want different types of Modems to work with the
>> same interface configuration, using 'wwan'. E.g. it's configured like
>> this (/etc/config/network):
>>
>> config interface 'umts'
>> option proto wwan
>> option apn internet.eplus.de
>> option metric 4
>>
>> And it will work with PPP, QMI, MBIM, HiLink or whatever modem supported
>> by "wwan" (which are hopefully more and more)... Doesn't that make
>> sense? It would help the user who doesn't want to guess wether QMI works
>> better than PPP for a specific modem and which serial port to use, etc...
>>
>
> That's a good goal, but I think it's confusing for the user when apn and pin
> options don't work with HiLink modems but do work with all other modems
> handled by wwan.
>
> Matti
>
>
>
> ___
> 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 2/2] Add support for 'metric' to QMI, NCM, MBIM and DirectIP

[Jakub Jančo]

You should add all important options to networking:
metric
defaultroute
peerdns
These are important for remote management and dns resolving.

You can see my not yet applied patch http://patchwork.ozlabs.org/patch/581065/
It works for me.

--
S pozdravom Jakub Janco


On Wed, Feb 17, 2016 at 7:21 PM, Bruno Randolf  wrote:
> Same as for other network interfaces, the option 'metric' should be respected.
>
> (Unfortunately I could not test these changes, since I don't have these modems
> and QMI is broken on trunk for me... But the same method is used in the
> "HiLink" script I just added before.)
>
> Signed-off-by: Bruno Randolf 
> ---
>  package/network/utils/comgt/files/directip.sh  |  7 +--
>  package/network/utils/comgt/files/ncm.sh   |  7 +--
>  package/network/utils/umbim/files/lib/netifd/proto/mbim.sh |  7 +--
>  package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh   | 11 +++
>  4 files changed, 22 insertions(+), 10 deletions(-)
>
> diff --git a/package/network/utils/comgt/files/directip.sh 
> b/package/network/utils/comgt/files/directip.sh
> index d828052..048b647 100644
> --- a/package/network/utils/comgt/files/directip.sh
> +++ b/package/network/utils/comgt/files/directip.sh
> @@ -15,14 +15,15 @@ proto_directip_init_config() {
> proto_config_add_string "auth"
> proto_config_add_string "username"
> proto_config_add_string "password"
> +   proto_config_add_string "metric"
>  }
>
>  proto_directip_setup() {
> local interface="$1"
> local chat devpath devname
>
> -   local device apn pincode ifname auth username password
> -   json_get_vars device apn pincode auth username password
> +   local device apn pincode ifname auth username password metric
> +   json_get_vars device apn pincode auth username password metric
>
> [ -n "$ctl_device" ] && device=$ctl_device
>
> @@ -80,6 +81,7 @@ proto_directip_setup() {
> json_add_string name "${interface}_4"
> json_add_string ifname "@$interface"
> json_add_string proto "dhcp"
> +   json_add_int metric $metric
> ubus call network add_dynamic "$(json_dump)"
>
> json_init
> @@ -87,6 +89,7 @@ proto_directip_setup() {
> json_add_string ifname "@$interface"
> json_add_string proto "dhcpv6"
> json_add_string extendprefix 1
> +   json_add_int metric $metric
> ubus call network add_dynamic "$(json_dump)"
>
> return 0
> diff --git a/package/network/utils/comgt/files/ncm.sh 
> b/package/network/utils/comgt/files/ncm.sh
> index 571cfaa..39bdaaf 100644
> --- a/package/network/utils/comgt/files/ncm.sh
> +++ b/package/network/utils/comgt/files/ncm.sh
> @@ -19,6 +19,7 @@ proto_ncm_init_config() {
> proto_config_add_string mode
> proto_config_add_string pdptype
> proto_config_add_boolean ipv6
> +   proto_config_add_string metric
>  }
>
>  proto_ncm_setup() {
> @@ -26,8 +27,8 @@ proto_ncm_setup() {
>
> local manufacturer initialize setmode connect ifname devname devpath
>
> -   local device apn auth username password pincode delay mode pdptype 
> ipv6
> -   json_get_vars device apn auth username password pincode delay mode 
> pdptype ipv6
> +   local device apn auth username password pincode delay mode pdptype 
> ipv6 metric
> +   json_get_vars device apn auth username password pincode delay mode 
> pdptype ipv6 metric
>
> if [ "$ipv6" = 0 ]; then
> ipv6=""
> @@ -141,6 +142,7 @@ proto_ncm_setup() {
> json_add_string name "${interface}_4"
> json_add_string ifname "@$interface"
> json_add_string proto "dhcp"
> +   json_add_int metric $metric
> ubus call network add_dynamic "$(json_dump)"
>
> [ -n "$ipv6" ] && {
> @@ -149,6 +151,7 @@ proto_ncm_setup() {
> json_add_string ifname "@$interface"
> json_add_string proto "dhcpv6"
> json_add_string extendprefix 1
> +   json_add_int metric $metric
> ubus call network add_dynamic "$(json_dump)"
> }
>  }
> diff --git a/package/network/utils/umbim/files/lib/netifd/proto/mbim.sh 
> b/package/network/utils/umbim/files/lib/netifd/proto/mbim.sh
> index f8b2c06..ab62ed6 100755
> --- a/package/network/utils/umbim/files/lib/netifd/proto/mbim.sh
> +++ b/package/network/utils/umbim/files/lib/netifd/proto/mbim.sh
> @@ -17,6 +17,7 @@ proto_mbim_init_config() {
> proto_config_add_string auth
> proto_config_add_string username
> proto_config_add_string password
> +   proto_config_add_string metric
>  }
>
>  _proto_mbim_setup() {
> @@ -24,8 +25,8 @@ _proto_mbim_setup() {
> local tid=2
> local ret
>
> -   local device apn pincode delay
> -   json_get_vars device apn pincode delay auth username password
> +   local device apn pincode delay metric
> +   

Re: [OpenWrt-Devel] downloads.openwrt.org NOT accessible!!!

[Jakub Jančo]

Accessible:
$ host wiki.openwrt.org
wiki.openwrt.org has address 188.40.166.25

Not accessible:
$ host openwrt.org
openwrt.org has address 78.24.191.177
openwrt.org mail is handled by 10 mail.openwrt.org.

--
S pozdravom Jakub Janco


On Sat, Feb 13, 2016 at 9:44 AM, Jakub Jančo <kub...@gmail.com> wrote:
> Hello,
>
> I cant access to downloads.openwrt.org.
> This problem persist for about 3-4days.
> Maybe it is "local" problem, but I tried 2places in SK and 1place from
> CZ country, 2 machines, many routers.
>
>
> $ host downloads.openwrt.org
> downloads.openwrt.org has address 78.24.191.177
>
> $ ping 78.24.191.177
> PING 78.24.191.177 (78.24.191.177) 56(84) bytes of data.
> ^C
> --- 78.24.191.177 ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 999ms
>
> $ wget https://downloads.openwrt.org
> --2016-02-13 09:39:06--  https://downloads.openwrt.org/
> Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
> Connecting to downloads.openwrt.org
> (downloads.openwrt.org)|78.24.191.177|:443... failed: Connection timed
> out.
> Retrying.
>
> $ wget http://downloads.openwrt.org
> --2016-02-13 09:39:18--  http://downloads.openwrt.org/
> Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
> Connecting to downloads.openwrt.org
> (downloads.openwrt.org)|78.24.191.177|:80... failed: Connection timed
> out.
> Retrying.
>
>
>
>
> --
> S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] downloads.openwrt.org NOT accessible!!!

[Jakub Jančo]

Hello,

I cant access to downloads.openwrt.org.
This problem persist for about 3-4days.
Maybe it is "local" problem, but I tried 2places in SK and 1place from
CZ country, 2 machines, many routers.


$ host downloads.openwrt.org
downloads.openwrt.org has address 78.24.191.177

$ ping 78.24.191.177
PING 78.24.191.177 (78.24.191.177) 56(84) bytes of data.
^C
--- 78.24.191.177 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

$ wget https://downloads.openwrt.org
--2016-02-13 09:39:06--  https://downloads.openwrt.org/
Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
Connecting to downloads.openwrt.org
(downloads.openwrt.org)|78.24.191.177|:443... failed: Connection timed
out.
Retrying.

$ wget http://downloads.openwrt.org
--2016-02-13 09:39:18--  http://downloads.openwrt.org/
Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
Connecting to downloads.openwrt.org
(downloads.openwrt.org)|78.24.191.177|:80... failed: Connection timed
out.
Retrying.




--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Proto add foreign routes on ifup doesnt add route to table

[Jakub Jančo]

Hello,

Im working on proto for openvpn, and I want add route to vpn server.
I added

proto_add_ipv4_route 0.0.0.0 0 vpn_gw
proto_add_ipv4_route vpn.server.ip 32 wan_gw

But this will only add default route to table. In ifstatus both routes
are "active".

As a workaround I set route with ip command, but as I see in mailing
lists, things are changing, and somewhere can be ifconfig somewhere
iproute.

Thanks for help.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] LuCI FileUpload in network section

[Jakub Jančo]

Hello,

I'm trying to upload file in interface configuration, but it always
save file as value in config file. Is there something like switch to
upload original file?

I added this option to
/usr/lib/lua/luci/model/cbi/admin_network/proto_newproto.lua
---
op_tls_auth = section:taboption( "security", FileUpload, "tls_auth",
"Key file" )
---


And after Save or Save and apply


/etc/config/network

config interface 'test'
option proto 'newproto'
option tls_auth 'line1 filecontent
line2 filecontent
'


Thanks for help.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Overlayfs with tmpfs failed

[Jakub Jančo]

Hello, did anybody try make OpenWRT image as LiveCD?
I need it for learning purpose, but I cant mount overlay with tmpfs.
Need I some special build options?

--
S pozdravom Jakub Janco


On Wed, Nov 18, 2015 at 3:39 PM, Jakub Jančo <kub...@gmail.com> wrote:
> Hello,
>
> I have problem with setting up OpenWRT to Overlafs with tmpfs upper layer.
>
> $ mount -t overlay overlay -o lowerdir=/test1,upperdir=/test2,workdir=/work
> /test3
> mount: mounting overlay on /test3 failed: Invalid argument
>
> Can someone help me, where problem can be?
>
> Thanks.
>
>
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Overlayfs with tmpfs failed

[Jakub Jančo]

Hello,
I have problem with setting up OpenWRT to Overlafs with tmpfs upper layer.

$ mount -t overlay overlay -o
lowerdir=/test1,upperdir=/test2,workdir=/work /test3
mount: mounting overlay on /test3 failed: Invalid argument

Can someone help me, where problem can be?

Thanks.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Fwd: Removing Telnet

[Jakub Jančo]

Is slow login still present on ssh?
Because we had problem, that ssh login takes about 10seconds and
telnet is instant. It is difference if we do initial bulk setup for
more devices.
If I login to my pc, ssh login takes <1sec.

Thanks for reply.

--
S pozdravom Jakub Janco


2015-09-08 10:15 GMT+02:00 Steven Barth :
> Hello everyone,
>
> as of https://dev.openwrt.org/changeset/46809 telnet is no longer part of
> the base images. As a replacement, it is now possible to login to the root-
> account via SSH without a password prompt whenever no root password is set,
> e.g. after a flash without keeping config, factory reset or in failsafe.
>
> We will see how that goes. Let us know if there are any issues.
>
>
> Cheers,
>
> Steven
> ___
> 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] Fwd: Removing Telnet

[Jakub Jančo]

Vittorio is right. Some seconds I got with disabling testing all my
public keys. I tried add dns to /etc/hosts, but no gain.

It waits where Vittorio wrote. I searched for disabling ciphers but
didnt found anything. Probably it cannot be done.

--
S pozdravom Jakub Janco


2015-09-08 18:00 GMT+02:00 Vittorio G (VittGam) :
> Il 08.09.2015 17:42 Brent Thomson ha scritto:
>>
>> Slowness probably depends on hardware as well as all the possibilities
>> listed by others. I have a model of router that always takes 2-3
>> seconds to initiate an SSH connection, just to set up encryption
>> (brief, but computationally intensive; happens with every connection).
>> 10 seconds seems really slow, though. Smells like DNS.
>
>
> It might not be DNS in fact. On AR9331 (MIPS 24k CPU, not that fast...)
> starting from Barrier Breaker SSH is pretty slow (3-4 seconds), so on
> slower routers the login time can be longer.
>
> If you login with ssh -v, you can see that it waits between
>
>> debug1: expecting SSH2_MSG_KEXDH_REPLY
>
>
> and
>
>> debug1: Server host key: RSA [...]
>
>
> If you check the CPU usage on the router while the client is waiting for
> the reply, you can see that dropbear is at 100%.
>
> Cheers,
> Vittorio
> ___
> 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] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged

[Jakub Jančo]

Hello,
After I unplug cable:

ifconfig
eth0  Link encap:Ethernet  HWaddr 14:CC:20:4D:3D:B5
  inet addr:10.1.5.246  Bcast:10.1.5.255  Mask:255.255.255.0
  inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:747 errors:0 dropped:0 overruns:0 frame:0
  TX packets:896 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:84708 (82.7 KiB)  TX bytes:487679 (476.2 KiB)
  Interrupt:4

ip link
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff

After plug in cable, no change, no logs.

ModelTP-Link TL-WR1043N/ND v2 Firmware Version OpenWrt Barrier Breaker
14.07 / LuCI Trunk (svn-r10472) Kernel Version3.10.49



--
S pozdravom Jakub Janco

2015-05-15 9:34 GMT+02:00 Hans Dedecker dedec...@gmail.com:

 On Thu, May 14, 2015 at 10:45 PM, Jakub Jančo kub...@gmail.com wrote:
  No I havent, I thought it is Bring on boot but it is another option.
 So my
  problem persist.
  config interface 'wan'
  option ifname 'eth0'
  option proto 'dhcp'
  option metric '1'
 
  config interface 'wan6'
  option ifname '@wan'
  option proto 'dhcpv6'
 
  This is my wan config, and after turn off and on lan port on remote
 site, no
  logs entries.
 netifd relies on events from the kernel to detect link changes; when
 the cable is unplugged the NO_CARRIER flag of eth0 needs to be set
 which can be checked via the ip utility (ip link show) or ifconfig
 (RUNNING flag not set in this case). Further the cmd ubus call
 network.device status dumps the netifd status of the devices
 (including the link state).

 Hans
 
 
  2015-05-14 22:29 GMT+02:00 Hans Dedecker dedec...@gmail.com:
 
  On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote:
   Thank you for explanation.
  
   Why does openwrt use force_link on WAN, when it can break internet
   connection and remote access?
   Or what are advantages of force_link?
  I don't see any added value of using force_link on a WAN interface
  unless you would use a static IP address.
  You verified force_link is enabled on the WAN interface for your board ?
 
  Hans
  
   Thanks.
  
  
   --
   S pozdravom Jakub Janco
  
   2015-05-14 17:32 GMT+02:00 Hans Dedecker dedec...@gmail.com:
  
   On Wed, May 13, 2015 at 12:35 PM, Conor O'Gorman i...@conorogorman.net
 
   wrote:
On 12/05/15 17:57, Jakub Jančo wrote:
   
Hello,
   
I have tplink 1043nd with BB
   
Problem is that I have dhcp client on WAN and if I unplug cable
 from
WAN, it doesnt change status, give up dhcp address.
   
Even worse is that if I plug cable with another end point with
another
network, WAN dhcp client doesnt  pull new IP, I must click on
Connect
to refresh dhcp client, then new ip is assigned and internet
 works.
Or
restart device.
   
   
Have a look at ifpugd.
   
But maybe netifd should/could/might do something for this scenario?
   
Conor
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
   netifd has support for link state changes; the network interface will
   be brought up/down
   if the link is active/inactive. However if the force_link parameter
 is
   enabled for a network
   interface netifd will ignore link state changes.
  
   Hans
   ___
   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] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged

[Jakub Jančo]

This is my original switch config:

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 1 2 3 4'
option vid '1'

config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0t'
option vid '3'

config switch_vlan
option device 'switch0'
option vlan '3'
option ports '0t'
option vid '2'

config switch_vlan
option device 'switch0'
option vlan '4'
option vid '4'
option ports '0t'

config switch_vlan
option device 'switch0'
option vlan '5'
option vid '5'
option ports '5 6'

But in wiki they say that wan must be vlan2, but I didnt notice difference
if it is on vlan5.

Anyway I revert switch to original config and add force_link=0 for wan:
config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option metric '1'
option force_link '0'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option vid '1'
option ports '0 1 2 3 4'

config switch_vlan
option device 'switch0'
option vlan '2'
option vid '2'
option ports '5 6'




It seems that switch noticed link down on port 5:



$swconfig dev switch0 port 5 show
Port 5:
mib: Port 5 MIB counters
RxBroad : 65
RxPause : 0
RxMulti : 47
RxFcsErr: 0
RxAlignErr  : 0
RxRunt  : 0
RxFragment  : 0
Rx64Byte: 310
Rx128Byte   : 960
Rx256Byte   : 101
Rx512Byte   : 16
Rx1024Byte  : 62
Rx1518Byte  : 1
RxMaxByte   : 0
RxTooLong   : 0
RxGoodByte  : 149935
RxBadByte   : 0
RxOverFlow  : 0
Filtered: 0
TxBroad : 322
TxPause : 0
TxMulti : 0
TxUnderRun  : 0
Tx64Byte: 668
Tx128Byte   : 493
Tx256Byte   : 135
Tx512Byte   : 9
Tx1024Byte  : 12
Tx1518Byte  : 494
TxMaxByte   : 0
TxOverSize  : 0
TxByte  : 715736
TxCollision : 0
TxAbortCol  : 0
TxMultiCol  : 0
TxSingleCol : 0
TxExcDefer  : 0
TxDefer : 0
TxLateCol   : 0

pvid: 2
link: port:5 link:down


Link port 6 stays ON, probably because it is cpu.



--
S pozdravom Jakub Janco

2015-05-15 12:28 GMT+02:00 Conor O'Gorman i...@conorogorman.net:

 On 15/05/15 10:48, Jakub Jančo wrote:

 Hello,
 After I unplug cable:

 ifconfig
 eth0  Link encap:Ethernet  HWaddr 14:CC:20:4D:3D:B5
inet addr:10.1.5.246  Bcast:10.1.5.255  Mask:255.255.255.0
inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:747 errors:0 dropped:0 overruns:0 frame:0
TX packets:896 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:84708 (82.7 KiB)  TX bytes:487679 (476.2 KiB)
Interrupt:4

 ip link
 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state
 UP mode DEFAULT group default qlen 1000
  link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff

 After plug in cable, no change, no logs.

 ModelTP-Link TL-WR1043N/ND v2 Firmware Version OpenWrt Barrier Breaker
 14.07 / LuCI Trunk (svn-r10472) Kernel Version3.10.49


 Do you have the switch configured correctly? You can use swconfig to check
 the physical port status.
 http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd
 ___
 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] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged

[Jakub Jančo]

Thank you for explanation.

Why does openwrt use force_link on WAN, when it can break internet
connection and remote access?
Or what are advantages of force_link?

Thanks.


--
S pozdravom Jakub Janco

2015-05-14 17:32 GMT+02:00 Hans Dedecker dedec...@gmail.com:

 On Wed, May 13, 2015 at 12:35 PM, Conor O'Gorman i...@conorogorman.net
 wrote:
  On 12/05/15 17:57, Jakub Jančo wrote:
 
  Hello,
 
  I have tplink 1043nd with BB
 
  Problem is that I have dhcp client on WAN and if I unplug cable from
  WAN, it doesnt change status, give up dhcp address.
 
  Even worse is that if I plug cable with another end point with another
  network, WAN dhcp client doesnt  pull new IP, I must click on Connect
  to refresh dhcp client, then new ip is assigned and internet works. Or
  restart device.
 
 
  Have a look at ifpugd.
 
  But maybe netifd should/could/might do something for this scenario?
 
  Conor
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 netifd has support for link state changes; the network interface will
 be brought up/down
 if the link is active/inactive. However if the force_link parameter is
 enabled for a network
 interface netifd will ignore link state changes.

 Hans
 ___
 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] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged

[Jakub Jančo]

No I havent, I thought it is Bring on boot but it is another option. So
my problem persist.
config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option metric '1'

config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'

This is my wan config, and after turn off and on lan port on remote site,
no logs entries.


--
S pozdravom Jakub Janco

2015-05-14 22:29 GMT+02:00 Hans Dedecker dedec...@gmail.com:

 On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote:
  Thank you for explanation.
 
  Why does openwrt use force_link on WAN, when it can break internet
  connection and remote access?
  Or what are advantages of force_link?
 I don't see any added value of using force_link on a WAN interface
 unless you would use a static IP address.
 You verified force_link is enabled on the WAN interface for your board ?

 Hans
 
  Thanks.
 
 
  --
  S pozdravom Jakub Janco
 
  2015-05-14 17:32 GMT+02:00 Hans Dedecker dedec...@gmail.com:
 
  On Wed, May 13, 2015 at 12:35 PM, Conor O'Gorman i...@conorogorman.net
  wrote:
   On 12/05/15 17:57, Jakub Jančo wrote:
  
   Hello,
  
   I have tplink 1043nd with BB
  
   Problem is that I have dhcp client on WAN and if I unplug cable from
   WAN, it doesnt change status, give up dhcp address.
  
   Even worse is that if I plug cable with another end point with
 another
   network, WAN dhcp client doesnt  pull new IP, I must click on
 Connect
   to refresh dhcp client, then new ip is assigned and internet works.
 Or
   restart device.
  
  
   Have a look at ifpugd.
  
   But maybe netifd should/could/might do something for this scenario?
  
   Conor
   ___
   openwrt-devel mailing list
   openwrt-devel@lists.openwrt.org
   https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  netifd has support for link state changes; the network interface will
  be brought up/down
  if the link is active/inactive. However if the force_link parameter is
  enabled for a network
  interface netifd will ignore link state changes.
 
  Hans
  ___
  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] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged

[Jakub Jančo]

Hello,

I have tplink 1043nd with BB

Problem is that I have dhcp client on WAN and if I unplug cable from WAN,
it doesnt change status, give up dhcp address.

Even worse is that if I plug cable with another end point with another
network, WAN dhcp client doesnt  pull new IP, I must click on Connect to
refresh dhcp client, then new ip is assigned and internet works. Or restart
device.


Thanks for help.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] xl2tpd in squash not recognized in Luci

[Jakub Jančo]

Hello,

please what can I do to recognize this package if it is in built in fw?

I continuously have built images for tplink 842n, 1043nd, wdr3500 since
half 2014 with package xl2tpd, but it was never recognized. Luci says
install xl2tpd so I must remove package and install package again on
every device.

Thanks.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Query serial number from device

[Jakub Jančo]

Hello,

I found model string, but I cant found serial number of device.

Can be serial number read from openwrt?

Thanks.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Desktop configuring tool

[Jakub Jančo]

Hello,

does exist something like winbox for mikrotik?
It should be owrt api(UCI+ssh for example) and desktop GUI. Then I dont
need compile LuCI and save place in 2-4MB router. Maybe someone can port
LuCI app to run on desktop and send commands via ssh to device.

Thanks for info.

--
S pozdravom Jakub Janco
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel