On Friday November 29 2013 15:52, you wrote to me:
BF> Welcome to the gang. I've been (theoretically at lest) IPv6 BF> compatible for more than three years now. But to no (binkp) avail.
Same here I have two tunnels running. One from SuxSx taht covers one machine and one from he.net that survices the entire LAN.
BF> felten.yi.org can successfully be pinged, but all telnet/binkp BF> access will be denied.
Good. Or maybe not.. If felten.yi.org also han an AAAA record attached and indeed it does, then your nodelist entries advertise a method of connection that you do not actually support. The is - as some would say - detrimental to the smooth opeartion of the network. Why? Because this way you make it harder for Kees, Wilfred and Andrew to connect to your system. If their mailers go by the information in the nodelist, their mailers will first try to connect via IPv6. That will fail. Presumably the mailers will eventually try IPv4, but that may take considerable time depending on the exact configuration. It could be minutes...
If you do not support incoming IPv6 over binkp, then the host name advertised in the nodelist should not have an AAAA record. If you want other applications to be reacheable via IPv6, you should use a differeny host name for that than the one in the nodelist used for binkp.
