Don’t worry about that; that’s how it looks by default. Further, you shouldn’t need LuCI to set this up. It can all be done via the GL GUI.
That’s an unrouteable IP behind a NAT for any WG Client. There’s no public IP as it’s behind your company network. Unless you get get some port forwarding set up on the upstream router, you’d have to switch from a WG Server at your office to a WG Client to your RPi as a WG Server. Setting that up for the allowed ip directives & such would require some finagling though.
I know that may sound counter intuitive but here’s the thing: WG, in reality, is all peer to peer. I agree w/ GL that it’s easier to grasp the concept of a Server/Client paradigm though.
Here’s a ‘known good’ WG Server → WG Client on the same subnet. It may/may not be helpful. I’m sure you can adapt the IPs, confs to your needs:
Though this would appear to be more related:
(This is all WG so any confs generated by the GL GUI should easily work with your RPi.)