As mentioned by CondorWonder, the LG via Serial HA Integration can already connect to a TCP socket instead of a TTY device.
If you want to use your Raspberry Pi as the serial proxy server, there’s tons of options. To recommend something kinda modern, I’d put a systemd service on your raspberry pi which starts netcat on a stty, see https://stackoverflow.com/a/71173551/2232127 as an example.
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.1 to test if your firewall is configured correctly. That should enable you to ping other networks.
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.
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)
What do you mean by expensive? It’s free open source software no?
That doesn’t match my experience with AUR at all. Usually it pulls a specific git revision and checks the hash. This also ensures that the build shouldn’t suddenly fail to some extent.
Though it’s entirely possible that it’s not like this for all packages, though I find it kind of counterintuitive since your package manager wouldn’t know when to perform an update in this case.
A diagram of the relevant Hypervisor/VMs/containers + Network information would be helpful.
From where and how are you testing DNS? Did you use dig and specified the nameserver directly?
Well since the Pi is already there and has a serial interface, getting an ESP32 is still more expensive :)