The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Move dropbear failsafe code out of
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Move dropbear failsafe code out of
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Rekey GTK on STA disassociate
Sig
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Allows dtim_period to be configura
I'm adding hotplug.d support to all DHCP events.
For now only dnsmasq triggers them, with
openwrt/package/network/services/dnsmasq/files/dhcp-script.sh
DHCP clients like udcpc and udcp6c are easy to add as the client calls
a script hook with documented arguments and environment
variables I can pa
Hi,
The OpenWrt community is proud to announce the first release candidate
of the upcoming OpenWrt 19.07 stable version series. It incorporates
over 3700 commits since branching the previous OpenWrt 18.06 release and
has been under development for about one a half year.
With this release the Ope
Hi Christian,
> -Original Message-
> From: Christian Lamparter [mailto:chunk...@gmail.com]
> Sent: Freitag, 8. November 2019 19:46
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: ipq40xx: Bogus IMAGE_SIZE on asus rt-ac58u
>
> Hello,
>
> On Tuesday, November
Hello,
On Tuesday, November 5, 2019 8:13:59 PM CET Adrian Schmutzler wrote:
> as stated already in the comment of an earlier patch, the asus_rt-ac58u
> on ipq40xx target has an IMAGE_SIZE of 20439364, which cannot be divided
> by 1024 and also does not seem to match anything in DTS.
This was soo
Cc: Robert Marko
This is a pick of commits from device support PR #2417:
https://github.com/openwrt/openwrt/pull/2417
There has been a request to merge those particular commits,
as they are required for any 60 GHz capable device, so
merging them will obviously make things easier for other
develo
From: Robert Marko
This patch enables hostapd.sh to properly configure wpa_supplicant
for when GCMP is used as cipher in station mode.
Without this wpa_supplicant will be unable to connect to AP.
This is needed for wil6210 as it does not support CCMP.
Signed-off-by: Robert Marko
[remove empty d
From: Robert Marko
This patch adds 802.11ad support by adding 11ad hwmode identifier.
This way hostapd.sh requires no modifications as for 802.11ad only
hwmode and channel are needed as channel width is fixed to 2160MHz
and there are no HT modes.
Signed-off-by: Robert Marko
---
package/base-fi
From: Robert Marko
This patch adds support for 802.11ad to mac80211.sh script.
It checks whether device supports 802.11ad Channel 1 and if so
configures it to channel 1 and ad hwmode.
htmode is not needed for 802.11ad.
Signed-off-by: Robert Marko
[rewrite if/else logic in mac80211.sh]
Signed-of
From: Robert Marko
This patch adds wil6210 driver for Wilocity/QCA based 802.11ad
PCI cards.
Driver uses cfg80211 and nl80211 but not mac80211.
Integration for UCI and LuCI will come in other patches.
Signed-off-by: Robert Marko
---
package/kernel/mac80211/ath.mk | 18 +++---
1 fi
From: Robert Marko
This patch adds wil6210 firmware and board files.
Firmware version is not up to date but is only freely
redistributable one I found.
Board file is a generic one so most devices and especially those
for long distance PtP links will require so in a ipq-wifi like way.
Signed-off-
On Fri, Nov 08, 2019 at 07:41:33PM +0300, Paul Fertser wrote:
> "lp" might be a "language pack" which is to be downloaded and
> flashed separately when using vendor firmware.
One forum post[1] says that the only language pack the person was able
to ever find for this device was for "taiwanese lang
Hi Adrian,
On Fri, Nov 08, 2019 at 03:53:59PM +0100, Adrian Schmutzler wrote:
> > With that I have 6 eraseblocks left for the rootfs_data partition (5
> > is the absolute minimum jffs2 allows).
> >
> > > Be aware that you might not find someone willing to merge this.
> >
> > I do not think this
thanks Adrian!
Yeah sure, I'll do this soon (e.g.: tomorrow, if all goes according to plans).
thanks again,
Enrico
On Fri, 8 Nov 2019, Adrian Schmutzler wrote:
Date: Fri, 8 Nov 2019 16:27:11
From: Adrian Schmutzler
To: Enrico Mioso , openwrt-devel@lists.openwrt.org
Cc: Filip Moc , openwrt-
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Enrico Mioso
> Sent: Freitag, 8. November 2019 16:14
> To: openwrt-devel@lists.openwrt.org
> Cc: Filip Moc ; openwrt-devel@lists.openwrt.org; Koen
> Vandeputte
> Subject: Re: [OpenWrt
Hello all! I am back again on this.
First of all - Thank you a lot Adrian for your patience and multiple reviews. I
would be happy to have your signoff in the final version of the patch, of
course when all of this is fixed.
Still - the main issue, that's stopping me from doing / fixing all the r
Hi,
> > > + firmware: partition@4 {
> > > + compatible = "denx,uimage";
> > > + reg = <0x4 0x37>;
> >
> > 3520k? Does this even build with standard buildbot settings?
>
> I did not know I need to check with standard build
Den 11/8/19 kl. 11:01 AM, skrev Piotr Dymacz:
> Hi Micke,
>
> On 08.11.2019 08:36, Micke Prag wrote:
>> In commit 00ea16557d [1] the way usb is initiated was changed. Instead
>> of initiate both ehci-platform and ci_hdrc the bootstrap status register
>> is checked and used to determine which platfo
This provides a uci system config setting that will be set only
during initial setup. This can be used by uci-defaults script to
determine whether they are run during initial setup or after a
sysupgrade.
Since the setting is removed again after uci-defaults have been
processed, it won't be recogni
By exploiting the new initial_setup option, default SSID setup
can be improved so it does not have to rely on the previous SSID
value anymore.
Signed-off-by: Adrian Schmutzler
---
This patch is a proof-of-concept based on the SSID EUI patch as
just submitted. It's mainly intended to show the us
uci-defaults are sourced and non-executable, so they do not require
a shebang.
While at it, apply consistent naming scheme.
Signed-off-by: Adrian Schmutzler
---
package/base-files/files/etc/uci-defaults/10_migrate-shadow | 2 --
.../base-files/files/etc/uci-defaults/12_network-generate-ula
If the label MAC address is provided for a device, the default SSID
will be set to contain the EUI of this address, e.g. OpenWrt-ddeeff.
With multiple routers, this will help the user to identify his device
based on the MAC address printed on the device.
If no label MAC address is specified, this
From: Rosy Song
If a label MAC address is provided for device, system
will rename the hostname with OpenWrt_.
This helps to distinguish between different devices.
Since it's no good idea to nest json_* functions, this code does
not use get_mac_label directly, but only get_mac_label_dt as
externa
This patchset will introduce the label MAC address into the _default_
hostname and SSID of OpenWrt devices. Devices installed after these
commits (or upgraded with sysupgrade -n) will have their hostname and
SSID set to
OpenWrt-ddeeff
where "ddeeff" is the EUI of the label MAC address aa:bb:cc:dd:e
Hi Micke,
On 08.11.2019 08:36, Micke Prag wrote:
In commit 00ea16557d [1] the way usb is initiated was changed. Instead
of initiate both ehci-platform and ci_hdrc the bootstrap status register
is checked and used to determine which platform to initiate.
There were other changes later, see for
On Fri, 8 Nov 2019, Lars Melin wrote:
Don't complicate simple things, all D-Link routers have a recovery web page
and you access it with your browser, not with curl.
/Lars
Some things maybe simple to you, yet complicated to me, and vice-versa. To me,using
"curl" to perform recovery ma
On 11/8/2019 14:50, Paul Fertser wrote:
On Thu, Nov 07, 2019 at 08:19:27AM +0300, Paul Fertser wrote:
I see there's some http server mentioned in the wiki article, haven't
tried it yet (and I can't understand what "simple" web browser it
talks about, probably there should be a curl command inste
30 matches
Mail list logo
