lovetoxThere tell me you see this option and think, No i defenitly want useless requests
lovetoxso i leave this unchecked
lovetoxturns out the useless request are not that useless
lovetoxthought to be fair thats not openwrt
lovetoxthats LUCI a webinterface for openwrt
ZashWat!
MartinWhat are 'useless requests' in openwrt jargon translated to plain english,✎
MartinWhat are 'useless requests' in openwrt jargon translated to plain english? ✏
lovetoxin dnsmask config which openwrt uses there is a decade old configswitch
lovetox -f, --filterwin2k
Later versions of windows make periodic DNS requests which don't get sensible answers from the public DNS and can cause problems by trigger-
ing dial-on-demand links. This flag turns on an option to filter such requests. The requests blocked are for records of types SOA and SRV,
and type ANY where the requested name has underscores, to catch LDAP requests.
lovetoxthis LUCI option turns this on, and filters all srv requests
lovetoxseems 12 years ago srv records counted as useless
selurveduhas joined
lovetoxsorry all srv records with underscore
lovetoxwhich xmpp uses
lovetoxbut i doubt this is on by default, i probably activated it because it looked good, when i configured my router
lovetoxgoes to show that you should not push buttons if you dont know what they do
ZashWin2k?!
lovetoxyeah more like 2 decades old :D
lovetoxbut that option is so bad named in in luci
lovetoxthe only reason to not activate that is when you actually know the background of what it does
lovetoxbut if Zash wouldnt have made that issue, i would probably never know that srv requests didnt work, like i wasnt impacted at all by this
nephelehas joined
selurveduhttps://git.openwrt.org/?p=project/luci.git;a=blob;f=modules/luci-mod-network/htdocs/luci-static/resources/view/network/dhcp.js;h=f425bd060509167d9be4ca6b50fd1c258fe45969;hb=HEAD#l385
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob;f=dnsmasq.conf.example;hb=9560658c5ba27a370b97d30850db474ce67912b7#l38
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
Yeah.
selurveduNot that useless.
selurveduhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464357 so this was fixed in upstream in 2008, but 13 years later it's still labelled as "useless" in OpenWrt :-\
ZashThings breaking SRV → admins deploying without → things continuing to break SRV
machas left
selurveduSpeaking of SRV, what level of support and adoption do direct TLS s2s connections and _xmpps-server SRV records have?
Zashejabberd seems to do it, and Daves proxy thing but the name escapes me
ZashMetre
ZashProsody trunk has some partial support, in that it can set up such a listening port and check if the SRV record is correctly set up
selurveduZash, will Prosody connect to a server via direct TLS s2s if _xmpps-server record is correctly set up?
ZashNo
ZashThat's the hard part
SamMinor weird thing that I didn't expect to cause me so much trouble: turns out pubsub items aren't directly in the IQ payload, they have a second wrapper (eg. instad of "<iq><pubsub><item1/><item2/>" you have "<iq><pubsub><items><item1/><item2/>"). Very clearly documented in the XEP, but I just kind of skipped over the extra wrapper not expecting it and took forever to track down the problem.
MartinBut you have something locally. Are there any issues stopping you from pushing it?
ZashMaking it *only* use `_xmpps-server` is easy. ✏
ZashMaking it use _both_ is *hard*
Kevhas left
MartinI see.
Kevhas joined
MartinAnyway, my server was part of the first prosody - prosody direct tls s2s connection. 😃
Martinupdates his CV…
SamIn pubsub land do you have to publish a complete XML document? If it's wrapped in <item/> could you publish <foo/><bar/> for example?
ZashSam: Yes. One child of `<item/>`, no more, no less.
SamThanks
ZashOnce upon a time there was a bunch of batch processing support in XEP-0060, that's where all the seemingly extra wrapper elements comes from
SamThat's what I figured; it seemed weird that there was a wrapper but then you couldn't eg. retract multiple items at once, why wrap in <items/> if it's only one item?
SamTrying to follow the constraints in this document is very difficult; thanks for the help.
ZashAh, there it is: https://xmpp.org/extensions/xep-0060.html#publisher-publish-error-badpayload
> If the <item/> element does not contain exactly one payload element [...] the service MUST bounce the request with a <bad-request/> error
ZashConveniently far away from "The syntax is as follows:" https://xmpp.org/extensions/xep-0060.html#publisher-publish-request
Sam"Ah, there it is" after some amount of time is exactly the problem I've been having :)
ZashWhat, aren't you used to reading kleinbottle-shaped hyperdimensional documents by now? 😉
SamAlas, it's a skill I've never mastered.
ZashTho this is one of those that constantly grow new text when you're not looking, so I agree it can be a bit confusing.
SamHowever, after multiple attempts to get something as simple as "be able to publish and retract an item" working, I think I've finally done it. Integration tests running now, so we'll see how ejabberd handles them though.
ZashIs this a client implementation?
SamYah
ZashCool
SamEventually it will grow a server side implementation too, but for now I just want "enough to fetch bookmarks"
ZashWhen do we finish the XEP-0060 split?
selurveduZash, I see, thanks. That is what I expected. I thought DTLS s2s is not supported anywhere, so I didn't configure it on my server, but since XEP-0368 mentions it, I decided to ask.
SamExcellent, ejabberd works too (for some reason it locks up the whole test suite if I try it locally, but works fine on the CI runner, so I'm never sure)
selurveduAlso I stumbled upon https://code.moparisthebest.com/moparisthebest/xmpp-proxy , it looks very interesting.
ZashSam, if you don't already have https://xmpp.org/extensions/xep-0223.html open in parallel, might be worth to do so
ZashDon't worry, it's only Informational, on use of pubsub for bookmarks and such
antranigvhas left
malthehas joined
me9has joined
mikeyehas joined
mikeyehas left
goffihas left
goffihas joined
marc0shas left
marc0shas joined
qrpnxzhas left
qrpnxzhas joined
qrpnxzhas left
qrpnxzhas joined
rom1dephas left
malthehas left
COM8has joined
goffihas left
selurveduhas left
marc0shas left
marc0shas joined
emushas left
Alexhas left
Alexhas joined
kikuchiyohas left
Kevhas joined
goffihas joined
Kevhas left
Kevhas joined
rom1dephas joined
marmistrzhas left
goffihas left
qrpnxzhas left
qrpnxzhas joined
qrpnxzhas left
qrpnxzhas joined
qrpnxzhas left
qrpnxzhas joined
COM8has left
qrpnxzhas left
qrpnxzhas joined
machas joined
Kevhas left
Kevhas joined
antranigvhas joined
Kevhas left
Kevhas joined
malthehas joined
antranigvhas left
antranigvhas joined
Kevhas left
Kevhas joined
machas left
PapaTutuWawahas joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
malthehas left
emushas joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
Yagizаhas left
goffihas joined
debaclehas joined
sanderhas left
Kevhas left
Kevhas joined
antranigvhas left
antranigvhas joined
malthehas joined
goffihas left
flowlovetox, you did not open an openwrt issue for, at least, better describing the configuration option, or maybe dropping it alltogether?✎
flowlovetox, you did not, by chance, open an openwrt issue for, at least, better describing the configuration option, or maybe dropping it alltogether? ✏