Paul Oranje writes:
> Small addition (the following may be non-obvious to those not involved
> in this discussion). Just saw that A_TA does not have renewal (T1) or
> rebinding (T2) fields and for that reason cannot suit a use-case like
> a IA just for a work shift.
RFC 3315 section 22.5:
A
Hello,
Many devices make use of "dual firmware" configurations, splitting the
available flash and allowing two complete and independent installations.
This works fine for devices like the Linksys WRT1900AC etc, where the
boot loader make sure the kernel command line "root=" parameter matches
the b
Alberto Bursi writes:
> Can this "bs" partition be manipulated on installation or later?
Yes. The only thing preventing that is the default "(ro)" in the LEDE
images. But by using mtd-rw it can be manipulated. That's how I fixed
my installation.
I believe there are tools to manipulate it in
Roman Spychała writes:
> diff --git
> a/target/linux/generic/patches-4.4/870-usb-plusb-Add-support-for-PL-27A1.patch
>
> b/target/linux/generic/patches-4.4/870-usb-plusb-Add-support-for-PL-27A1.patch
> new file mode 100644
> index 00..794a861993
> --- /dev/null
> +++
> b/target/linux/
Hello,
I note that a recent commit to the lede-17.01 branch has added a few
driver patches which have barely hit the mainline kernel:
https://github.com/lede-project/source/commit/1ab41265c39354332630bcba0ec704abd2e790f0
This surprised me quite a bit. I would expect any such fixes to go the
nor
Mathias Kresin writes:
> I had a similar problem with the dual image feature of brnboot in
> lantiq. It resulted in the following two patches:
>
> https://git.lede-project.org/d7438ce3152e2e0dc1678dcb24ca050dbc2733c8
> https://git.lede-project.org/60ac4852745c69ae13a770dc343b648925b73ca2
>
> Sinc
Ермошкин А.Ю. writes:
> This patch adds support for the ZTE usb modem MF667 in rndis/network card
> mode.
>
> generic/099-usb-cdc_ether-zte-update.patch
> generic/774-net-usb-cdc_ether-quirks-for-zte-mf667.patch
Any reason why the first patch isn't simply a backport of mainline
commit bfe9b9d2d
Kevin Darbyshire-Bryant writes:
> CVE-2018-9078 https://secure.ucc.asn.au/hg/dropbear/rev/c8114a48837c
2018? Early fix, I guess :-)
Bjørn
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Rafał Miłecki writes:
> From: Rafał Miłecki
>
> Counting commits to determine revision number is a wrong idea when there
> are branches in a project. This could generate the same revision for
> different git commits, e.g.:
>
> For master branch:
> ./scripts/getver.sh bb9d2aa868
> r3438-bb9d2aa86
This looks yucky. Experimenting a bit, I see that the result with
a) -T 0 depends on multi-core vs single-core
b) -T 1 is always different from the output of -T x where x > 1
c) -T x where x > 1 is independent of both x and the actual number of
cores
So you will not get reproducible resul
Shelly Coen writes:
> Hi Everyone,
>
> The prplWrt Working Group has compiled a survey on the subject of how
> OpenWrt/LEDE is used.
>
> We would really appreciate if you could take some time to complete this short
> survey to help give us a valuable oversight of this. We will present the
> re
Note that security is the usual (only?) reason one would enforce TTL=255.
Requiring TTL=255 is the same as guaranteeing that the packet source is
in the same L2 domain. This prevents any direct remote attack.
Please do not propose any patches removing such a restriction without at
least explainin
Matthias May writes:
> While unfortunate that the actual patch which got merged didn't have the
> explanation why the patch was done, if you look
> at the mailing list archive you will see that there was a thread discussing
> this topic:
> http://lists.infradead.org/pipermail/lede-dev/2017-Sept
David Lang writes:
> 17.01 is pointer to a particular commit on the master branch
>
> I haven't looked at the specific method used for the r# generation,
> but I think it's incremented daily
No, it counts commits. See scripts/getver.sh
The method was discussed when the current scheme was commi
Matthias Schiffer writes:
> Fixing our revision numbering to include the branch name to make this more
> or less unambiguous is the intent of the two patches I linked. The commit
> ID should still be included in this revision number (e.g.
> lede-17.01-r9000-abcdef), as developers could still set
Koen Vandeputte writes:
> @@ -99,6 +99,13 @@ proto_qmi_setup() {
>
> uqmi -s -d "$device" --set-data-format 802.3
> uqmi -s -d "$device" --wda-set-data-format 802.3
> + dataformat="$(uqmi -s -d "$device" --wda-get-data-format)"
> +
> + if [ "$dataformat" = '"raw-ip"' ]; then
Koen Vandeputte writes:
> On 2017-11-27 17:53, Bjørn Mork wrote:
>> Koen Vandeputte writes:
>>
>>> @@ -99,6 +99,13 @@ proto_qmi_setup() {
>>> uqmi -s -d "$device" --set-data-format 802.3
>>> uqmi -s -d "$device"
Quanta mode was introduced in usb_modeswitch 1.2.6 and Blackberry
mode in usb_modeswitch 1.2.7
Signed-off-by: Bjørn Mork
---
convert-modeswitch.pl | 2 ++
switch.c | 21 +
2 files changed, 23 insertions(+)
diff --git a/convert-modeswitch.pl b/convert
USB_ModeSwitch version 2.3.0 introduced "OptionMode".
Signed-off-by: Bjørn Mork
---
convert-modeswitch.pl | 1 +
switch.c | 16
2 files changed, 17 insertions(+)
diff --git a/convert-modeswitch.pl b/convert-modeswitch.pl
index 6930e5f8d668..71c2b7950
he Pantech support, as it complicates stuff quite a bit
for little gain AFAICS. But it's there if you want it.
This is build tested only. I dont' own any of the affected modems.
Bjørn Mork (3):
fix support for Option modems
support Quanta and Blackberry modes
support PantechMode
c
The behaviour of the usb_modeswitch "Pantech" mode depends on the
option value, so we need to propagate this via the json config to
the usbmode tool.
Signed-off-by: Bjørn Mork
---
convert-modeswitch.pl | 9 +
switch.c | 16
2 files changed, 25
Julian Labus writes:
> diff --git a/package/utils/usbmode/Makefile b/package/utils/usbmode/Makefile
> index 7f0195fdce..1b1ef147b6 100644
> --- a/package/utils/usbmode/Makefile
> +++ b/package/utils/usbmode/Makefile
> @@ -40,8 +40,13 @@ endef
> define Build/Prepare
> $(Build/Prepare/Defaul
Julian Labus writes:
> On 12/22/2017 10:48 AM, Bjørn Mork wrote:
>> Julian Labus writes:
>>
>>> diff --git a/package/utils/usbmode/Makefile b/package/utils/usbmode/Makefile
>>> index 7f0195fdce..1b1ef147b6 100644
>>> --- a/package/utils/usbmode/Makefil
Koen Vandeputte writes:
> On 07-02-18 22:14, Levente Kovacs wrote:
>> On Wed, 7 Feb 2018 13:23:25 +0100
>> Koen Vandeputte wrote:
>>
Quectel EC25-A
>> Does the EC25 work without any kernel patch? I was testing EC25 with 17.01.1,
>> and it was working only with a kernel patch. Can you give m
Bjørn Mork writes:
> Backporting the raw-ip feature to v4.4 is simple. Just cherry-pick
>
> 81e0ce79f291 ("usbnet: allow mini-drivers to consume L2 headers")
> 32f7adf633b9 ("net: qmi_wwan: support "raw IP" mode")
> 6c730080e663 ("net: qmi
Rosen Penev writes:
> curl is more common than GNU wget is.
No.
> For example, Cygwin, Arch Linux, and my android phone all come with
> curl by default whereas wget is missing.
wget has priority "important" in Debian, while curl is "optional".
I don't think it makes much sense to tune the ins
Rosen Penev writes:
> On Sat, Mar 10, 2018 at 3:31 AM, Bjørn Mork wrote:
>> Rosen Penev writes:
>>
>>> curl is more common than GNU wget is.
>>
>> No.
> Yes.
How about throwing in an actual argument why you think it is? Or why it
makes curl a better
commit 6ed389da85a9 ("base-files: sysupgrade: do not rely on opkg
to list changed conffile") adds a call to sha256sum. Make sure it
exists.
Signed-off-by: Bjørn Mork
---
You'll see this unless you select sha256sum:
root@wrt1900ac-1:~# sysupgrade -b /tmp/foo
/sbin/sysupgrad
Matthias Schiffer writes:
> We generally do no add dependencies for busybox applets that are enabled by
> default - otherwise, we would also need to add dependencies for sed, awk,
> grep, etc. When you change the busybox configuration, you are on your own,
> and you should regularly check the out
Great!
Note that the OpenWrt usbreset utility has been included in this version
of usbutils. usbreset is currently packaged separately with its source.
Maybe consider merging the two source packages and start building
usbreset as part of the usbutils package?
Bjørn
___
mba support.
Link: https://forum.lede-project.org/t/wrt1900acv1-reboots-kernel-4-9/2025
Signed-off-by: Bjørn Mork
---
target/linux/mvebu/config-4.14 | 4
1 file changed, 4 deletions(-)
diff --git a/target/linux/mvebu/config-4.14 b/target/linux/mvebu/config-4.14
index 5286bf9b8314..78bed5b32
Felix Fietkau writes:
> On 2018-03-19 10:51, Bjørn Mork wrote:
>> A regression seriously affecting the Linksys WRT1900ACv1 (Mamba) was
>> introduced some time between the OpenWrti/LEDE v4.4 and v4.9 kernels.
>> The root cause has not yet been identified, despite many attemp
Cezary Jackiewicz writes:
> Dnia 2016-10-31, o godz. 19:17:38
> "Giuseppe Lippolis" napisał(a):
>
>> Hallo,
>> I'm completing the support for the dlink dwr-512 adding the support for 3G.
>> In order to enable the 3G modem the following step need to be performed:
>>
>> 1) write '1' to the gpio18
Bastian Bittorf writes:
> i'am using LEDE with target UML and rr2155 and has this problem:
>
> root@uml:/ df -h
> FilesystemSize Used Available Use% Mounted on
> /dev/root15.7M 12.3M 3.1M 80% /
> tmpfs12.5M320.0K 12.2M 3
Bastian Bittorf writes:
> * Bjørn Mork [11.11.2016 14:58]:
>> > in fact there is enough space, but not useable.
>>
>> And "df -i" says?
>
> this seems not supported by the busybox applet, but
> on the host i can see this:
>
> bastian@LEDE:/home/
Felix Fietkau writes:
> On 2016-11-22 12:47, Mogens Lauridsen wrote:
>> Hi,
>>
>> I found a memory overwrite causing a crash when using uqmi and
>> qmi-via-mbim such as:
>> uqmi -m -d /dev/cdc-wdm0 --get-signal-info
>>
>> The problem is missing space for mbim header, which is assumed in
>> qmi_
Felix Fietkau writes:
> On 2016-11-22 14:10, Mogens Lauridsen wrote:
>> Seems like a better fix, but it doesn't work. uqmi hangs, so I suspect
>> that EM7455 has misunderstood the command. I have removed/replaced the
>> ustream_write(..,..,.., true) and after the changes below it works.
>> I gues
"Giuseppe Lippolis" writes:
> Currently I'm able to establish a connection setting the interface in
> "manual" mode.
>
> To do this I setup an usb interface
>
> config interface 'wan3g'
> option ifname 'usb0'
> option proto 'dhcp'
>
> then I need to send manually the following com
"Giuseppe Lippolis" writes:
> Dear Bjørn,
>
>> Nice. The "M-MBIM" is a bit confusing, though. This doesn't seem to have
>> anything to do with MBIM?
>>
> I'm just recompiled an image with mbim, ncm support.
>
> But I don't know if it is the right driver.
> If I send the cmd
> echo '2001 7d04'
"Giuseppe Lippolis" writes:
> Dear Bjørn, Matti,
>
>> I don't think it is relevant for you, though. You should continue your
>> initial
>> idea, creating a "proto" supporting the AT managed cdc_ether based
>> modem.
>
> I add a pull request here:
>
> https://github.com/lede-project/source/pull/
Petr Štetiar writes:
> Matti Laakso [2016-12-08 15:39:57]:
>
> Hi,
>
>> I don't like the autoconnect at all, it being so unpredictable across
>> various models.
>
> This autoconnect feature should burn in hell :-) The funny thing about this
> feature is, that the behaviour is network specific[1]
Matti Laakso writes:
> On 12.12.2016 08:52, Petr Štetiar wrote:
>> Matti Laakso [2016-12-09 11:35:35]:
>>
>>> On 09.12.2016 11:27, Petr Štetiar wrote:
I knew, that there's only one profile defined, operator has deleted all
other
profiles, there's currently only one APN defined.
>>
Petr Štetiar writes:
> Adding laforge and zecke to the Cc loop.
>
> Matti Laakso [2017-01-08 14:39:34]:
>
> Hi,
>
>> I'm almost done with checking the connection state using a proto_run_command
>> with a simple script running uqmi --get-data-status periodically. If the
>> check fails, the script
Petr Štetiar writes:
> Bjørn Mork [2017-01-08 23:10:20]:
>
>> The output above comes from the Sierra Wireless EM7455 originally delivered
>> as part of my Lenovo X1 Carbon, running bog standard firmare.
>
> Oops. How did you get into the shell of your modem? Is it a
Harald Welte writes:
> On Sun, Jan 08, 2017 at 11:10:20PM +0100, Bjørn Mork wrote:
>> Note that there is nothing Quectel here. This is a standard Qualcomm
>> platform. The output above comes from the Sierra Wireless EM7455
>> originally delivered as part of my Lenovo X
Eric Luehrsen writes:
> IP6 SLAAC plus privacy is common. DHCPv6 should be able to provide
> the same funciton. This way central IT can maintain integrity and
> traceability. However, individual machines will not be easily
> placed into a pattern over time by external snooping.
This looks wrong.
Eric Luehrsen writes:
> It appears many other severs and clients dont implement IA_TA. Its a lost
> option.
Sure. Very few want this feature. We must however assume that those
who do want it will implement it.
> It should not break "expectations" as this an central administrative
> option.
Rafał Miłecki writes:
> -# Copyright (C) 2007 OpenWrt.org
> +# Copyright (C) 2016 LEDE project
I've always wondered about the OpenWrt copyright assigment process, and
this looks like a perfect opportunity to clear that up. Why do you
assign the copyright to the project? What are the formalitie
Hauke Mehrtens writes:
> On 05/09/2016 10:19 PM, Bjørn Mork wrote:
>
>> How do you ensure that they use the code only like you intended after you
>> donated it?
> This copyright notice is useless. The copyright will stay at the
> individual author. At least in Germany
John Crispin writes:
> On 09/05/2016 09:44, David Lang wrote:
>
>> I don't think that will be possible because it's different people
>> working on each tree. I know the OpenWRT folks deleted the @openwrt
>> e-mail addresses for the people working on LEDE. I would assume that
>> they have blocked c
John Crispin writes:
> On 19/05/2016 14:48, Bjørn Mork wrote:
>> John Crispin writes:
>>> On 09/05/2016 09:44, David Lang wrote:
>>>
>>>> I don't think that will be possible because it's different people
>>>> working on each tr
Daniel Curran-Dickinson writes:
> I wasn't meaning it to be hostile (the other guy I think was),
who? me? No, grumpy is just my default mode. I need to work on that.
But I never rant without caring, so "hostile" is not correct.
Anyway, I want to apologize for breaking the "Be nice to eachother
Dheeran Senthilvel writes:
>> Its gonna take a while before either Linksys just releases a proper
>> working drivers (or) just releases the code under GPL for upstream
>> kernel-development (Just like what happened for raspberrypi).
This is wrong. The mwlwifi driver is GPL and has been so for y
Petr Štetiar writes:
> More info at https://www.kernel.org/introducing-fastly-cdn.html
>
> Signed-off-by: Petr Štetiar
> ---
> scripts/download.pl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/download.pl b/scripts/download.pl
> index 548eb7a..ec7067b 100755
>
Felix Fietkau writes:
> On 2016-05-23 12:29, Petr Štetiar wrote:
>> Felix Fietkau [2016-05-23 11:11:50]:
>>
>>> On 2016-05-23 10:29, Bjørn Mork wrote:
>>> > Petr Štetiar writes:
>>> >
>>> >> -
Arjen de Korte writes:
> Since GitHub apparently also uses Fastly as CDN provider, building on
> a machine with IPv6 only connectivity is going to be difficult anyway.
> Using both won't hurt, but if you're not able to connect to an IPv4
> server for the kernel sources, you'll likely run into sim
Zoltan HERPAI writes:
>> On 05/24/2016 10:31 PM, Hauke Mehrtens wrote:
>>
>> This is my personal opinion and this was not somehow internally planned
>> with other LEDE people.
>
> If I start a discussion about my employer-related topics along a beer
> with a couple friends, that's a private discus
mbm writes:
> The hackers email address represents the primary point of contact for
> OpenWrt, particularly in regards to donations. Following the surprise
> LEDE announcement, forwarding rules for @openwrt.org email addresses
> were disabled. This was done to mitigate further damage to OpenWrt d
Alexey Brodkin writes:
> Hello,
>
> I think it would be quite convenient to add info about URLs
> that could be used for accessing Lede repos via git.
>
> In OpenWRT Git Web we had something like that:
> --->8---
> URL http://git.openwrt.org/openwrt.git
>
g the '-t X' option:
$ umbim -d /dev/cdc-wdm0 -t 2 caps
devicetype: 0003 - remote
cellularclass: 0001
voiceclass: 0001 - no-voice
simclass: 0002
dataclass: 003C
smscaps: 0003
controlcaps: 0001
maxsessions: 0008
deviceid: 0145820007x
firmwareinfo: SWI9X30C_0
C Authentication" support. There
are no TLVs associated with this request, so it is pretty simple.
Bjørn Mork (2):
uqmi: add support for MBIM devices with QMI service
dms: add "Set FCC Authentication" request
CMakeLists.txt| 2 +-
commands-dms.c|
thentication
feature enabled:
$ umbim -d /dev/cdc-wdm0 -n radio
hwradiostate: on
swradiostate: off
$ uqmi -m -d /dev/cdc-wdm0 --fcc-auth
$ umbim -d /dev/cdc-wdm0 -t 2 radio
hwradiostate: on
swradiostate: on
Signed-off-by: Bjørn Mork
---
commands-dms.c| 8 ++
commands-d
All MBIM integer fields are 32bit little endian. So we need to convert
then all on big endian systems.
Fixes: e69bf24b00d8 ("uqmi: add support for MBIM devices with QMI service")
Signed-off-by: Bjørn Mork
---
mbim.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
di
Felix Fietkau writes:
> Applied with some cleanups and portability fixes.
> I changed the code to use __packed and endian conversion from libubox.
Thanks! Sorry about the sloppy implementation. I guess I expected it to
come back with a "changes requested" instead of just fixed up and
applied ;)
ns found on MTD device firmware
[1.728233] 0x0040-0x005e : "kernel"
[1.739291] 0x005e-0x0440 : "ubi"
[1.750251] 0x0440-0x0450 : "Private"
[1.761403] 0x0450-0x05500000 : "Log"
[1.7719
Bjørn Mork writes:
> This is achieved by registering in the reverse order.
No, that is not true. Drop this. I tricked myself by disabling
debugging while making changes. Stupid...
The points for further work are valid though.
Bjørn
___
Lede-
Hello,
I apologize for bringing up this long-standing issue at a time where you
all have need to other issues to take care of. But it's again become a
real pressing issue, at least seen from the networks I have a presence in.
The main problem is that there still hasn't been any update to the
*te
Jo-Philipp Wich writes:
> Hi Joerg, John.
>
> I created an openwrt.org zone on Digital Ocean now so you could delegate
> the name servers to ns1.digitalocean.com, ns2.digitalocean.com and
> ns3.digitalocean.com, maybe with one of the SPI machines thrown into the
> mix...
Good! I hope you implici
John Crispin writes:
> On 06/05/18 22:44, Joerg Jaspert wrote:
>> On 15029 March 1977, Bjørn Mork wrote:
>>
>>> 1) update the .org delegation to include *all* NS records for the
>>> openwrt.org zone
>> I added the soapstone one to the registrar for now,
michael.g...@lantisproject.com writes:
> + &nand {
> + /* Spansion S34ML02G2 256MiB, OEM Layout */
> + partition@0 {
> + label = "u-boot";
> + reg = <0x000 0x20>; /* 2MB */
> +
70 matches
Mail list logo
