Hi, and thanks for taking the time to answer. There is no DHCP on the WAN interface. Just out of curiosity, I set up DHCP client, and it keeps stuck on “Searching”. It’s not a typical Internet provider, but a data center/colocation, although our office is directly connected via Ethernet. So there is also no DSL, cable or other PPP involved. We’re literally directly plugged into their routers.
I was under the impression that the ISP allocated the 2a00:1234:5:d00::/56 and expects me to subnet it to LAN/DMZ/guest/etc in the form of one or more /64 nets.
I set accept-router-advertisements=yes although that doesn’t make a difference. I simply don’t get why I am getting an answer to my ping on the router, but not when the ping originates from an internal host, despite the ping request leaving the WAN interface. The lan-in/wan-out forward rule counts packets, and I can see them leaving with Torch and Package Sniffer, but the wan-in/lan-out forward rule remains at zero. For example, I see:
lan rx 2a00:1234:5:d01:1a03:73ff:fe40:5f7a -> 2a00:1450:4001:80e::2003
wan tx 2a00:1234:5:d01:1a03:73ff:fe40:5f7a -> 2a00:1450:4001:80e::2003
But then the WAN interface never gets a reply from the public server. Not even sure if the ISP router forwards the initial ping request packet. Or if it’s just the answer that doesn’t get forwarded.