IPv6 connectivity stopped to work in LAN, ok on router

[trendy]

@Menion

Well my ISP gives a /64 prefix, so this is the result of the configuration following the instructions.

If they are allocating just a /64 for the wan6, then you cannot delegate it to the lan. What you can do is relay from lan.

@Menion

Neverthless I have exactly the same problem with the hurricane tunnel that gives a /48

We'll have to look at it individually, if you want to stick with that.

@Menion

I bridge WAN because I use a dedicated VLAN to bring the ISP LAN subnet to particular clients that may need it.

Since there is no other interface in the bridge, there is no usage of the bridge. If other clients need to connect directly to the ISP router this isn't the right way. Better connect them on the ISP router.

@Menion

What I am actually trying to do is to have the LAN interface to act as dhcpv6 server and delegate prefix based on the information of wan6.

Then this configuration is not correct. But even if you configure it as delegated, it won't work, because the ISP router will try to contact the hosts directly, because they are in the same subnet.

@Menion

Which one exaclty? they should be "normal" VPN and WAN rules

config forwarding
        option dest 'vpn'
        option src 'wan'

config forwarding
        option dest 'lan'
        option src 'wan'

@Menion

What shall I configure then, considering the on the 6in4 tunnel i get /64 prefix?

Use the last example of relay.
Or check here to use hybrid for both relay and delegation.