<ldir>
how can I reply/update the status on a patchwork patch if I don't have the original email in my inbox ?
<hauke>
ldir: you can update the status on all of your patches, it checks the email it was send from and you can configure multiple email addresses in patchwork
<hauke>
ldir: you should be part of the openwrt organisation then you can update all openwrt patches
<ldir>
it's not my patch - it's the dnsmasq bump which needs changes - basically a patch refresh
<zorun>
hauke: yes this should be enough (login, email, notify)
Rentong_ has joined #openwrt-devel
Rentong has quit [Read error: No route to host]
goliath has joined #openwrt-devel
SamantazFox has quit [Quit: Bye]
Rentong_ has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<PaulFertser>
hauke: I just paste user name, full user name, e-mail, check the "notify user" and press the button, and that's it.
<PaulFertser>
hauke: and I usually use the same both for user nick and full name.
<hauke>
PaulFertser: thanks
Rentong_ has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
Rentong_ has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Tapper has joined #openwrt-devel
takimata has quit [Ping timeout: 480 seconds]
mkresin has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
arifre has quit [Remote host closed the connection]
arifre has joined #openwrt-devel
aleasto has quit [Quit: Konversation terminated!]
Rentong has quit [Remote host closed the connection]
aleasto has joined #openwrt-devel
Rentong has joined #openwrt-devel
takimata has joined #openwrt-devel
Tapper has joined #openwrt-devel
takimata has quit [Quit: wat?]
takimata has joined #openwrt-devel
takimata has quit []
takimata has joined #openwrt-devel
mkresin has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
dorf has joined #openwrt-devel
Rentong_ has joined #openwrt-devel
Rentong_ has quit [Remote host closed the connection]
Rentong has quit [Read error: No route to host]
Rentong has joined #openwrt-devel
Rentong_ has joined #openwrt-devel
Rentong_ has quit [Remote host closed the connection]
Rentong_ has joined #openwrt-devel
Rentong_ has quit [Remote host closed the connection]
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<nick[m]4>
please write nickname xD I always get notified ^^
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong_ has joined #openwrt-devel
rejoicetreat has quit [Remote host closed the connection]
Rentong_ has quit [Remote host closed the connection]
Rentong_ has joined #openwrt-devel
Rentong_ has quit [Remote host closed the connection]
Rentong has quit [Read error: No route to host]
Rentong has joined #openwrt-devel
Rentong_ has joined #openwrt-devel
Rentong_ has quit [Remote host closed the connection]
Rentong has quit [Read error: Connection reset by peer]
<rsalvaterra>
ldir: Have you seen this with 2.86test3?
<rsalvaterra>
One of my dnsmasq instances isn't coming up, after the update… :/
Rentong has quit [Remote host closed the connection]
dorf has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
<ldir>
rsalvaterra: no, haven't seen that - looking at git log I note 3c93e8e Re-order UBus initialisation to avoid logging before logs set up. So was it always erroring you just didn't know
<rsalvaterra>
ldir: Do you run multiple instances?
<ldir>
no
<rsalvaterra>
Hm… I guess that might be broken, for some reason.
<rsalvaterra>
I noticed now (after restart) it's not a problem with any specific instance, any of them may come up, but only one.
Weasel___ has joined #openwrt-devel
<ldir>
I wonder what happens in ubus_init() and how that has changed
<ldir>
unfortunately I have to go and mix some football. - we could just revert
<rsalvaterra>
ldir: Can't really investigate now. I'll just revert, or my dad will kill me when he finds out he can't access the internet. :)
Rentong has joined #openwrt-devel
<ldir>
rsalvaterra: I'd be tempted to revert Etan Kissling's conntrack mark based DNS filtering 'cos that has played with ubus.c quite a bit. would be good to eliminate
<rsalvaterra>
ldir: It might have broken multi-instancing…
<rsalvaterra>
I'm positive that's the problem. Single-instance setups work just fine.
<rsalvaterra>
(I just tested again.)
<rsalvaterra>
Let me see if I can cook a revert patch in record time…
<rsalvaterra>
Need to clone the dnsmasq git tree first…
<ldir>
the other option is can you quickly come up with a way to pass a unique '--enable-ubus=<service-name>' option ?
<rsalvaterra>
Ouch. No easy revert.
Rentong has quit [Ping timeout: 480 seconds]
<ldir>
must go, sorry
rsalvaterra_ has joined #openwrt-devel
Rentong has joined #openwrt-devel
<rsalvaterra_>
ldir: Yeah, I just ended up reverting the bump. No ubus errors with 2.85, everything works. 2.86test3 is definitely broken.
<blogic_>
dnsmasq mayhem
<blogic_>
I was working on a simple dnsfwd agent today
<blogic_>
we can assume that in most deploys there is an upstream dns server (unless using a lantiq dsl SoC)
<blogic_>
I based this on the mdnsd codebase
<blogic_>
this would allow us to use odhcpd not only for v6 but also v4
<blogic_>
then have dnsfwd talk to odhcpd via ubus to allow local resolves
<blogic_>
I added a patch to dnsmasq last week to allow option82 dhcp relay support and I was shocked about the state of the code
rsalvaterra has quit [Ping timeout: 480 seconds]
<blogic_>
fun fact, there is a struct dhcp_message
<blogic_>
and in the code the struct invocation uses mess
<blogic_>
which is rather descriptive of the whole codebase
<blogic_>
I no longer want to run dnsmasq on my network
<blogic_>
and if anyone needs dnssec, they can install an unbound infront of dnsfwd
Rentong has quit [Ping timeout: 480 seconds]
rejoicetreat has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
<aparcar[m]>
hauke: me neither but I'd merge it
<aparcar[m]>
blogic_: please proceed that sounds awesome
Rentong has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
Tapper has quit [Ping timeout: 481 seconds]
Rentong has joined #openwrt-devel
<ldir>
ok I'll revert the dnsmasq bump
Rentong has quit [Ping timeout: 480 seconds]
<ldir>
reverted.
Tapper has joined #openwrt-devel
Rentong has joined #openwrt-devel
goliath has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Rentong has quit [Ping timeout: 480 seconds]
rejoicetreat has joined #openwrt-devel
Rentong has joined #openwrt-devel
Tapper has joined #openwrt-devel
<mangix>
Hauke: that patch should be merged, yes.
rejoicetreat has quit [Ping timeout: 480 seconds]
<mangix>
blogic_: wouldn’t doubt the state remains the same. Getting rid of it would be great.
Rentong has quit [Ping timeout: 480 seconds]
valku has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
rsalvaterra_ has quit [Ping timeout: 480 seconds]
jlsalvador has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
valku has quit [Quit: valku]
rmilecki has quit [Ping timeout: 480 seconds]
SamantazFox has joined #openwrt-devel
SamantazFox is now known as Guest644
SamantazFox has joined #openwrt-devel
SamantazFox is now known as Guest645
SamantazFox has joined #openwrt-devel
Guest644 has quit []
Guest645 has quit []
<rsalvaterra>
blogic_: Does odhcpd do DNS forwarding?
<rsalvaterra>
blogic_: Oh, dnsfwd… I never used that.
SamantazFox has quit []
SamantazFox has joined #openwrt-devel
<rsalvaterra>
blogic_: I'm all for the "do one thing and do it well" *nix way. However… does this dnsfwd thingy support per network forwardings? That's one of my pet peeves with dnsmasq, I have to run one instance per DNS forwarding.
<rsalvaterra>
blogic_: In other words, if dnsfwd could listen on multiple interfaces (no wildcard addresses, please) and forward DNS requests to different upstream servers depending on request source, that would be just perfect. :)
<aparcar[m]>
update, revert and now also some dns_fwd package in the game. were there some recent cve's?
<ldir>
no cves
<mangix>
aparcar[m]: excitement over potentially getting rid of dnsmasq
<mangix>
I know Turris people are looking into this.
<mangix>
They only use dnsmasq for its DHCP server stuff.
<ldir>
there are some good improvements to have and after finding & fixing a bug in test1/2 I thought test3 stable enough to have a try AND there were patches in patchwork
<aparcar[m]>
well that's what odhcpd is for isn't it?
<ldir>
so I applied them - rui found another issue to do with ubus support which I can only now reproduce.
<ldir>
I considered the best option was to revert.
<mangix>
aparcar[m]: so odhcpd has broken DHCPv4 support. That is, last I tried it, my Debian device was not getting an IPv4 address
<aparcar[m]>
mangix: w00t
<mangix>
once that's fixed, it should be good to go.
<aparcar[m]>
I'll ping daniel about that
<aparcar[m]>
mangix: can you fix it?
<mangix>
I don't know how. lol.
<mangix>
It might be an incompatibility with networkd
<mangix>
IIRC, Windows was getting a DHCP address
<mangix>
IPv4 that is. IPv6 worked as usual.
<aparcar[m]>
mhh IPv4 is kind of still athing
<mangix>
AFAIK my ISP doesn't do IPv6
<mangix>
could also be my modem. who knows.
<mangix>
DOCSIS MIMO IPv4 Only
<ldir>
what your ISP supplied doesn't matter - this is lan facing
<mangix>
Right. Even in my LAN there are still IPv4 only devices
<slh>
networkd is a bit hit or miss, I still use it, but there are quite a few oddities - both with DHCPv6 (as client) and losing network during systemd upgrades
Rentong has joined #openwrt-devel
<mangix>
slh: it's default with openmediavault. not easily replaceable
<slh>
plain debian here, so I could do whatever I wanted, but technically networkd is a good and very flexible choice, but it's still lacking in some domains - and fragile