In a terminal on deb, type hostname. This will return the actual hostname of that machine. Then in a terminal on any other machine on the network, type "ssh deb", possibly replacing deb with the actual hostname. There is nothing extra needed to use the hostname with ssh. Either the hostname or the ip address should give the same results, nothing else needed. If a VPN is in use, or deb is on a different local network, then that has to be addressed, but I don't know if that is the case. If the debian machine is on the network, it has an ip address and a hostname, you just have to find and use the correct one.
Solved Sftp with dual boot
- Thread starter Danbor
- Start date
Solved issue
Hello deb_user. I must have my network totally borked. I can ping all computers using the ip address. However, trying to ping any hostname returns "Name or service not known"
I am using Nord VPN on all machines with LAN discovery on, but as pinging via ip address works, and sftp through file manager works on all but the just added dual booted debian system, I doubt that is the issue.
I'm feeling badly for taking taking up so much of everyones time on this so I'll drop it for now. It's not a mission critical problem just frustrating that I can't make it work. I do have an sftp connection from deb to all the other computers, just not from any computer to deb. I'll further research how to assign deb it's own ip address and get it working both directions that way.
I was going to try and get things working using ssh.config files but though I think I have host, hostname, and username understood, I can't figure out how to supply the IdentifyFile so that's out.
Thanks to everyone that has tried to help. I appreciate the kindness.
I am using Nord VPN on all machines with LAN discovery on, but as pinging via ip address works, and sftp through file manager works on all but the just added dual booted debian system, I doubt that is the issue.
I'm feeling badly for taking taking up so much of everyones time on this so I'll drop it for now. It's not a mission critical problem just frustrating that I can't make it work. I do have an sftp connection from deb to all the other computers, just not from any computer to deb. I'll further research how to assign deb it's own ip address and get it working both directions that way.
I was going to try and get things working using ssh.config files but though I think I have host, hostname, and username understood, I can't figure out how to supply the IdentifyFile so that's out.
Thanks to everyone that has tried to help. I appreciate the kindness.
The VPN may be the problem. More than likely you are correct.
But, I managed to learn how to assign a static ip address to the debian computer.
Rebooted it and now I can SFTP both ways! Success!
Thanks to everyone.
But, I managed to learn how to assign a static ip address to the debian computer.
Rebooted it and now I can SFTP both ways! Success!
Thanks to everyone.
I'm not sure if I'm following properly, but I used to use NordVPN. It allowed 'whitelisting' addresses, I'm pretty sure. That meant that certain addresses would bypass the VPN and connect directly. Maybe setting that for local addresses will help.
(I think I'm following along, but I may have missed something along the way.)
(I think I'm following along, but I may have missed something along the way.)
Yes, Nord does allow whitelisting addresses. It didn't cross my mind that the VPN might be the issue as the SFPT using the ip addresses works.
Now that I've got it up and running, I need to take a timeshift snapshot and file backup before I play with it any longer. And I can't do that until the back roads are plowed so I can get to town and pick up some more USB sticks.
I'll revisit this thread and report back what I find out.
Now that I've got it up and running, I need to take a timeshift snapshot and file backup before I play with it any longer. And I can't do that until the back roads are plowed so I can get to town and pick up some more USB sticks.
I'll revisit this thread and report back what I find out.
theLegionWithin
Well-Known Member
I suspect a DNS issue (lol "it's never dns!"). I'd recommend looking at the DNS settings in your router and/or the DNS settings in your pihole, if you have one set up.
Since @Danbor has now circled the VPN app as culprit, that behaviour probably takes precedence regardless of what the router does. Yes, a router can still assign names to hosts, but it's not requisited.
The default Linux daemon to propagate the hostname to local lan is the avahi-daemon. So, on the toshiba machine with config in #19, check if the daemon is started and look at its log
It will (/should) show a line like
This is what makes the hostname discoverable locally. - Given there is no firewall/VPN (which integrates fw-rules) prohibiting the daemon to broadcast.
The default Linux daemon to propagate the hostname to local lan is the avahi-daemon. So, on the toshiba machine with config in #19, check if the daemon is started and look at its log
journalctl -b -u avahi-daemon.It will (/should) show a line like
avahi-daemon[729]: Server startup complete. Host name is .... This is what makes the hostname discoverable locally. - Given there is no firewall/VPN (which integrates fw-rules) prohibiting the daemon to broadcast.
Done a little more digging. While Nord does offer whitelisting, it can't be used when lan discovery is on. So it's either or but not both.
I checked journalctl -b -u avahi-daemon and there is an entry for the hostname.
So I probably could turn lan discovery off on all machines and whitelist them all, on all machines. But since they are all now communicating with each other I'll consider the issue successfully resolved. But it's good to know there are options in case things go pear shaped.
Plus, I learned a little more about the OS.
I checked journalctl -b -u avahi-daemon and there is an entry for the hostname.
So I probably could turn lan discovery off on all machines and whitelist them all, on all machines. But since they are all now communicating with each other I'll consider the issue successfully resolved. But it's good to know there are options in case things go pear shaped.
Plus, I learned a little more about the OS.
