danitool has quit [Read error: Connection reset by peer]
<SpaceRat>
Greetings!
<SpaceRat>
Is there any method to know from which partition a WRT3200ACM booted to OEM firmware?
danitool has joined #openwrt-devel
<SpaceRat>
I'm currently preparing a WRT3200ACM for return and I want to remove all traces of OpenWrt (And especially my configs) from the router ... I already flashed the OEM firmware over the previously active installation of OpenWrt, but I want to make sure it's also gone from the other partition.
<SpaceRat>
Ok, I think I could solve it myself :)
<SpaceRat>
When the OEM firmware booted and I flash the OEM firmware again, it should go to the other partition ...
feriman has quit [Ping timeout: 240 seconds]
kristrev_ has joined #openwrt-devel
kristrev has quit [Read error: Connection reset by peer]
<russell-->
stintel: lol, i just sent a patch and then noticed you'd already fixed the missing config-5.10 symbol
<russell-->
stintel: i just marked my patch as superseded in patchwork
<stintel>
russell--: thanks
sbrown has joined #openwrt-devel
ChanServ has quit [shutting down]
zkrx has quit [Ping timeout: 252 seconds]
sbrown has quit [Read error: Connection reset by peer]
ChanServ has joined #openwrt-devel
sbrown has joined #openwrt-devel
sbrown_ has joined #openwrt-devel
sbrown has quit [Read error: Connection reset by peer]
<tmn505>
Hauke: please add this to release notes: the default rootfs patition size changed for targets/devices relying on booting from mass storage (HDD, USB flash, SD card, etc.), so MBR will change and any additional partition will be deleted when sysupgrading. Backup Your data.
<stintel>
Habbie: had a small remark, if you fix that I'll push the button afterwards :)
<Habbie>
haha
<Habbie>
i -just- squashed those because I couldn't figure out in which of the two i should bump PKG_RELEASE
<stintel>
:D
<Habbie>
pushed
<stintel>
you can actually do it in both I would say
<Habbie>
oh i messed up the DCO again
<Habbie>
ok, will do that
<Habbie>
done and signed off
<stintel>
they both change the package so the PKG_RELEASE bump is needed. you could argue that because it's a single PR you can do it only in the last commit of the PR
<Habbie>
yes, i figure the answer would be 'last' or 'both' or 'squash'
<Habbie>
*figured
<stintel>
hmmm and maybe copy the details from the PR to the relevant commit message
<Habbie>
makes sense
<Habbie>
pushed
<stintel>
lol, now that approve button disappeared
<stintel>
ah
<stintel>
it's back
<Habbie>
interesting that the DCO check runs without approval - a special github feature I guess?
<stintel>
magic ;)
<stintel>
but the DCO check is cheap, just checks the commit author + message
<Habbie>
oh, that i get, but apparently github knows this :)
<stintel>
the rest of those checks ... take some CPU cycles ;)
<Habbie>
yep :)
<Habbie>
i have several more patches and i keep thinking 'i should submit them' but they rely on a release candidate of dnsdist ;)
madwoota has quit [Read error: Connection reset by peer]
kristrev_ has quit [Read error: Connection reset by peer]
kristrev has joined #openwrt-devel
madwoota has joined #openwrt-devel
madwoota has quit [Changing host]
madwoota has joined #openwrt-devel
<mirko>
is the pkg maintainer of unbound - Eric Luehrsen - around by any chance?
<Habbie>
i know a thing or two about unbound - depending on what your question is :)
<mirko>
Habbie: i want to forward my queries to a tcp port listening on 127.0.0.1
<mirko>
however everything 127.0.0.1 alike defined in forward zones in /etc/config/unbound doesn't make it into the generated unbound.conf
<mirko>
i wonder if it's on purpose or a bug. seems on purpose as everything !=127.0.0.1 /does/ go into the generated unbound.conf
<mirko>
it seems about $dns_ast within the uci-parsing/conf-generating scripts within the unbound pkg however i'm a bit lost
<mirko>
ah, it explicitly checks whether local_subnet() is true and discards if that's the case
<mirko>
but still doesn't make it into the generated conf.., hrmpf
<Habbie>
is local_subnet true for 127?
<mirko>
i think so, but even dropping that check doesn't help
<mirko>
without knowing the purpose/intentions it's quite hard to parse and understand the scripts :/
<Habbie>
where does 'local_subnet' come from?
<mirko>
iptools.sh
<mirko>
but found another hint:
<mirko>
else
<mirko>
# soft brick loop back risk see DNS assist above
<mirko>
127.*|::0*)
<mirko>
case $server in
<mirko>
didn't see it as i was grepping for '127.0.0.1'
<Habbie>
ah!
<Habbie>
if it reaches that, it sounds like local_subnet was never true to begin with
<Habbie>
stintel, i see $(AUTORELEASE) would also have caused two bumps on my two commits - if the port used it :)
<mirko>
nice catch
<stintel>
ah I haven't used that before
<Habbie>
stintel, i was about to push my unbound PR, then i realised i forgot to bump it, and there was no number there
<mirko>
Habbie: so you're involved in powerdns?
<Habbie>
mirko, yep
<mirko>
interesting, using it heavily with a maintenance frontend from like 10 years ago (poweradmin) - upgrading/re-doing on my todo list for years and coming indeed closer
<Habbie>
ah
<Habbie>
changing frontends too i bet?
<mirko>
Habbie: it's protected via tls client cert auth and users having certs considered trusted, but yes, at least evaluation what's out there
<mirko>
not yet, it's on my todo list without having started any evaluation yet
<Habbie>
ack :)
<mirko>
but thanks, will put the list right next to my powerdns-todo-list-item :>
<Habbie>
hehe
<stintel>
heh poweradmin. also using that one still :)
<mirko>
oh, there's frontend directly using the powerdns API nowadays
<Habbie>
several in fact
<mirko>
that's neat, so you can interchange frontends?
<Habbie>
well, you could also interchange db-based frontends, depending on how much extra stuff they store
<Habbie>
and some API-based frontends still have their own extra db for user management etc.
<Habbie>
but if you ignore all that, then yes, you can :)
<mirko>
ok, that helps a lot in not having to put too much thought into which frontend, as i figured i have to stick with what i choose fr the next 10 years as custom database schema
<Habbie>
PowerDNS-Admin is the community favourite, followed by Opera DNS UI, I believe
<Habbie>
(i have not tried any of them myself)
<mirko>
poweradmin "Last Commit 2019-02-21" - not as bad as i feared.. maybe i could just get away with updating..
<mirko>
but once on it, doing it right i guess - so looking will at PowerDNS-Admin first. thanks!
<mirko>
i use poweradmin's features pretty excessively.. from user management over its templates for new zones, etc.
<mirko>
so migration will be quite some effort either way
<Habbie>
right
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 240 seconds]
kristrev has quit [Read error: Connection reset by peer]