News:

SMF - Just Installed!

Main Menu

Can not use ssh through Ethernet anymore

Started by kalpana, Oct 21, 2023, 04:46 AM

Previous topic - Next topic

kalpana

Hello, I'm currently struggling with some problems trying to ssh my Raspberry Pi 3 to my Ubuntu 22.04. I don't have any chance to connect to my raspberry Pi over wifi and I also don't have any keyboard nor monitor to interface it. The only option left is trying to connect with ssh over Ethernet.
This is not the first time I do this and it has worked before, so my main problem is not really with my Raspberry but with my Ethernet interface.

A little bit more about the raspberry. I have set up in the past a telegram bot, that connects to the raspberry and give me the exact IP address of the board, both for the Ethernet port and the Wifi. So whenever I want to connect I just use the telegram bot to get the ethernet address and try to ssh it, but I get this error:


Code:
ssh: connect to host 169.254.38.195 port 22: No route to host
Before I go on I should mention that my friends try to connect with the same process but using different laptops, but using the same IP given by the telegram bot and it worked. So the problem lies in my computer. I have tried a lot of troubleshooting guides to fix my ethernet interface but nothing has worked. I've tried to restart the network manager, check if the drivers were updated, changed multiple times some of the settings of the ethernet port but nothing has worked so far. The only thing I didn't do is updating the kernel, but I want to avoid doing that now.

My guess is that the ethernet port is not being given an Ipv4 address, because when I run this commands I don't get any Ipv4 under the ethernet interface infos:

Code:
ifconfig
enp4s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 54:ab:3a:b5:db:2f  txqueuelen 1000  (Ethernet)
        RX packets 201  bytes 41875 (41.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 496  bytes 85990 (85.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 126  base 0xb000 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 7598  bytes 880053 (880.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7598  bytes 880053 (880.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.218.206.21  netmask 255.255.252.0  broadcast 10.218.207.255
        inet6 fe80::75b:c62b:3211:8764  prefixlen 64  scopeid 0x20<link>
        ether 54:8c:a0:a8:e4:95  txqueuelen 1000  (Ethernet)
        RX packets 82207  bytes 77203393 (77.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38669  bytes 6491855 (6.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I beg for your help, I am losing my mind :)