Hello again,
On OpenWrt 21.02-rc2 (and probably earlier), the WAN port is treated
as a LAN port and LAN port 4 is treated as the WAN port on the TP-Link
AD7200. (Actually, all the ports show up in LuCI in reverse order from
their labels on the case.) How can I fix that?
-Alex
___
On 31.05.2021 23:58, Hauke Mehrtens wrote:
New network configuration syntax
There have been several changes to the network configuration syntax in
/etc/config/network:
To provide some context: that change resulted in cleaner configs and
manageable UI interface (LuCI) support.
Big thanks to J
On 28.05.2021 20:18, Evgeny K wrote:
3. Drop section name
It's not required by netifd or LuCI & it's not needed by this script
as $device contains a single device name now.
It could be convenient to have it, though. In the former scheme of
things, if one would like to know the interface
Hi,
since we are starting to add support for ath11k i was thinking... To
have things organized
and remove some confusion, I was thinking if it wouldn't be better to
split the ath
patch dir to 3 (or 4) sub directory and introduce patch for ath9k,
patch for ath10k
and patch for ath11k with a 4th opti
Hi,
The OpenWrt community is proud to announce the second release candidate
of the upcoming OpenWrt 21.02 stable version series. It incorporates
over 5800 commits since branching the previous OpenWrt 19.07 release and
has been under development for about one and a half year.
Changes between
MikroTik boards with 512 byte NAND pages require the old YAFFS1 OOB
layout for compatibility with the RouterBoot bootloader. The RB4xx NAND
driver supports such OOB layout, but checks a NAND page size too early
before the flash identification, what effectively preventing the old OOB
layout from bei
Sync iptables FLOWOFFLOAD target with upstream nft_flow_offload.c, which
fixes the issue.
Fixes: FS#3649
Signed-off-by: DENG Qingfang
---
Note: I am by no means an expert on Netfilter subsystem. I just kind of
copied and pasted upstream nft_flow_offload.c here, which seemed to work.
A fix for ker
One more question, now I'm trying to put a bridge on top of each of these vlan*
interfaces so that I can map those to a few physical interfaces. I also need
several vlans to map to one of the interfaces (tagged).. not sure how to do
that yet either. Any suggestions with this config? When I apply
Hi,
> This is the reason. Long time ago, I did select the option 'Remove ipkg/opkg
> status data files in final images' to reduce the image size. Since such an
> option can be selected, LuCI cannot assume, that the file netifd.control
> exists.
fixed.
~ Jo
signature.asc
Description: OpenPGP
Am 31.05.2021 um 16:36 schrieb e9hack:
LuCI commit 17af33e
luci-mod-network: migrate network config depending on netifd version
does introduce to read the file /usr/lib/opkg/info/netifd.control. I don't have
this file on my router. Can that be the reason for the error 'Resource not
found'?
Am 31.05.2021 um 15:52 schrieb e9hack:
Am 31.05.2021 um 07:18 schrieb Rafał Miłecki:
On 30.05.2021 18:02, e9hack wrote:
Am 30.05.2021 um 15:41 schrieb e9hack:
Am 30.05.2021 um 09:59 schrieb Rafał Miłecki:
On 29.05.2021 23:28, e9hack wrote:
I'm using a TP-Link Archer C7 v2 router. For every b
Am 31.05.2021 um 07:18 schrieb Rafał Miłecki:
On 30.05.2021 18:02, e9hack wrote:
Am 30.05.2021 um 15:41 schrieb e9hack:
Am 30.05.2021 um 09:59 schrieb Rafał Miłecki:
On 29.05.2021 23:28, e9hack wrote:
I'm using a TP-Link Archer C7 v2 router. For every build, I do update my
sandbox with the c
12 matches
Mail list logo
