That looks like the output from ifconfig on your Ubuntu PC, not RPi OS on a Pi; the device names are wrong for a Pi OS on a Pi. ifconfig on the PC will not tell you anything about a remote Pi on the LAN. arp is a chicken and egg type thing, it won't list the Pi's IP until after something has communicated with it on the PC.
Your LAN DHCP server is the place to be looking in terms of figuring it out remotely. For most people, that's on their router. Exactly how to find it varies by router OS, but most of the decent ones have some way of looking at the dynamic DHCP leases.
If you don't have access to the router, you could try a broadcast ping from your Linux PC. I.e. "ping -b 192.168.1.255" if your IP subnet is 192.168.1.0/24. Unfortunately, that may be blocked by security on a communal router. Edit: Unfortunately, broadcast pings are blocked by RPi OS Bookworm by default, as it ships with "sysctl net.ipv4.icmp_echo_ignore_broadcasts = 1", so that's not going to work.
If your PC is a desktop PC, try temporarily using its monitor and keyboard on the Pi, to see what's going on when it boots. Or you could use a television with HDMI input.
You could connect your Pi to your PC by Ethernet, instead of connecting the Pi to the Wi-fi. Configure Ubuntu on the PC with its Ethernet and Wi-fi ports in a bridge group, and the Pi might then be able to access the Wi-fi via the PC. The communal router might block multiple devices using a single Wi-fi session, depending on its security settings, in which case you might need to get a bit creative about that config and do something more than a simple bridge.
Some communal routers will block communication between clients, only allowing communication between individual clients and the Internet. It's just one of those security settings which the network administrator can turn on, and it provides a little bit of privacy and security between the people sharing the router (while additionally preventing their devices from seeing each other). That can potentially prevent your Pi and PC directly talking to each other over communal Wi-fi.
Your LAN DHCP server is the place to be looking in terms of figuring it out remotely. For most people, that's on their router. Exactly how to find it varies by router OS, but most of the decent ones have some way of looking at the dynamic DHCP leases.
If your PC is a desktop PC, try temporarily using its monitor and keyboard on the Pi, to see what's going on when it boots. Or you could use a television with HDMI input.
You could connect your Pi to your PC by Ethernet, instead of connecting the Pi to the Wi-fi. Configure Ubuntu on the PC with its Ethernet and Wi-fi ports in a bridge group, and the Pi might then be able to access the Wi-fi via the PC. The communal router might block multiple devices using a single Wi-fi session, depending on its security settings, in which case you might need to get a bit creative about that config and do something more than a simple bridge.
Some communal routers will block communication between clients, only allowing communication between individual clients and the Internet. It's just one of those security settings which the network administrator can turn on, and it provides a little bit of privacy and security between the people sharing the router (while additionally preventing their devices from seeing each other). That can potentially prevent your Pi and PC directly talking to each other over communal Wi-fi.
Statistics: Posted by Murph9000 — Wed Sep 25, 2024 11:52 pm