> Looks like to setup a 6in4 tunnel, I need a static public IP first
I don't think that static IP is needed to make it work at least temporarily, I don't have a static one either, just public. You only need to have public IP on the device you can manage - e.g. router at home, and make sure that raspberry has a static internal address. Then, in the router's firewall/forwarding settings, either set raspberry as the DMZ host, or set forward anything from the remote tunnel IP to raspberry.
That being said, if are behind a carrier NAT which you can't manage, you won't be able to set up the tunnel.
I've just tried the switch to dwc2 driver, it didn't help. (still on ~1018 kernel).
> Looks like to setup a 6in4 tunnel, I need a static public IP first
I don't think that static IP is needed to make it work at least temporarily, I don't have a static one either, just public. You only need to have public IP on the device you can manage - e.g. router at home, and make sure that raspberry has a static internal address. Then, in the router's firewall/forwarding settings, either set raspberry as the DMZ host, or set forward anything from the remote tunnel IP to raspberry.
That being said, if are behind a carrier NAT which you can't manage, you won't be able to set up the tunnel.
I've just tried the switch to dwc2 driver, it didn't help. (still on ~1018 kernel).