<stintel>
like how to properly integrate all of this in OpenWrt
<stintel>
I'll publish my local /60 instead, see if that sticks
<neggles>
iirc thread doesn't have to only use ULA though?
<neggles>
thread border routers can request a DHCPv6 PD and hand that out to devices
<stintel>
yep
<stintel>
but right now it's ULA
<stintel>
I might need to ask for a /56 instead of a /60 :P
<neggles>
shouldn't a /64 be plenty for a single thread network? :P
<stintel>
I'm running out of /64s in this /60
<neggles>
ah wait, misread, yeah you should definitely ask for a /56
<neggles>
handing out /56s to even home users seems to be what most ISPs are converging on
<stintel>
yeah this is just 2 tunnels with BGP to local hacker space
<neggles>
ah
<stintel>
they asked if /60 was enough, back then it was for sure, so I said yes
<neggles>
(/56s is partly because the way cisco/arista/juniper lay out their TCAM, you can fit more /56s than /60s in the same space)
<dwfreed>
oh, I do have a /56 from cox
<stintel>
all bird2 here :)
<dwfreed>
I think I had to set something special to make that work, though
<stintel>
ugh something is leaking ULAs though
<neggles>
a lot of arista's current gen stuff is bird2 under the hood
<neggles>
but the FIB is still in... sortahardware
<dwfreed>
ah, yeah, specifically specifying reqprefix 56, otherwise it would just get a /64
<neggles>
yeah most routers / DHCPv6 clients seem to default to just asking for a /64
<neggles>
my ISP gives me an address for on-link and a /56, or a /48 if you ask for it
<dwfreed>
well, the way it works on openwrt, odhcp6c doesn't specify a prefix length (just the option for getting a prefix), and then my ISP just says "here's a delegated /64"
<neggles>
yeah, same here
<neggles>
have to send prefix length hint
<dwfreed>
but if you set option reqprefix 56, then it'll hand out a /56 just fine
<dwfreed>
(and that's the largest I can get)
<stintel>
uff where are these fucking ULAs on my workstation coming from
<dwfreed>
stintel: leftovers that haven't expired yet?
<stintel>
rtt min/avg/max/mdev = 126.242/308.896/526.042/118.421 ms
<stintel>
I know it's not the intended use, but still, with matter being so huge that some mfgs are unable to add support to some existing devices because not enough storage ...
<stintel>
firmware updates need to happen
<stintel>
and if that can cause >500ms latencies ... hmmm
<stintel>
maybe I should add a another thread client and ping that while scping to the other
<stintel>
anyway, I think that's enough for today, possibly for this week, and maybe even for this year
<dwfreed>
keep in mind the maximum packet size on 802.15.4 is 127 octets
<dwfreed>
at the same time, a peak latency of only 500ms really isn't *that* bad
<dwfreed>
especially if you're transferring a file across at the same time
<stintel>
now if only I could figure out how to trick the Eve app into thinking I have a crapple thread network
<stintel>
so that I can upgrade my eve energy and eve motion sensor, get the thread key, and try joining them in my thread network
<stintel>
maybe I can run homebridge
<stintel>
it doesn't have thread support but I'm seeing mdns requests for homekit stuff
<stintel>
hmmmz
<stintel>
also seeing _meshcop._udp.local. queries but no responses
<stintel>
maybe I don't know how mdns works
<stintel>
Installing Homebridge and user plugins, please wait...
<stintel>
on container startup *facepalm*
dansan has quit [Ping timeout: 480 seconds]
<neggles>
stintel: homekit has Matter support now and iirc Matter runs on Thread as well as wifi
<neggles>
homepods, appletvs can be / are matter routers/gateways
<stintel>
I know, but I don't have homepod nor apple tv
<stintel>
and I apparently need to one of those before the Eve app will allow me to upgrade the firmware of my eve energy or eve motion sensor to the firmware that supports matter
<stintel>
they're working on an android app also, so this firmware should drop the homekit requirement
<stintel>
just a bit annoying that I need some homekit/thread device to do the firmware upgrade
<stintel>
good thing I didn't go bonkers and ordered 20 eve energy with black friday deal
<neggles>
stintel: heh, "you can upgrade to the Matter firmware and use matter with Samsung SmartThings, Google Home, and HomeKit!"
<neggles>
further down the page: "ur gonna need an appletv or a homepod mini and an iphone to update to this firmware"
<stintel>
I have an ipad with the required version of ipados and have the testflight version of the eve app
<stintel>
but no homepod or appletv
<neggles>
> All Eve products that are currently available in retail work with Apple Home only. So in order to update them to Matter, you have to use the Eve app for HomeKit.
<neggles>
hmm
<neggles>
someone will probably work out how to DIY a homekit-compatible thread border router sooner rather than later
<stintel>
I guess I can get a homepod or appletv :)
<stintel>
unlinked the motion sensor a few times already and rejoined but keeps connecting via bluetooth
<stintel>
oh well
<neggles>
homepod mini is quite cool and good as a speaker, but if you don't trust apple with a microphone in your house the appleTV
danitool has quit [Remote host closed the connection]
<stintel>
iPad is not supported as a home hub on the new, more reliable, and more efficient Home architecture, which is available as a separate upgrade in the Home app.
<stintel>
grmbl
<stintel>
and I just did that upgrade probably
<stintel>
fml
<stintel>
ok support for that was dropped in ipados 16
<aiyion>
stintel: good morning. Trains have been taken, birthdays been celebrated, time to test the patch.
<stintel>
and needed 16.1 iirc to be able to run the eve preview app
<stintel>
aiyion: morning :)
goliath has quit [Quit: SIGSEGV]
<stintel>
I'm gonna head to bed though
<aiyion>
On the train the build wouldn't compile but hang on the musl stage -.-'
<aiyion>
good choice.
<aiyion>
will do once I've upgrade to your staging tree.
<stintel>
had enough of the apple wiseassery for today :)
minimal has joined #openwrt-devel
<aiyion>
stintel: compilation sucessful, sysupgrade as well. 3/3 reboots without problems. Will leave this rebooting till morning and share the stats, but I'd say this is ready to merge.
<nkko>
I'm having issues with BCM963138 routers, they seem to be close to bcm53xx, but not? There is mainline support for them, but I just cannot get it to boot (vendor kernel works, I was also able to build a neer cfe release)
<nkko>
I've checked the ELF sections, etc., ran diff on the vendor source, I just cannot figure out what could be causing it
<nkko>
*newer
<nkko>
I don't think it'd be related to the device tree, though, surely (cmplzma is probably stripping the appended dtb, anyway)
<champtar>
ynezz: thanks for the links, I added a comment to the ticket, Turris Omnia is broken for me with latest master / 5.15 with a pretty basic config
<Borromini>
do the buildbots clean the build environment on every run? I suppose so?
<dhewg>
which is prolly sdk related again
<dhewg>
I never used the sdk, but it's just a headache if buildbot/ci fails when everything works locally, it's a reoccuring issue
<robimarko>
Well, there have been weird failures recently
srslypascal is now known as Guest138
srslypascal has joined #openwrt-devel
Guest138 has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest139
srslypascal has joined #openwrt-devel
tomn has quit [Quit: leaving]
tomn has joined #openwrt-devel
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
Guest139 has quit [Ping timeout: 480 seconds]
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
<tmn505>
WRT build error; AFAICS we don't build gzip in buildroot but it tries to run staging_dir/host/bin/gzip, is the 47df168 change bogus? < oliv3r[m]
<dhewg>
include/prereq-build.mk checks for gzip, and hence creating a shortcut in staging/host/bin
<dhewg>
and I guess that doesn't work with the sdk
<tmn505>
hmm, I don't have that symlink in my staging_dir.
<tmn505>
ok, that's recent addition and I didn't rebase my tree yet
<Znevna>
jkolp6
<Znevna>
whops, sorry
<tmn505>
so f595beb should be backported to to 22.03
<tmn505>
hauke: ^^
<dhewg>
oh haha, yeah that makes sense
<stintel>
aiyion: done
<stintel>
oops I added the wrong closes tag
<stintel>
rectified and dupe closed
<stintel>
cool. already 2 issue report since the template is in place
<f00b4r0>
yay :)
<stintel>
and 2 feature requests in the forum
<f00b4r0>
looks like it's working then :)
<stintel>
yep
felix has joined #openwrt-devel
<stintel>
and it looks like my OpenWrt Thread "client" is still accessible
<stintel>
yay
<Borromini>
stintel: this? 'I am reporting an issue for OpenWrt, not an unsupported fork.'
<stintel>
Borromini: what do you mean?
<stintel>
that particular element is only a *very* small part of the issue template
<stintel>
Borromini: looks like a report with enough info ?
<Habbie>
1 task done
<Habbie>
:)
<stintel>
I mostly hope the page *before* reporting an actual issue makes people think twice about reporting a bug, and reach out to the community instead
<stintel>
yeah
<Habbie>
it's even worse in pdns, where some of the checkboxes are not required (that's a PR thing, though)
<stintel>
we discussed this in the PR, it's being worked on to make checkboxes not tasks unconditionally
<dangole>
dangole: ok, so that's different from mediatek SoCs, then it's up to the driver in which order they show up...
<dangole>
dangole: because it's just a single call to drivers probe() function from Linux kernel...
<stintel>
ah so the aliases won't solve this
gladiac has quit [Quit: k thx bye]
robimarko_ has joined #openwrt-devel
gromero has quit [Remote host closed the connection]
gromero has joined #openwrt-devel
schwicht has joined #openwrt-devel
felix has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
<opty>
what do you think about iwinfo build on other systems using https://termbin.com/1j8m and e.g. 'make CFLAGS="-DNO_UCI -DNO_UBUS -DNO_UBOX -DNO_LUA -DUSE_STDBOOL_H -I/usr/include/libnl3 -D_GNU_SOURCE" FPIC=-fPIC BACKENDS=nl80211 SOVERSION=20210430'? (no essid, encryption and expected throughput yet, though)
<robimarko_>
stintel: Honestly, so far I think I had one break with Fedora in like 5+ years
<stintel>
sigh, thread. now I need a new CLI tool for commissioning a new device
<robimarko_>
And I am the guy that usually even updates to beta versions
<stintel>
I guess it's the hardware then (thinkpad x1 carbon g9 iirc)
* Borromini
is happy enough with Debian testing
<robimarko_>
Well, I am using it on T490, Huawei Matebok 16 and on my workstation which is 5950X
<f00b4r0>
linux desktop. /me rolls eyes xD
* f00b4r0
hides
<stintel>
I don't remember the last time my workstation crashed
<robimarko_>
Neither
<robimarko_>
And I did some crazy stuff
<stintel>
my work macbook ... acting up all the time
<stintel>
yeah I do crazy shit on my workstation too :P
<f00b4r0>
stintel: it can tell you hate it :}
<stintel>
and this is Gentoo
<Znevna>
my storage server is missing a capacitor from the CPU, still doesn't crash.
<stintel>
thread community on github does seem very active
<f00b4r0>
so thread is a replacement to matter, itself an alternative to homekit, did I get this right?
<stintel>
no
* f00b4r0
is a bit confused by the iot space
<f00b4r0>
more than a bit then :)
<Borromini>
you're in the same boat as me then :P
<stintel>
matter works over (on top of) Thread, WiFi, Ethernet
<stintel>
well, or just over IP
<stintel>
so all your IoT devices will have an IP, and you use the matter standard to tell e.g. your lamp: switch to color X, over IP
<stintel>
I kind of like that idea, you can use ULA and you don't have to worry for the Internet to be able to access your IoT devices, but it does allow simple monitoring with ICMP "hey is my lamp still on the network"
<stintel>
and OpenThread should fix a lot of the shortcomings of Zigbee and Zwave
<stintel>
and iiuc we will finally be able to have a redundant home automation controller
<stintel>
something that simply isn't possible with zwave or zigbee
<stintel>
which makes it ... super mega annoying
<Borromini>
i haven't got any IoT stuff in here but my brother pointedly observed our screens (when we install them) will need some form of control, and that's often domotics
<Borromini>
so i guess we'll need to have *some* form of that stuff anywya
<Borromini>
* anyway
<stintel>
I've 20 zigbee lamps, 2 zwave lamps, 6 zwaves smart wall plugs, 13 esp32s, an esp-based smart wall plug, and a few raspberry pis doing IoT stuff
<stintel>
and some more zigbee lamps to be added
<stintel>
but if I can get redundant thread network with openwrt border routers and then use matter from whatever device with the right tools ...
<stintel>
I will replace *everything*
<Borromini>
:)
<f00b4r0>
e-waste :P
<stintel>
nah, donate to local hacker lab
<stintel>
or my parents
<stintel>
or a friend
<Borromini>
i guess he'll find someone to relieve him from that stuff
<f00b4r0>
i kinda like the idea that I can still turn all my lamps on after an EMP :)
<stintel>
f00b4r0: just flip the switch
<f00b4r0>
simply by getting my ass up to the switch
<stintel>
but if EMP happens ... I guess we've other things to worry about :P
<f00b4r0>
fair enough :)
<stintel>
but I like that my back row of spots switches off and my front row of spots switches to yellow / low brightness whenever I start watching some movie or series
<f00b4r0>
I simply turn off the lights
<f00b4r0>
i guess I have simpler needs ;}
<Borromini>
we have a dimmer B-)
<stintel>
or that all my lamps switch off 15 minutes after me or my partner leaves the apartment (not if one of us is still here of course)
<stintel>
"hmmm, I think I forgot to unplug the iron"
<stintel>
vpn, click, not a problem
<stintel>
etc
<f00b4r0>
to me all that iot / automation screems of more points of failures, maintenance and security nightmares. There's only so much time I'm willing to dedicate to controlling lamps :)
<Znevna>
official firmware was hanging at mt7621-pci 1e140000.pcie: Failed to get gpio for PCIe1
<f00b4r0>
hmm maybe I shouldn't have crossgraded this raspi to vanilla devuan. It keeps resetting every now and then now
* f00b4r0
disables frequency scaling for a try
<Borromini>
f00b4r0: from raspbian?
<f00b4r0>
Borromini: raspbian -> debian -> devuan (I have documented the process)
<Borromini>
:)
<f00b4r0>
i've had success stopping at debian, although I didn't update the kernel to the current 6.0
<f00b4r0>
I've also seen cpufreq causing similar havoc on raspi zeroes, so that'd be my primary suspect right now :)
<Borromini>
ok :)
<Borromini>
I'm on Armbian for my Odroid, happy enough with it.
danitool has joined #openwrt-devel
<f00b4r0>
yeah armbian is mostly ok
<f00b4r0>
i just got fed up with raspbian (lack of) security policy
<Borromini>
:-/
<f00b4r0>
and I wanted to give a shot at running a raspi without systemd :) (and I know I could do that with openwrt too, it might end there ;)
<Borromini>
:D
Tapper has joined #openwrt-devel
<minimal>
f00b4r0: Alpine has OpenRC rather than Systemd ;-)
<Borromini>
i've made my peace with systemd, grudgingly. I found networkd more robust than Debian's ifupdown framework :(
<Znevna>
looks like something trashed nvram x.x
<f00b4r0>
well I nearly bricked my device when systemd upgraded: I had the watchdog setup and apparently the configuration changed, there was no warning, and the device ended up rebooting 6-7s after coming online.
<f00b4r0>
I had to be "creative" to recover from that, considering it's 200km from here
<f00b4r0>
and I don't have console
<Borromini>
:-/
<f00b4r0>
i don't have enough foul words to express my contempt for this piece of software (and the people who brought it to life) ;-P
<slh>
Borromini: there's one very annoying catch with networkd (I use it - and prefer it over ifupdown, but...), upgrading systemd over ssh tends to kill the active ssh session - which is 'great design(TM)'...
<Borromini>
slh: i haven't noticed that personally.
<slh>
I'm seeing that quite regularly (Debian/unstable), as I'm upgrading quite a few (local-) systems via ssh
<Borromini>
i take your word for it.
<Borromini>
maybe a regression?
<slh>
I've been seeing it for a couple of years now (and I hopped onto networkd rather early on)
<f00b4r0>
i think that's "known". I remember seeing something like that on a website that collects all the reasons why systemd is an abomination :)
<Borromini>
xD
<Borromini>
i'm surprised Poettering didn't DDOS it yet ;)
<aiyion>
stintel, blocktrron: I've handed in a patch that ensures a unique and reboot persistent mac for the NanoPi R1 with eMMC and makes it more probable for the variant with just SD-cards.
<robimarko_>
You can get the latest versions for free
<nkko>
I have access to broadcom's cfe code and I've been going through it
<nkko>
I think I know how it mostly works now, with regards to loading the kernel image
<dwfreed>
stintel: free as in beer, but you do have to tell them who you are
<robimarko_>
Yeah, you have to have an account
yolo has joined #openwrt-devel
<robimarko_>
But no subscription or anything, same goes for 802.3 and some other standards families
<dwfreed>
Habbie: "Membership in Thread Group is necessary to implement, practice, and ship Thread technology and Thread Group specifications."
<yolo>
watched 2022.11 yocto summit esp its SPDX and SBOM, saying it's possible EU etc will mandate it for open source projects, openwrt might need that sometime
<Habbie>
dwfreed, ack, thanks
<hauke>
yolo: Is this about the EU Cyber Resilience Act?
<f00b4r0>
Borromini: turns out random reboots were due to lack of syslogd. Now I have more incentive to see if I could use openwrt's so I can stop killing my sdcard :)
robimarko_ has quit [Quit: Leaving]
<Borromini>
f00b4r0: glad you found the culprit :)
<f00b4r0>
was easy enough. After cpufreq didn't change anything I had a hunch the system might be unhappy without a way out for all those log messages
<f00b4r0>
probably overflowing the kernel buffer
<Borromini>
:)
<Borromini>
i've had times where I thought to myself 'nope can't be it' and kept digging stubbornly... only to find out hours later it *was* the first thing i thought of but found too obvious >_>
<f00b4r0>
yeah, I suppose old age taught me to pay more attention to the little voice ;)
<f00b4r0>
and be a bit less stubborn that I used to be
<Borromini>
i'm curious as to what you define as old age ;)
<f00b4r0>
I'm kidding
* Borromini
just passed 40
<f00b4r0>
although this day next month I'll be 42
<Borromini>
see ;)
<f00b4r0>
well this day -1 since we just past midnight
<Borromini>
congrats!
<f00b4r0>
heh
<Borromini>
oh next month
<Borromini>
sorry
<f00b4r0>
;)
<slh>
beware of the soon-to-be-neckbeard staring at you in the bathroom mirror ;)
<f00b4r0>
rofl
<Borromini>
:P
<f00b4r0>
anyway, me not getting any younger I need more sleep. gnight all :)