From: noel <deletethis@invalid.lan>
Subject: Re: News./Tcpreset./Net Open for peering
Newsgroups: news.admin.peering
References: <vsl5ae$2htvi$1@news.tcpreset.net>
	<20250403202001.41731d6f@ryz.dorfdsl.de> <vsmpvl$3eqqt$1@news.tcpreset.net>
	<20250404082737.529cc57d@ryz.dorfdsl.de>
	<slrnvuuvl7.2qbc2.rayban@raybanana.net> <67f37a31$1@news.ausics.net>
	<7p17p7o4-sr4-n018-o82s-o678q5r26op1@sbk.nhfvpf.arg>
User-Agent: Pan/0.141 (Tarzan's Death; 168b179 git.gnome.org/pan2)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: news.ausics.net
Message-ID: <67f3cd00$1@news.ausics.net>
Date: 7 Apr 2025 23:02:56 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 28
X-Complaints: abuse@ausics.net
Path: ...!weretis.net!feeder9.news.weretis.net!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 2290

also did you check hetzner, I'm told if you checked enable ipv6 filter,
nothing gets through unless you allow it on their cloud

 
> On Mon, 7 Apr 2025, noel wrote:
> 
>> unless I missed it, I don't recall Gabx confirming above nmap output on
>> their side of the great firewall. Also don't recall seeing the latest
>> netstat after they said they fixed it not listening.
>>
>> I also see tcpreset domain has LE errors - check web redirections,
>> seems didn't include subdomains on cert generation, but still throws
>> errors becasue of next point.
>>
>> DNSSEC conflict, must have upgraded old SHA1 key with 13/2, but not
>> removed the sha1 key (in most cases since do have a good 13/2 as well,
>> the sha1 might be ignored, but pedantic test scripts (like one we use
>> will issue a fail status), as will some services, saying the cert is
>> not trusted. https://zonecheck.org/zonemaster might be of use
>>
>> What ports are supposed to be open on ipv6 ?
>> I only see imap and imaps on ipv6 but you have on ipv4 some 9 services.
>> if you can shell to that machine lynx https://zonecheck.org (it will
>> show you your IP, if it gives you an IPv6 display, select port scanner
>> and run the basic tcp check
>>
>> I also not sure why you are using inn 2.6.2, thats some 4 years old now
>> with 2.7.2 current and 2.8 weeks from release IIRC.