orce the user to set a password.
However, it will never get merged if that setup applies to everything
as it would break many provisioning. It might be overkill but maybe it
looks like a new image flavor...
My 2 cents,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
Em ter., 6 de j
a73e1bf307e..ac71b3305ee6 100644
> --- a/tools/firmware-utils/src/tplink-safeloader.c
> +++ b/tools/firmware-utils/src/tplink-safeloader.c
> @@ -1262,7 +1262,7 @@ static struct device_info boards[] = {
> "{product_name:Archer
> C7,product_ver:5.0.0,special_id:4B520000}\n&qu
, I get no output from:
https://buildbot.openwrt.org/openwrt-21.02/packages/#/builders/12/builds/58/steps/24/logs/stdio
Is there any place to get full buildbot output for packages? Or an
easy way to locally simulate a buildbot?
Regards,
---
Luiz Angelo Daros de Luca
luizl
ot;18.06 era".
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ifd really wanted to add a dependency to the first
route, not the second one.
Maybe netifd should ignore those routes with types for host
dependencies, but I don't know the consequences of that change.
Regards,
---
Luiz Angelo Daros de Luca
luizl...
> I think that netifd really wanted to add a dependency to the first
> route, not the second one.
> Maybe netifd should ignore those routes with types for host
> dependencies, but I don't know the consequences of that change.
Or maybe it is ok to monitor those kinds of routes if their type is
> > @@ -301,9 +301,26 @@ interface_ip_add_target_route(union if_addr *addr,
> > bool v6, struct interface *if
> > route->mask = v6 ? 128 : 32;
> > memcpy(>addr, addr, addrsize);
> > memcpy(>nexthop, _next->nexthop, sizeof(route->nexthop));
> > - route->mtu = r_next->mtu;
> >
ffload eth0 tx off" but it would be nice to have it back.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The package update is not a perfect solution but it is better to have
it as is than to remove it.
Updated packages are also used by imagebuilder and attended
sysupgrade. I normally generate a new image to apply updates because
some devices cannot afford the extra installation. If we need updated
> > 2) I was pretty fuzzy about what people should do if their target did
> > migrate to DSA. Do we have a guide to help those people through the
> > transition?
>
> We do not support a migration and people have to start with a new fresh
> installation. Doing a backup and restoring some settings
> I believe what he meant to say was to make another 19.07.x point
> release with an updated sysupgrade mechanism which would improve the
> situation when upgrading to 21.02.x and, for example, allow
> flashing with non-matching DEVICE_COMPAT_VERSION already when
> specifying the '-n' flag to not
Registers in MT7620A_GDMA_OFFSET range were incorrect, except for the
first one GDM_FWD_CFG (which is actually the only one in use).
The next and last register is GDM_SHPR_CFG. All others are not mentioned
in docs.
Signed-off-by: Luiz Angelo Daros de Luca
---
.../ramips/files/drivers/net
mt7620 can forward jumbo frames. The fe_change_mtu() was already
compatible except for the GDM_FWD_CFG address.
An MTU greater than 1500 is required to use DSA tags with a stacked
switch chip.
Signed-off-by: Luiz Angelo Daros de Luca
---
.../files/drivers/net/ethernet/ralink/mtk_eth_soc.c | 13
fe_change_mtu didn't update the registers if the interface was down.
DSA increases the CPU port MTU to accommodate the CPU tag. As this
happens while the CPU port was still down, the chip regs didn't get
updated and larger frames were dropped.
Signed-off-by: Luiz Angelo Daros de Luca
> I've started to look at the first vulnerability, but it is not as
> straightforward as I was hoping. Perhaps Luiz Angelo Daros de Luca,
> reporter and author of the fixes, can help me out with this.
Sure. And I do have interest in getting it fixed. It is both a
security fix (whe
Hi Andrey,
> It simple a) don't apply to master tree; b) not working - MAX_RX_LENGTH
> constant not
> touched, GSW_REG_GMACCR not tweaked for accepting jumbo frames.
a) Sorry, I missed your answer and thanks for the review. Yes, it was
not applying to master. It was based on another patch
to operate with a 2048-bytes frame (included single VLAN tag).
Are you ignoring CONFIG_SOC_MT7621 support for this driver? (it is
indeed upstream for recent kernels).
The patch worked as expected! Thanks a lot! Do you plan to submit it?
Tested-by: Luiz Angelo Daros de Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> On Tue, 2021-10-05 at 22:40 +0300, Paul Fertser wrote:
> > I only have D-Link DGS-1210-10P R1 for testing but other devices should be
> > very
> > similar judging by the photos. Would be nice to share support for all the
> > features available rather than get just R1 fully working.
> >
> > Paul
Em dom., 17 de jul. de 2022 06:55, Paul Fertser escreveu:
>
> On Sat, Jul 16, 2022 at 11:32:52PM -0300, Luiz Angelo Daros de Luca wrote:
> > It uses SOC := rtl8380 while all existing dgs-1210 F1 variants use
> > rtl8382 (except for the pending -52 variant). The commit didn
> The default uhttpd configuration has this:
>
> # HTTP listen addresses, multiple allowed
> list listen_http0.0.0.0:80
> list listen_http[::]:80
>
> Now, I know there's lots of practical reasons for this to be the case,
> and I know also that the firewall setup in
> > The previous fixup was incomplete, and the offsets for the
> > queue and crc_error cpu_tag bitfields were still wrong on
> > RTL839x.
> >
> > Fixes: 545c6113c93b ("realtek: fix RTL838x receive tag decoding")
> > Suggested-by: Jan Hoffmann
> > Signed-off-by: Bjørn Mork
> > ---
> > Jan pointed
> - Bridge device "br-vlan10" containing "lan1.10 lan2.10 lan3.10"
> - VLAN filtering disabled
Bridging virtual 802.1q interfaces might fail in some scenarios, like
when you use vlan1 or mix tagged with untagged traffic
(https://github.com/openwrt/openwrt/issues/9066)
I do recommend
> On Sun, Jul 31, 2022 at 03:36:32PM +0200, Sander Vanheule wrote:
> > On Sat, 2022-07-23 at 22:53 +0200, Jan Hoffmann wrote:
> > > Add the 7zr command line tool, which is a version of the 7z application
> > > that only supports 7z archives.
> > >
> > > 7z is one of the two compression formats
>
>
> > D-Link DGS-1210-48 HW Ver. G1 - will be fine? I need some confirmation.
> > Anyone could confirm?
>
D-Link DGS-1210-52 F does work in snapshot. You'll need to wait for
the next 23.x for a stable release.
I think there is only one switch with >=48 ports supported in 22.03:
zyxel gs1900.
> Thanks all!
> Finally buy: D-LINK DGS-1210-48 G1.
>
> U-Boot 2011.12.(2.1.5.67086)-Candidate1 (Apr 13 2017 - 13:58:11)
>
> Board: RTL839x CPU:700MHz LXB:200MHz MEM:400MHz
> DRAM: 128 MB
> SPI-F: 1x32 MB
>
> Next:
> - connected serial cable
> - stop in uboot
> - boot from
>
I know that autorelease has introduced some problems but it would be
good to keep a way to automatically bump releases. Every second we
could save from devs/maintainers is more time to do really useful
things.
Can't we have a central way to publish the "official list of package
releases''? It
> When reading https://openwrt.org/docs/guide-user/virtualization/start it
> is clear this hasn't seen much love. Several portions seemed to
> exclusively target developers and not really be meant for serious use.
> As such I was unsurprised to discover:
>
> Would it be too complex to implement a log limit for fw4?
Not really. But I might not have followed the best practices as this
is my first run on ucode/nftables:
https://github.com/luizluca/firewall4/tree/log_limit
It needs some more tests on cases that I'm not using in production and
a test
,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> Thanks, Alberto. I'm wondering how much work making it cross-build packages
> is going to be...
>
> Digging into it now...
>
You should take a look at ksmbd package. It does compile an out-of-tree module.
Maintaining a package like that might be challenging for a stable
version. The kernel
Em sáb., 6 de mai. de 2023 06:12, Arınç ÜNAL escreveu:
>
> Hi.
Hi Arinç,
> I see a lot of development on the network drivers like DSA, PHY, etc.
> Are there any plans to put all these drivers on the realtek target on
> mainline Linux? To fully support these SoCs on mainline Linux?
>
> Arınç
>
> Am 12.02.2024 um 17:59 schrieb Christian Marangi (Ansuel):
> > Would be ideal to know what target are we talking about.
>
> The device is a TP Link C7 converted to using DSA.
It is a good opportunity to use it as a loadable module. It is tricky
but it works if configured correctly.
Regards,
nd this solution to make it more generic:
> 1. Always mount overlay while creating backup
> 2. Overlay whole / to don't limit it to /etc/backup/
>
> This allows including any additional files in backups and adding more
> sysupgrade features.
It is a nice feature. Thanks.
>
> C
> On 21.02.2024 20:52, e9hack wrote:
> > root@WLAN-DSL9:~# sysupgrade -b /var/config-backup.tar.gz
> > Wed Feb 21 20:48:30 CET 2024 upgrade: Saving config files...
> > tar: var/dhcp.leases: No such file or directory
> > tar: var/lib/logrotate.status: No such file or directory
> > tar:
> >I would choose 6.1: to get more time for some things to stabilize out and
> >because I am under the impression the kernel size is growing too fast and so
> >we are accelerating hw obsolescence.
The firmware overall size is not the only problem. Some bootloaders
might have trouble loading
Hello Rafał,
Sorry for the late review.
I know this will be used for a limited context but it can be
constructed in such a way it could be used for more cases without
increasing its complexity.
> From: Jo-Philipp Wich
>
> This allows building uncompressed tar archives from shell scripts (and
>
>
> Replace mount + overlay with manually built tar archive that gets
> prepended to the actual config files backup. This allows more
> flexibility with including extra backup files. They can be included at
> any paths and don't require writing to flash or mounting an overlay
> which has its own
Hello,
There is a small fix for uhttpd pending in github.
https://github.com/openwrt/uhttpd/pull/2
If github should not be used for that, it would be nice to have it
explicitly mentioned in the github project or a Readme.md file.
Regards,
---
Luiz Angelo Daros de Luca
luizl
101 - 138 of 138 matches
Mail list logo
