GL-AXT1800 - Unable to get connectivity on remote devices through Tailscale

I’ve setup tailscale using the official guide however I’m not able to ping remote devices through tailscale.

The exit node feature also won’t work and won’t create any routes in the administration panel to approve.

Which kind of logs would be useful to provide in this case ?

EDIT: I would also suggest to add tailscale as a toggle button option.

Thank you in advance

Is the tailscale official admin console set to allow access?

Yes, I have approved the node and the ACLs allow all access between nodes.

I will try to ping remote devices from the router shell to check if it has connectivity and if this is a routing issue.

Just confirmed, I’m able to ping other tailscale nodes within the router shell. This seems to be a routing issue on the router side.

EDIT: Routing table on one of the devices is using the router as gateway (as it should):

   route to: 100.XX.XX.XX (redacted)
destination: default
       mask: default
  interface: en0
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0

Routing table on the router side seems right:

root@GL-AXT1800:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         UG    20     0        0 wlan-sta0    *        U     20     0        0 wlan-sta0      *          U     0      0        0 tailscale0     *        U     0      0        0 br-lan     *        U     0      0        0 br-guest

Within the router I’m able to ping other tailscale nodes:

root@GL-AXT1800:~# ping 100.XX.XX.XX (redacted)
PING 100.XX.XX.XX (100.XX.XX.XX): 56 data bytes
64 bytes from 100.XX.XX.XX: seq=0 ttl=64 time=64.223 ms
64 bytes from 100.XX.XX.XX: seq=1 ttl=64 time=7.950 ms
64 bytes from 100.XX.XX.XX: seq=2 ttl=64 time=7.333 ms
--- 100.XX.XX.XX ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 7.333/26.502/64.223 ms

What am I missing ?

Any update ? Should I downgrade firmware ?

I’ve downgraded to 4.2.0 with no success (same behavior), I’ve reverted back to 4.2.1.