virgosystems Posted June 17, 2022 Posted June 17, 2022 nmcli states eth0 is connected on 192.168.1.10 but putty times out with 'connection refused'. Relevant screenshots attached. Many thanks in advance for any help Joe
CryBaby Posted June 17, 2022 Posted June 17, 2022 Is sshd running on your Pi? What do its logs say? Does your network have a route from 192.168.137.3 to 192.168.1.10? Can you ping it? 1
virgosystems Posted June 17, 2022 Author Posted June 17, 2022 Systemctl says sshd is running. Ping request (from Windoze to 192.168.1.10) times out. Nothing in /var/log/auth.log about ssh, but I guess that's expected.
CryBaby Posted June 17, 2022 Posted June 17, 2022 You'll need a route from the 192.168.137 network to the 192.168.1 network, probably in your gateway. Hopefully you have a network administrator who will cooperate.
virgosystems Posted June 18, 2022 Author Posted June 18, 2022 It's a direct ethernet connection. No hardware between rpi and windoze.
Werner Posted June 18, 2022 Posted June 18, 2022 Then either adjust one of the ip addresses to be in the same /24 subnet or adjust subnet mask on both to /16 1
virgosystems Posted June 18, 2022 Author Posted June 18, 2022 So you're saying I need to set manual address on both ends?
Werner Posted June 18, 2022 Posted June 18, 2022 If you do not have a dhcp server that distributes addresses automatically yes, you have to properly set manual addresses on all devices connected.
virgosystems Posted June 18, 2022 Author Posted June 18, 2022 Does address need to be identical on both windoze and rpi?
Werner Posted June 18, 2022 Posted June 18, 2022 Addresses need to be unique but within the defined subnet mask. From your previous postings and questions you seem either lacking fundamental networking knowledge and/or your home setup has some weirdness into. Both is out of scope of Armbian since its competence ends at the PHY plug. I suggest you try getting yourself more comfortable with that topic and start learning about it on places like https://www.geeksforgeeks.org/computer-network-tutorials/ or https://www.google.com/search?q=networking+for+beginners Best of luck.
CryBaby Posted June 18, 2022 Posted June 18, 2022 (edited) It will probably be easiest to just set your Pi to use 192.168.137.x where x is a number between 1 and 254 that is not in use by any other device on your network. If you have more than one ethernet interface in use you may also need to set a route in your PC to use the right interface for the Pi. Edited June 18, 2022 by CryBaby
Myron Posted June 20, 2022 Posted June 20, 2022 Erm... If this is a direct Ethernet connection between PC and SBC, is a cross-over cable required?
CryBaby Posted June 20, 2022 Posted June 20, 2022 Unlikely, unless the PC is ancient. Most interfaces these days have auto-MDI-X. 1
Myron Posted June 21, 2022 Posted June 21, 2022 On 6/20/2022 at 3:22 PM, CryBaby said: Unlikely, unless the PC is ancient. Most interfaces these days have auto-MDI-X. Still, worth checking. Maybe there is some setting on a NIC that has disabled auto-MDI-X?
Recommended Posts