On Saturday December 08 2018 00:05, you wrote to me:
Mv>> What happens iof you try to ping fido.vlist.eu?
WD> ********************************************************************** WD> Pinging fido.vlist.eu [2001:1c02:1100:bd00:f1d0:2:280:5555] WD> with 32 bytes of data:
WD> Reply from 2001:1c02:1100:bd00:f1d0:2:280:5555: time=25ms
So far so good.
You definitely have IPv6 and not just that, you have full dual stack. You not only have a block of IPv6 addresses, you also still have a public IPv4 address. Consider yourself lucky.
Mv>> Go to the setup of your router and look for a setting to enable Mv>> ICMP or PING for IPv6.
WD> I think there may be a problem there. The router is ISP-provided and WD> pretty good. However there are 3 lvels to log into "User", "Admin" and WD> "Expert" and they only give-out the password for "User".
WD> That level is too low to do what you ask.
Oh.... That sucks. Consider yourself not so lucky...
Maybe you still have a friend at Belgacom that can "arrange" something for you. Maybe there are some tricks to raise your access level. Google is your friend. An maybe we do not need it for now. Ping is nice, but not essantial.
WD> Let me get to their local shop on Monday and see if they understand WD> what I'm talking about ...
Don't be surprised if you get a blank stare if you ask about IPv6...
Mv>> Hmmm... click om the "general" button on the top..
Good, except for one thing. "ICMP filtered". IPv6 requires ICMP to properly functionm but not all of ICMP is needed. YMMV...
What puzzels me is that you obviously have outgoing IPv6 capability and your OS is configuerd to first try IPv6. A very simple quick test is here:
www.kame.net
If you see the turtle dance, you have outgoing IPv6.
What puzzles me is that your binkd does not make outgoing IPv6 calls. AFAIK, all versions of binkd that support IPv6 default to the OS preference when choosing between IPv4 and IPv6. In your case IPv6.
Binkd should make outgoing IPv6 calls. But it does not, you come in with IPv4 in my logs. Binkd can be forced to use either IPv4 or IPv6 on an outgoing call, but that is not the default.
There may be something in the interface between D'Bridge and Binkd that I am unaware of. Kees should be your man, AFAIK he is the only Fidonet sysop that got D'Bridge to do IPv6. Mv>> No incoming IPv6 yet.
With IPv4 you have to make an entry in the NAT table to allow incoming. With IPv6 there is nno NAT. Every device on the LAN has its own public IPv6 address. No need to do address translation.
By default the IPv6 firewall in the router will drop every unsollicited incomong IPv6 packet. To allow incoming one has to punch a hole in the firewall for the port(s) and destination(s).
In order to "help" users, router manufacturers sometimes call it "forwarding" anyway. Sometimes it is in the same page as the IPv4 forwarding, sometimes it a separate IPv6 page. So you have to look in the firewall settings for "port forwarding" or "opening ports" or something like that.
Since there is no translation, you specify just two parameters. The port number or port range and the destination. Sometimes the destination can be an IPv6 address, some also allow a MAC address.
If your router allows it I recommend using :: for the destination addres for port 24554. :: stands for "all IPv6 adresses" That way you never have to change it any more. And the risk of allowing port 24554 to all destinations in your LAn is minimal. If your router does not allow :: use the MAc address or IPv6 address of the destination.
