If that's the only route then your issue starts there. If you want to reach anything other than the local network there needs to be a default route to the gateway.
The default route is sent along the dhcp lease so my suspicion is that the issue is in the dhcp server config.
Just for context, this technology is not made for any specific end-consumer. This is for backbone connections of ISP and higher tier networks.
In that space, 400Gb/s is the current stuff that's being rolled out with 800Gb/s starting to get traction. 1.2Tb is just the next step to reduce the amount of Fibers and Ports used per connection (renting fibers of an undersea cable is expensive).
Though one issue I see slowing adoption is that new fibers are needed. With coherent optics we already achieve 800G with the same single mode fibers already in use.
Which fiber provider doesn't support IPv6? I thought it was only Swisscom mobile and its subsidiary's which don't support it (though from what I heard, even that is in testing now)
DHCP usually provides three things:
In the DHCP lease you for example get the IP 192.168.10.42/24. That IP is assigned to your interface which creates a implizit route like
192.168.10.0/24 dev netinterface. Now you know how to reach other hosts in your local network.In the same DHCP lease, you should also receive a default gateway - likely 192.168.10.1. this would add a route like
default via 192.168.10.1.Without the default route, packets for IPs other than your local network never leave your host because it doesn't know where to send them to.
DNS servers are also provided, though before troubleshooting that, I would just ping addresses like 8.8.8.8 (google dns) for testing connectivity.
(Btw, what I'm trying to say is: DHCP is working, but your server configuration may not be correct for what you're trying to do)
You could also skip troubleshooting DHCP by running
ip route add default via 192.168.10.1to test if your firewall is configured correctly. That should enable you to ping other networks.