<mrkiko>
nbd: when wi-fi goes down on a Fritz!box 7530, I see Fri Sep 22 00:00:00 2023 daemon.notice netifd: radio0 (8806): WARNING: Variable 'data' does not exist or is not an array/object
<mrkiko>
nbd: snapshot of more or less 3 days ago
philipp64 has quit [Ping timeout: 480 seconds]
philipp64 has joined #openwrt-devel
Daanct12 has joined #openwrt-devel
tSYS has quit [Quit: *squeak*]
tSYS has joined #openwrt-devel
dether has quit [Read error: Connection reset by peer]
xback has quit [Remote host closed the connection]
<rmilecki>
nbd: could you give Acked-by to the [PATCH] ARM: dts: BCM5301X: Relicense Felix's code to the GPL 2.0+ / MIT
<nbd>
will do
<rmilecki>
thank you!
tidalf has quit [Remote host closed the connection]
tidalf has joined #openwrt-devel
goliath has joined #openwrt-devel
Daanct12 has quit [Quit: WeeChat 4.0.4]
hitech95 has joined #openwrt-devel
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
cyrozap has joined #openwrt-devel
<hitech95>
What is the difference between using label-mac-device or ethenet0? I cant find where those aliases are used.
<robimarko>
They are completely different things
<robimarko>
label-mac-device alias is used to populate the info about what MAC is printed on the device label/sticker
<robimarko>
ethernetN is the generic alias that U-Boot uses to patch the MAC
<hitech95>
robimarko, Where can I find an usage of such aliases? Cant figure out what they do :D
<robimarko>
Like I said, U-boot will use the ethernet0 and so on to populate the MAC in the node before passing the DTB to the kernel
<robimarko>
So you magically have the correct MAC
<robimarko>
label-mac-device is an OpenWrt thing
<hitech95>
Got It, how can I know if I need to populate such entries?
<hitech95>
By searchinf for "label-mac-device" I only find DTS results so I'm not sure how it is used.
<karlp>
does your device have a printed label with a mac address onit?
<hitech95>
yep
<nbd>
rmilecki: ping
<karlp>
then you want to add a label-mac-device property to your DT, poitning to the mac that matches the label...
<karlp>
or, just ignore it.
<hitech95>
karlp, oh ok so if there is a phisical label there must be the alias.
<karlp>
you can script access to the label-mac to write "portable" scripts that use the label mac, rather than having to juggle in shell scripts whether the label mac is frrom eth0 or wlan42 or whatever...
<hitech95>
karlp, ok what if my driver is using the nvmem-cells to laod the mac address directly in the driver?
tidalf has quit [Remote host closed the connection]
tidalf has joined #openwrt-devel
<rmilecki>
nbd: pong
<rmilecki>
nbd: i'm around for 15-30 minutes
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
cyrozap has joined #openwrt-devel
cyrozap has quit []
cyrozap has joined #openwrt-devel
<nbd>
rmilecki: i've started to write a new packet steering script, i was wondering if you could give it a try for me: https://nbd.name/p/3a85f072
<rmilecki>
nbd: i will during weekend
<nbd>
thx
<nbd>
before you test it, please boot with the previous packet steering script disabled, so that it doesn't change any settings not touched by my script
<hitech95>
nbd, I have a dumb question about the mtk ppe and hw offloading. Can I pm you for a couple of questions?
<nbd>
hitech95: sure
<karlp>
hitech95: independent. nvmem cells is how you specify the mac for an eth, for instance.
<karlp>
label-mac is how you specifyc which mac is on the label.
<karlp>
eg like this: https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ath79/dts/qca9563_ubnt_unifiac-pro.dtsi;h=bb00643377e35314405f02d77644a4f7b0cde20f;hb=HEAD
<hitech95>
karlp, yep, got that. I'm testing my patch right now having some issue with uboot :D
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
cyrozap has joined #openwrt-devel
xback has joined #openwrt-devel
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
filimonic has joined #openwrt-devel
cyrozap has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
<mrkiko>
nbd: [ 0.000000] Linux version 6.1.52 (mrkiko@mStation) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 12.3.0 r23958-12584395dc) 12.3.0, GNU ld (GNU Binutils) 2.40.0) #0 SMP Sun Sep 17 22:08:19 2023
<mrkiko>
nbd: 12584395dc
<nbd>
mrkiko: the fix for that issue was added after that commit
<mrkiko>
nbd: sorry for the noise, then; even for the "data" variable?
<mrkiko>
k
<mrkiko>
oops :D
<nbd>
the fix is f52e008d045302976d2ff40f35e91b84a5678d12
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
cyrozap has joined #openwrt-devel
minimal has joined #openwrt-devel
bluew has joined #openwrt-devel
hanetzer1 has joined #openwrt-devel
hanetzer has quit [Ping timeout: 480 seconds]
<hitech95>
nbd, is better to use the led pinmux for the wifi on mt76 or is better to use a netdev trigger on the wireless phy?
robimarko has quit [Remote host closed the connection]
philipp64 has quit [Quit: philipp64]
<hitech95>
does anyone know if the mt7986a USB is supposed to work or if its broken?
philipp64 has joined #openwrt-devel
<hitech95>
ok there was a package missing in the device config...
<dwfreed>
usb packages are often not included by default
<hitech95>
yea but that was the core usb module
<dwfreed>
that would still be a usb package :P
<dwfreed>
the default package lists are generally just limited to what is necessary for the core features of a router
<dwfreed>
(ie, wireless and ethernet)
<dwfreed>
the device page usually mentions what packages may be needed for non-core features
<hitech95>
dwfreed, int he same target all other boards have the kmod-usb3 included this one is not
<dwfreed>
does this board have less storage than the others?
<hitech95>
dont think so
<hitech95>
we are talking about filologic stuff so nand with a ton of space
philipp64 is now known as Guest967
philipp64 has joined #openwrt-devel
Guest967 has quit [Ping timeout: 480 seconds]
philipp64 is now known as Guest968
philipp64 has joined #openwrt-devel
<mrkiko>
nbd: but the error shows up even running 587f94eb1a
<hitech95>
is there a way to include custom scripts in an image for a specific target? The scripts should be hotplug.d stuff
<philipp64>
is there a cheat sheet for setting up multi-homing with two ISPs on OpenWRT?
<dwfreed>
philipp64: see mwan3
<philipp64>
I looked at that. isn't that when you have TWO routers and you want redundancy? I have just the one router with two WAN interfaces.
<dwfreed>
no, it's for exactly what you want
<philipp64>
okay... I'm reading about where 'lo' gets reconfigured. isn't that going to break IPC for processes that expect to talk to 127.0.0.1?
<philipp64>
and... first fly in the ointment:
<philipp64>
> Ensure that every WAN interface has a gateway IP and metric defined! This is very important as otherwise mwan3 will likely not work!
<philipp64>
even though T-Mobile is (supposedly) selling me a static IP, they want me to run DHCP...
<Habbie>
won't DHCP "define" that gateway IP?
<philipp64>
right, but then some stuff needs to be plugged into /etc/config/mwan3 ...
<philipp64>
Also, need to configure my email (SMTP anyway) to always flow out through my primary WAN interface... at least until T-Mobile gives me an rDNS mapping... and I update GoDaddy (sigh... too many providers).
<philipp64>
back in a bit... need to meet the kids at the bus stop...