XMPP Service Operators - 2023-04-10

What are user-side tools to manage personal MAM archive? Like, truncate or purge it? I think I heard of such some time ago.

As far as I know it is still an idea in the developers heads at this point.

Just to clarify my understanding of the previous discussion regarding sslh and transparent proxying. Is it possible to avoid needing to rewrite iptables/nftables rules if using the proxy protocol? It seems ejabberd supports it, but the community prosody module can't do it on TLS ports

Can someone clarify nixnet? Since ~March 30th I get > Failed to establish outbound s2s connection konvers.me -> muc.nixnet.services: Peer certificate rejected: certificate has expired; bouncing for 268 secon But search.jabber.network shows numerous mucs on nixnet with many users in them. Is that just servers who haven't rebooted or dropped connection for two weeks? or are some servers not checking cert? or???

unrelated I also see > Failed to establish outbound s2s connection conference.konvers.me -> jabber.lqdn.fr: DNS lookup failed: when trying to resolve it on a few resolvers I get a timeout, but some eventually return result on repeat

are you sure your resolver is good?

I'm using quad9 DoT with opportunistic dnssec

have no issues with others

dns can fail in non-obvious ways if TCP is dropped or your MTU isn't set correctly in combination with icmp filtering

mtu is fine, and there is no icmp filtering

lqdn.fr has their own nameserver and I suspect it is just slow

$ host -t SRV _xmpp-server._tcp.jabber.lqdn.fr _xmpp-server._tcp.jabber.lqdn.fr has SRV record 0 5 5269 iota.lqdn.fr.

i had 3 NXDOMAIN errors querying iota then the third time:

dig iota.lqdn.fr ; <<>> DiG 9.16.37-Debian <<>> iota.lqdn.fr ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23934 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;iota.lqdn.fr. IN A ;; AUTHORITY SECTION: lqdn.fr. 899 IN SOA pi4.lqdn.fr. root.pi4.lqdn.fr. 2023031601 21600 3600 1209600 3600 ;; Query time: 3 msec ;; SERVER: 192.168.55.1#53(192.168.55.1) ;; WHEN: Mon Apr 10 13:04:28 PDT 2023 ;; MSG SIZE rcvd: 86

still NXDOMAIN

dns is indeed broke

I am upset with the state of (or rather lack thereof) internet registries in America

Why is it that in America, we don't have LIRs and only the RIR ARIN?

ARIN charges $2500 initially and $600/year recurring fee for the smallest possible IPv6 range.

That's absolutely absurd

This isn't V4, these resources are not scarce. That could buy over 20 years of registration fees in europe.

What has stopped american LIRs from forming?

What is stopping us from pooling together and starting our own LIR?

one moment, I might have some info wrong

it's actually a lot more affordable if for an 'isp' and the qualification for isp doesn't just mean your a company like comcast

end user means your a mass mailing company or your providing a product without support

otherwise not providing a internet service like your a steel mill but need your own range

turns out the ARIN region does have LIRs but their not defined the same as in the LACNIC or APNIC regions. Large ISPs like lumen, charter, Frontier are LIRs. ARIN is unable to provide a list of LIRs and this may or may not be private information. LIRs in the ARIN region cannot issue ASNs. Only ARIN can issue ASNs. LIRs in the ARIN region can issue IPv6 blocks, but you do not actually own the registration rights to those blocks. If you switch peers or backbone providers you may lose those blocks.

Very recently as of Effective 1 January 2022 the ARIN board voted to change and ratify the way fees are handled across these LIRs, including "fee harmonization" which I think means LIR fees are the same as ARIN, defeating much of the point of LIRs.

Supposedly this was done to deter 'end user' type registrations from getting lower rates for LIRs like lumen, charter, frontier, etc.

https://www.arin.net/resources/fees/fee_schedule/

is the price really the big blocker when these are prereqs? > Have 13 end sites (offices, data centers, etc.) within one year > Use 2,000 IPv6 addresses within one year

that's not the requirements for the smallest allocation

at least I don't think, the way their documented is really confusing

https://www.arin.net/resources/guide/request/