On Sun, Jan 28, 2018 at 8:02 PM, Ansuel Smith wrote:
> Can this bug be fixed?
In order to get the bug fixed please create an issue in Flyspray
(https://bugs.openwrt.org/) and provide all the necessary info which
helps to get the bug fixed.
Hans
>
> 2018-01-26 11:14 GMT+01:00 Ansuel Smith :
>> The
To make it more accessible for nodejs users to configure and run a build
on mips target lacking hardware fpu
Signed-off-by: Yousong Zhou
---
v2 <- v1
Use TARGET_lantiq_ase instead of TARGET_lantiq
config/Config-kernel.in| 5 +
target/linux/lantiq/ase/config-default
To make it more accessible for nodejs users to configure and run a build
on mips target lacking hardware fpu
Signed-off-by: Yousong Zhou
---
config/Config-kernel.in| 5 +
target/linux/lantiq/ase/config-default | 1 -
target/linux/pistachio/config-4.9 | 1 -
3 files chang
nf.org/2.1/slides/apr8/ayuso-netdev-netfilter-upd
>>>>> ates-canada-2017.pdf
>>>>>
>>>>> The flowtable representation, in software, is providing a faster
>>>>> forwarding path between two nics. So it's basically an alternative to
&g
>> > With the TP-Link firmware:
>> > - wired 930+ Mbit/s both ways
>> > - wireless 5G 560+ Mbit/s down 440+ Mbit/s up
>> > - wireless 2.4G 100+ Mbit/s both ways
>>
>> > With OpenWRT/LEDE trunk 20180128 4.
org/2.1/slides/apr8/ayuso-netdev-netfilter-upd
>>>>> ates-canada-2017.pdf
>>>>>
>>>>> The flowtable representation, in software, is providing a faster
>>>>> forwarding path between two nics. So it's basically an alternative t
gt;>> if there is a hit in the software flowtable, ttl gets decremented,
>>>> NATs are done and the packet is placed in the destination NIC via
>>>> neigh_xmit() - through the neighbour layer.
>>>
>>> Hi Pablo,
>>>
>>> I tested toda
> - wireless 5G 560+ Mbit/s down 440+ Mbit/s up
> > - wireless 2.4G 100+ Mbit/s both ways
>
> > With OpenWRT/LEDE trunk 20180128 4.4 kernel:
> > - wired 350-400 Mbit/s both ways
> > - wired with firewall deactivated 550 Mbit/s
> > (just "
nless specified,
> using iperf3 LAN=>WAN and -R for WAN=>LAN (both TCP).
> With the TP-Link firmware:
> - wired 930+ Mbit/s both ways
> - wireless 5G 560+ Mbit/s down 440+ Mbit/s up
> - wireless 2.4G 100+ Mbit/s both ways
> With OpenWRT/LEDE trunk 201
if there is a hit in the software flowtable, ttl gets decremented,
>> > NATs are done and the packet is placed in the destination NIC via
>> > neigh_xmit() - through the neighbour layer.
>>
>> Hi Pablo,
>>
>> I tested today a few things on a brand new TP-Li
ination NIC via
> > neigh_xmit() - through the neighbour layer.
>
> Hi Pablo,
>
> I tested today a few things on a brand new TP-Link Archer C7 v4.0,
> LAN client Dell Latitude 7480 (eth I219-LM, wifi 8265 / 8275)
> WAN server NUC5i3RYB (eth I218-V), NAT between them, <1
I219-LM, wifi 8265 / 8275)
WAN server NUC5i3RYB (eth I218-V), NAT between them, <1 ms latency
(everything on the same table), IPv4 unless specified,
using iperf3 LAN=>WAN and -R for WAN=>LAN (both TCP).
With the TP-Link firmware:
- wired 930+ Mbit/s both ways
- wireless 5G 560+ Mbit/s dow
Can this bug be fixed?
2018-01-26 11:14 GMT+01:00 Ansuel Smith :
> Then the bug is real.
>
> Il 26 Gen 2018 08:01, "Nishant Sharma" ha scritto:
>>
>> Hi,
>>
>> On Friday 26 January 2018 04:18 AM, Ansuel Smith wrote:
>>>
>>> https://forum.lede-project.org/t/no-space-left-in-tmp/11000/14
>>> Here y
Tested-by: Stijn Segers
Compile and run-tested on ar71xx / ramips/mt7621 / x86/64.
Op za, 27 jan 2018 om 5:05 , schreef Kevin Darbyshire-Bryant
:
Refresh patches.
Refresh x86/config for RETPOLINE.
More Meltdown & Spectre mitigation.
Signed-off-by: Kevin Darbyshire-Bryant
---
v2 - clarify t
14 matches
Mail list logo
