We have a new one:
81 2:243/39 Karl Kral Native WEDOS
Karl, your system still needs a bit of tuning. Sometimes an attempt to connect at IPv6 times out and an IPv4 connect results. Sometimes it
takes a while but there is an IPv6 connect anyway. Sometimes there is an
IPv6 connect right away.
Suggestions anyone?
We have a new one:
81 2:243/39 Karl Kral Native WEDOS
I believe you mean 2:423/39.
Suggestions anyone?
-46 :)
81 2:243/39 Karl Kral Native WEDOS
I believe you mean 2:423/39.
Yes. I stand corrected.
connectivity...Suggestions anyone?
-46 :)
hmm... I was hoping for suggestions that would help him improve his IPv6
Ryan, welcome to the Fidonet IPv6 club.
We have a new one:
There is another at 1:153/146 also.. :)
Christina, welcome to the Fidonet IPv6 club.
I might change the IPv6 address soon to one that includes F1D0 :)
(the DNS name will stay the same, of course)
Christina, welcome to the Fidonet IPv6 club.
Thank you! :)
I might change the IPv6 address soon to one that includes F1D0 :)
(the DNS name will stay the same, of course)
Regards,
Anna
I just saw that the DNS name you used ends in binkp.net...
Who is administering these records?
BTW your IPv6 address does not ping:Daten:
D:\FIDO\IPV6>ping box.imzadi.de
Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32 Bytes
Zielprotokoll nicht erreichbar.thingies)
Zielprotokoll nicht erreichbar.
Zielprotokoll nicht erreichbar.
Zielprotokoll nicht erreichbar.
Ping-Statistik für 2001:470:540b:0:ba27:ebff:fef1:42dc:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),
You may want to open your IPv6 firewall for PING. (And some other ICMP
BTW your IPv6 address does not ping:
D:\FIDO\IPV6>ping box.imzadi.de
Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32
Bytes Daten:
Zielprotokoll nicht erreichbar.
Zielprotokoll nicht erreichbar.
Zielprotokoll nicht erreichbar.
Zielprotokoll nicht erreichbar.
Ping-Statistik für 2001:470:540b:0:ba27:ebff:fef1:42dc:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100%
Verlust),
You may want to open your IPv6 firewall for PING. (And some other
ICMP thingies)
Ping is not needed for binkp connections. Also telnet to her bbs
works fine.
I might change the IPv6 address soon to one that includes F1D0 :)I just saw that the DNS name you used ends in binkp.net...
(the DNS name will stay the same, of course)
Who is administering these records?
BTW your IPv6 address does not ping:Ping is not needed for binkp connections. Also telnet to her bbs works fine.
You may want to open your IPv6 firewall for PING. (And some other ICMP
thingies)
You may want to open your IPv6 firewall for PING. (And some other
ICMP thingies)
Ping is not needed for binkp connections.
Also telnet to her bbs works fine.
Blocking ICMP (including ping) is dangerous: this tells possible
hackers the administrator of such network is mentally impaired.
I might change the IPv6 address soon to one that includes F1D0 :)When you do, I will update the list.
Regards,I am confused... The nodelist says "Christina Nass" and so does your
Anna
binkp server. How do we call you and how do you want to be listed in the list of IPv6 nodes?
Is "Anna Christina Nass" OK with you?
BTW your IPv6 address does not ping:
You may want to open your IPv6 firewall for PING. (And some other ICMP
thingies)
Blocking ICMP (including ping) is dangerous: this tells possible hackers the administrator of such network is mentally impaired.
I see you use a he.net tunnel.
I see your IPv4 address is from DTAG. DTAG provides native IPv6 to
(some?) of its customers. There are two German Fidonet sysops that have native IPv6 from DTAG.
You do not have native IPv6 from DTAG or is there another reason you use
a he.net tunnel?
I've enabled PING6 now for this host...
I chose this, as my DTAG DSL connection would indeed offer a
Dual-Stack IP connection, but the IPv6 prefix is not fixed and could change at any time - kind of like the IPv4 address.
And thus I would need dynamic DNS not only for IPv4 but also for
IPv6... So I chose to stay with my he.net tunnel
-- which also allows me to specify reverse DNS servers. I don't know
if that is even remotely possible for a private DTAG DSL connection...
Aha. How often does it change? I too have dynamic addresses, In theory.(...)
For a hobby system it is no big deal if IPv6 is occasionally
down for a few hours.
For IPv6 it is more difficult than for IPv4.
The he.net tunnel did a fine job, but I never
got more than half the IPv4 speed.
I might change the IPv6 address soon to one that includes F1D0 :)
(the DNS name will stay the same, of course)
I just saw that the DNS name you used ends in binkp.net...
Who is administering these records?
For a hobby system it is no big deal if IPv6 is occasionally
down for a few hours.
Well, that is true, yes. But I want my setup to be stable and reliable
- and thus I went this way and won't change it any time soon :)
(DynDNS)
For IPv6 it is more difficult than for IPv4.
A little, maybe. At least if you use "standard" DynDNS providers. Recently, I changed my setup so that I'm my own DynDNS provider for
most of my needs. Thus, "box.imzadi.de" is a CNAME entry for "box.my.imzadi.de", and the nameserver for the "my.imzadi.de" domain
is on my vServer and this gets the new IP at every change from my home router.
The he.net tunnel did a fine job, but I never
got more than half the IPv4 speed.
Oh, I don't notice any real slowdown here, it is "fast enough" for my needs :)
Xs4All sunset was three years ago.
I don't know if that is even remotely possible for a private DTAG DSL connection...
I chose this, as my DTAG DSL connection would indeed offer aAha. How often does it change? I too have dynamic addresses, In
Dual-Stack IP connection, but the IPv6 prefix is not fixed and
could change at any time - kind of like the IPv4 address.
theory. My IPv4 address has been stable for almost two years now. It
only changes when the MAC address of the CPE changes. It can be stable
for years. The IPv6 prefix changes a bit more often and there is no visible pattern. But it is only twice a year or so. Not often enough
to bother with dyndns. On the rare occasion that it changes, I just
update it manually. For a hobby system it is no big deal if IPv6 is occasionally down for a few hours.
On 11-16-20 14:26, Tommi Koivula wrote to Michiel van der Vlist <=-
You may want to open your IPv6 firewall for PING. (And some other ICMP
thingies)
Ping is not needed for binkp connections. Also telnet to her bbs works fine.
I don't know if that is even remotely possible for a private DTAG
DSL connection...
Yes ... definitely not doable with the DTAG IPv6.
Hello Richard,
On Tuesday November 17 2020 08:48, you wrote to Anna Christina Nass:
I don't know if that is even remotely possible for a private DTAG
DSL connection...
Yes ... definitely not doable with the DTAG IPv6.
Reverse DNS is not needed for binkp connections. (in "Tommi style") :-)
On 11-16-20 14:26, Tommi Koivula wrote to Michiel van der Vlist <=-
You may want to open your IPv6 firewall for PING. (And some other ICMP
thingies)
Ping is not needed for binkp connections. Also telnet to her bbs works fine.
But from what I recall, IPv6 is even more dependent on properly working ICMP than IPv4, so even if ping is blocked, other ICMP needs to be allowed.
I don't have to worry about reverse DNS. My ISP does that for me. ;-)
I don't have to worry about reverse DNS. My ISP does that for me. ;-)
But you cannot control it.
+ 17 Nov 11:35:28 [7821] incoming session with 2001:1c02:1102:ac00:f1d0:2:280:5555
+ 17 Nov 11:35:28 [7821] addr: 2:280/5555@fidonet
host 2001:1c02:1102:ac00:f1d0:2:280:5555 5.5.5.5.0.8.2.0.2.0.0.0.0.d.1.f.0.0.c.a.2.0.1.1.2.0.c.1.1.0.0.2.ip6.ar
pa domain name
pointer 2001-1c02-1102-ac00-f1d0-0002-0280-5555.cable.dynamic.v6.ziggo .nl.
See. It is not fido.vlist.eu :)
Reverse DNS is not needed for binkp connections. (in "Tommi style")
:-)
What's that style?
But I know that DTAG has even a page, where you can trigger an IPv6 network prefix change. But they also do it periodically.
Some of their customers see it as a "privacy" feature.
zugeordnetenI don't have to worry about reverse DNS. My ISP does that for me. ;-)
But you cannot control it.
I am not a control freak. ;-)
+ 17 Nov 11:35:28 [7821] incoming session with 2001:1c02:1102:ac00:f1d0:2:280:5555
+ 17 Nov 11:35:28 [7821] addr: 2:280/5555@fidonet
host 2001:1c02:1102:ac00:f1d0:2:280:5555 5.5.5.5.0.8.2.0.2.0.0.0.0.d.1.f.0.0.c.a.2.0.1.1.2.0.c.1.1.0.0.2.ip6.ar pa domain name
pointer 2001-1c02-1102-ac00-f1d0-0002-0280-5555.cable.dynamic.v6.ziggo .nl.
See. It is not fido.vlist.eu :)
I know. It is still better than how you come in:
- 06 Nov 01:03:24 [1228] incoming from 2001:999:93:5fa::15 (60628)
+ 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte Name ist
gültig und wurde in der Datenbank gefunden. Er
verfügt jedoch nicht über die richtigen
Daten, die ausgewertet werden sollten. (11004)
+ 06 Nov 01:03:24 [2676] incoming session with 2001:999:93:5fa::15
- 06 Nov 01:03:24 [2676] SYS RBB/2
- 06 Nov 01:03:24 [2676] ZYZ Tommi Koivula
No backresolve.. ;-)
@MSGID: 2:280/464 5fb3b1cf^^^^
@REPLY: 2:280/5555 5fb3aad3
@PID: GED+LNX 1.1.5-b20161221
@TID: FMail-lnx64 2.1.0.18-B20170815
@RFC-X-No-Archive: Yes
@TZUTC: 0100
@CHRS: UTF-8 2
Looks like utf-8 in a CP850 message? :-(
Guess what, I can't control my ISP's DNS. ;-)
Looks like utf-8 in a CP850 message? :-(
Hello Tommi,
On Tuesday November 17 2020 14:46, you wrote to me:
Guess what, I can't control my ISP's DNS. ;-)
Figures. ;-)
Reverse DNS is not needed for binkp connections. (in "Tommi style")
:-)
But from what I recall, IPv6 is even more dependent on properly
working ICMP than IPv4, so even if ping is blocked, other ICMP needs
to be allowed.
Guess what, I can't control my ISP's DNS. ;-)
Figures. ;-)
In fact I'm using several outbound gateways, so you can see a few different incoming addresses.
Reverse DNS is not needed for binkp connections. (in "Tommi style")
:-)
Sure ... but it is nice to have ;)
Other than that, it is my understanding that most of the IPv6 network
works pefectly well without reverse DNS. It is rumoured that mail
servers are the exception.
Other than that, it is my understanding that most of the IPv6
network works pefectly well without reverse DNS. It is rumoured that
mail servers are the exception.
Many smtp servers refuse mail from ip addresses without a valid
reverse. Both ipv4 and ipv6.
Other than that, it is my understanding that most of the IPv6 network works pefectly well without reverse DNS.
It is rumoured that mail servers are the exception.
Many smtp servers refuse mail from ip addresses without a valid
reverse. Both ipv4 and ipv6.
So I heard too. I haven't encountered any problems myself.
Now that you mention smtp servers, I have not yet run into an smtp
server that supports IPv6...
Yes ... but nice to have means it works without but it still is nice
to have ;) I stand by that point.
It is rumoured that mail servers are the exception.
That is not a rumour!
If you get back a different domainname you usually get a malus.
Many smtp servers refuse mail from ip addresses without a valid
reverse. Both ipv4 and ipv6.
So I heard too. I haven't encountered any problems myself.
Try sending mail to google smtp servers. It's not that easy.
Now that you mention smtp servers, I have not yet run into an
smtp server that supports IPv6...
I have been running such a thing for many years.
One of the advantages of HE tunnel is that you have static ipv6 and
can run smtp server.
Try sending mail to google smtp servers. It's not that easy.
I have never tried and have no plans to try in the foreseeable
future. I stay away from Gmail.
One of the advantages of HE tunnel is that you have static ipv6
and can run smtp server.
You need Sage status to unblock port 25. But you have that of course.
;)
So I heard too. I haven't encountered any problems myself. Now that you mentionsmtp servers, I have not yet run into an smtp server that
supports IPv6...
I have never tried and have no plans to try in the foreseeable
future. I stay away from Gmail.
So you are not communicating anyone that uses gmail?
There are also millions on companies that "rely" to google mail
services.
But since you apparently send all your email to your ISP's smarthost,
you don't see the problems they may get when trying to send mail via google.
You need Sage status to unblock port 25. But you have that of
course. ;)
Of course I do. :)
Google does:
Name: ASPMX.L.GOOGLE.COM
Address: 2607:f8b0:400d:c00::1a
Our Office 365 tenant doesn't seem to support IPv6 yet.
Now that you mention IPv6, your incoming IPv6 is down:
Dynamic IP?
On 11-17-20 19:13, Richard Menedetter wrote to Tony Langdon <=-
Indeed!
Especially IPv6 packet too big messages.
IPv4 would fragment on the way.
That is not possible in IPv6 where fragmentation is only allowed on the ends of a connection.
It relies on the ICMP packet too big arriving at the sender, so he can resend.
Yeah that makes sense, and even blovking IPv4 ICMP causes strange
issues, like without path MTU discovery, senders won't know to adjust packet size.
On 11-19-20 21:22, Richard Menedetter wrote to Tony Langdon <=-
At least IPv4 can fragment on the way.
IPv6 is dropped instead of fragmented ... that makes a difference ;)
IPv6 is still down...
www.ipv6scanner.com reports bbs.nrbbs.net as open for IPv4 and Filtered forIPv6...
www.ipv6scanner.com reports bbs.nrbbs.net as open for IPv4 and Filtered forIPv6...
IPv6 is still down...I'm showing it as up and available externally with some port scanners.
Can someone else give it a try?
So... it is not your provider that changed the prefix. That would affect thefirst 64 bits. It is within your own local network that the host
part, the last64 bits have changed. So the issue is a local issue and should be addressedlocally.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 765 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 02:53:56 |
| Calls: | 12,759 |
| Calls today: | 3 |
| Files: | 15,360 |
| Messages: | 6,556,967 |