You are not logged in.
Pages: 1
Hi there,
I have been trying to deal with this issue for a few hours now and can't figure it out. I am having another unrelated issue on my laptop and I am trying to ssh into it from my arch desktop but I am unable to, actually I can't ping local machines either. I am able to ssh from another laptop into this one but my dekstop seems to not be seen on the network, I can't ping from it or receive pings from other devices. Using ethernet or wifi dongle the issue still persits. This isn't ssh issue per-se but rather than something in my network settings that isn't working as it should be.
I have tried nmap on wifi and ethernet and found 0 IP addresses.
I have generated new ssh keys too which didn't change anything.
This is the output of me trying to ssh:
ssh -vvv root@192.168.0.53
OpenSSH_8.7p1, OpenSSL 1.1.1l 24 Aug 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: resolve_canonicalize: hostname 192.168.0.53 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/x/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/x/.ssh/known_hosts2'
debug3: ssh_connect_direct: entering
debug1: Connecting to 192.168.0.53 [192.168.0.53] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: connect to address 192.168.0.53 port 22: Connection timed out
ssh: connect to host 192.168.0.53 port 22: Connection timed outThe ip 192.168.0.53 is reachable from other devices though.
systemctl list-units |grep .service |grep running
accounts-daemon.service loaded active running Accounts Service
colord.service loaded active running Manage, Install and Generate Color Profiles
cronie.service loaded active running Periodic Command Scheduler
dbus.service loaded active running D-Bus System Message Bus
gdm.service loaded active running GNOME Display Manager
geoclue.service loaded active running Location Lookup Service
mullvad-daemon.service loaded active running Mullvad VPN daemon
NetworkManager.service loaded active running Network Manager
pamac-daemon.service loaded active running Pamac Daemon
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
sshd.service loaded active running OpenSSH Daemon
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
user@1000.service loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicantLast edited by Falladis (2021-09-26 17:33:32)
Offline
This isn't ssh issue per-se but rather than something in my network settings that isn't working as it should be.
So let's start there.
ip a; ip r
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fAnd finally please post a complete system journal ("sudo journalctl -b")
Offline
This isn't ssh issue per-se but rather than something in my network settings that isn't working as it should be.
So let's start there.
ip a; ip r find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fAnd finally please post a complete system journal ("sudo journalctl -b")
ip a; ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 78:24:af:47:1f:a2 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 78:24:af:d9:76:ec brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.0.173/24 brd 192.168.0.255 scope global dynamic noprefixroute eno1
valid_lft 3558sec preferred_lft 3558sec
inet6 fe80::4294:a5c7:75e7:9868/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: wlp0s20u14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 10:fe:ed:25:aa:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.0.137/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp0s20u14
valid_lft 3560sec preferred_lft 3560sec
inet6 fe80::1d20:671e:969a:fbfe/64 scope link noprefixroute
valid_lft forever preferred_lft forever
default via 192.168.0.1 dev eno1 proto dhcp metric 100
default via 192.168.0.1 dev wlp0s20u14 proto dhcp metric 600
192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.173 metric 100
192.168.0.0/24 dev wlp0s20u14 proto kernel scope link src 192.168.0.137 metric 600 find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
cronie.service | multi-user.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
dirmngr.socket | sockets.target.wants
display-manager.service | system
getty@tty1.service | getty.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
haveged.service | sysinit.target.wants
mullvad-daemon.service | multi-user.target.wants
mullvad-daemon.service | system
NetworkManager-wait-online.service | network-online.target.wants
NetworkManager.service | multi-user.target.wants
numlockon.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pamac-cleancache.timer | timers.target.wants
pipewire-media-session.service | pipewire.service.wants
pipewire.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
sshd.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
xdg-user-dirs-update.service | default.target.wantsThe last command outputs 45k lines. Whats the best way to deal with that output?
Offline
ix.io, but 45k lines is excessive - did you rise the debug level or so?
Edit: 1st link below
You've 3 NICs, enp6s0 has no carrier (no cable plugged), eno1 and wlp0s20u14 are connected to the same segment (192.168.0.0/24) in some(?) sort of failover(?) configuration.
Unless this is the explicit and deliberate cause of the problem, I'd suggest to only use one NIC for the moment and until the basic issues are sorted out.
Last edited by seth (2021-09-26 16:28:57)
Offline
ix.io, but 45k lines is excessive - did you rise the debug level or so?
Edit: 1st link belowYou've 3 NICs, enp6s0 has no carrier (no cable plugged), eno1 and wlp0s20u14 are connected to the same segment (192.168.0.0/24) in some(?) sort of failover(?) configuration.
Unless this is the explicit and deliberate cause of the problem, I'd suggest to only use one NIC for the moment and until the basic issues are sorted out.
I have a USB dongle connected to Wifi of the same router as my ethernet, this was a debug step, I forgot to remove it.
This is not an issue because the issue was present before. I will unplug the dongle now though.
The journal start from 2021-09-01 to 2021-09-26 hence the number of lines when I type in that command. You need this all? Also how would I decrease the length of the output for the specific parts you need?
Last edited by Falladis (2021-09-26 17:06:20)
Offline
The command is supposed to print the journal of the current boo ("-b"), did you not reboot since a month?
Another thing: your OP suggests a failure to ssh into 192.168.0.53, but that IP isn't attached to any NIC according to #3. Are you simply trying to connect to the wrong IP?
Offline
The command is supposed to print the journal of the current boo ("-b"), did you not reboot since a month?
Another thing: your OP suggests a failure to ssh into 192.168.0.53, but that IP isn't attached to any NIC according to #3. Are you simply trying to connect to the wrong IP?
So I figured it out thanks for my friend. He was also having trouble sshing into his laptop on the same network but we were both able to ssh into each others pcs to test. Even if we're both connected to the same router through wifi and ethernet they're on a different layer it seems.
After I unplugged my ethernet from my pc and only had the wifi dongle I was able to finally SSH.
Thanks for the help tho seth, much love.
Offline
Pages: 1