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 ---
ДЕТСКИЕ ДИАФИЛЬМЫ
Каждый из нас
Thanks so much for the quick response.
Sounds promising. I will definitely take a look on those steps.
Best regards,
--
Xianjun Jiao
Senior researcher, imec-Gent university
210.007, IDLab, iGent, Technologiepark 126, 9052, Ghent, Belgium
Mobile: +32 484 57 22 32
On Dec 18, 2019, at 23:36, Hauke
On 12/18/19 11:09 PM, Xianjun Jiao (UGent-imec) wrote:
> Dear openwrt friends,
>
>
> A message may interest you. Our openwifi project is online:
>
> https://github.com/open-sdr/openwifi
>
>
> Full stack real time SDR (Software Defined Radio) Wi-Fi implementation
> on zynq FPGA with embedded
Dear openwrt friends,
A message may interest you. Our openwifi project is online:
https://github.com/open-sdr/openwifi
Full stack real time SDR (Software Defined Radio) Wi-Fi implementation on zynq
FPGA with embedded ARM Linux. Compatible with Linux mac80211 SoftMAC framework.
hostapd,
Do not just silently fail when kernel modules are nowhere to be
found. This is essential for diagnosing mismatched kernel version
failures.
Signed-off-by: Paul Fertser
---
kmodloader.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kmodloader.c b/kmodloader.c
index
On Tuesday 17 December 2019 08:28:35 Rafał Miłecki wrote:
> From: Pali Rohár
>
> commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
>
> When FAT directory entry has leading byte 0x05 it is interpreted as byte
> 0xE5. This is how FAT stores file name which starts with byte 0xE5 as
>
When netifd manages the prefix route directly, it will remove it
the moment prefix gets deprecated. This will make it impossible
for the target to send ICMPv6 errors back to LAN devices still
using the deprecated prefix, thus breaking the L-14 requirement
of RFC 7084.
Signed-off-by: Alin Nastac
