Resources on setting up my local network
Many years ago I set up a network of 4 Linux machines running RHEL 5. At the time it all seemed straight-forward. However, over the last few years, most of my work has required Windows. When I attach a Windows 7 or 10 machine to the network, everything just works. I now have project where the program only runs on Linux. So I installed Kubuntu 18.04 from a live image. Nothing related to networking functions and the messages I get make so little sense I have not been able to google a solution.
To start, all the machines are part of the domain td-research.com. The netmask is 255.255.255.0, I created an /etc/hosts file on the new machine and assigned it 172.24.2.65. The internal address of the modem that acts as the dns server is 172.24.2.2. Everything is hard-wired.
I then went to Configure Network Settings
Some of the terminology is not completely clear to me, but the settings I used were:
Method: Manual
DNS Servers: 172.24.2.2,8.8.8.8
Search Domains: td-research.com
Address: 172.24.2.65
Netmask: 255.255.255.0
Gateway: 172.24.2.1
and required IPv4, just to try and get this started.
I can ping vesta and it says it is pinging 172.24.2.70, which is correct from the hosts file.
I am not sure I believe it. If I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect. When I say yes, it says it connected, but 'hostname' returns themis- the LOCAL computer and using ls, it is clear that it logged into itself, not another computer.
resolv.conf has the search field for the domain, but it does not list the nameservers that I thought I setup earlier. The /etc/network/interfaces has nothing in it except the loopback interface. But ifconfig shows inet 172.24.2.65 netmask 255.255.255.0 broadcast 172.24.2.255. A netstat -r shows 172.24.2.0 as a destination with a gateway of 0.0.0.0 and a Genmask of 255.255.255.0.
I cannot rlogin or ssh from vesta to themis either, I just get host unreachable.
Most of the google hits refer to performing operations that no longer work or involve commands that don't exist.
Could any one suggest what to do in terms of debugging this or tutorial that actually explains the whys of the steps and is not just a bunch of magic commands to type? Or are there pieces of kubuntu that need to be installed?
I already installed net-tools and the ssh-server.
I do notice that when it 'connects' it says last login from 127.0.0.1 and not last login from 172.24.2.65. Whereas if I log in from vesta to one of my other RHEL machines, I'll see last login from vesta as the message.
If I look in resolv.conf I see a nameserver 127.0.0.53. I saw something that said that sudo systemctl disable systemd-resolved would remove that and fix my problem. When I rebooted, the network would not connect until I unchecked IPv4 is required. And even then FireFox stopped working-
networking kubuntu
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Many years ago I set up a network of 4 Linux machines running RHEL 5. At the time it all seemed straight-forward. However, over the last few years, most of my work has required Windows. When I attach a Windows 7 or 10 machine to the network, everything just works. I now have project where the program only runs on Linux. So I installed Kubuntu 18.04 from a live image. Nothing related to networking functions and the messages I get make so little sense I have not been able to google a solution.
To start, all the machines are part of the domain td-research.com. The netmask is 255.255.255.0, I created an /etc/hosts file on the new machine and assigned it 172.24.2.65. The internal address of the modem that acts as the dns server is 172.24.2.2. Everything is hard-wired.
I then went to Configure Network Settings
Some of the terminology is not completely clear to me, but the settings I used were:
Method: Manual
DNS Servers: 172.24.2.2,8.8.8.8
Search Domains: td-research.com
Address: 172.24.2.65
Netmask: 255.255.255.0
Gateway: 172.24.2.1
and required IPv4, just to try and get this started.
I can ping vesta and it says it is pinging 172.24.2.70, which is correct from the hosts file.
I am not sure I believe it. If I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect. When I say yes, it says it connected, but 'hostname' returns themis- the LOCAL computer and using ls, it is clear that it logged into itself, not another computer.
resolv.conf has the search field for the domain, but it does not list the nameservers that I thought I setup earlier. The /etc/network/interfaces has nothing in it except the loopback interface. But ifconfig shows inet 172.24.2.65 netmask 255.255.255.0 broadcast 172.24.2.255. A netstat -r shows 172.24.2.0 as a destination with a gateway of 0.0.0.0 and a Genmask of 255.255.255.0.
I cannot rlogin or ssh from vesta to themis either, I just get host unreachable.
Most of the google hits refer to performing operations that no longer work or involve commands that don't exist.
Could any one suggest what to do in terms of debugging this or tutorial that actually explains the whys of the steps and is not just a bunch of magic commands to type? Or are there pieces of kubuntu that need to be installed?
I already installed net-tools and the ssh-server.
I do notice that when it 'connects' it says last login from 127.0.0.1 and not last login from 172.24.2.65. Whereas if I log in from vesta to one of my other RHEL machines, I'll see last login from vesta as the message.
If I look in resolv.conf I see a nameserver 127.0.0.53. I saw something that said that sudo systemctl disable systemd-resolved would remove that and fix my problem. When I rebooted, the network would not connect until I unchecked IPv4 is required. And even then FireFox stopped working-
networking kubuntu
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit withCould not resolve hostname vesta: Name or service not known
– steeldriver
Dec 29 '18 at 18:06
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
That's completely normal, and nothing to do with/etc/hosts- it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established
– steeldriver
Dec 29 '18 at 18:35
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38
add a comment |
Many years ago I set up a network of 4 Linux machines running RHEL 5. At the time it all seemed straight-forward. However, over the last few years, most of my work has required Windows. When I attach a Windows 7 or 10 machine to the network, everything just works. I now have project where the program only runs on Linux. So I installed Kubuntu 18.04 from a live image. Nothing related to networking functions and the messages I get make so little sense I have not been able to google a solution.
To start, all the machines are part of the domain td-research.com. The netmask is 255.255.255.0, I created an /etc/hosts file on the new machine and assigned it 172.24.2.65. The internal address of the modem that acts as the dns server is 172.24.2.2. Everything is hard-wired.
I then went to Configure Network Settings
Some of the terminology is not completely clear to me, but the settings I used were:
Method: Manual
DNS Servers: 172.24.2.2,8.8.8.8
Search Domains: td-research.com
Address: 172.24.2.65
Netmask: 255.255.255.0
Gateway: 172.24.2.1
and required IPv4, just to try and get this started.
I can ping vesta and it says it is pinging 172.24.2.70, which is correct from the hosts file.
I am not sure I believe it. If I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect. When I say yes, it says it connected, but 'hostname' returns themis- the LOCAL computer and using ls, it is clear that it logged into itself, not another computer.
resolv.conf has the search field for the domain, but it does not list the nameservers that I thought I setup earlier. The /etc/network/interfaces has nothing in it except the loopback interface. But ifconfig shows inet 172.24.2.65 netmask 255.255.255.0 broadcast 172.24.2.255. A netstat -r shows 172.24.2.0 as a destination with a gateway of 0.0.0.0 and a Genmask of 255.255.255.0.
I cannot rlogin or ssh from vesta to themis either, I just get host unreachable.
Most of the google hits refer to performing operations that no longer work or involve commands that don't exist.
Could any one suggest what to do in terms of debugging this or tutorial that actually explains the whys of the steps and is not just a bunch of magic commands to type? Or are there pieces of kubuntu that need to be installed?
I already installed net-tools and the ssh-server.
I do notice that when it 'connects' it says last login from 127.0.0.1 and not last login from 172.24.2.65. Whereas if I log in from vesta to one of my other RHEL machines, I'll see last login from vesta as the message.
If I look in resolv.conf I see a nameserver 127.0.0.53. I saw something that said that sudo systemctl disable systemd-resolved would remove that and fix my problem. When I rebooted, the network would not connect until I unchecked IPv4 is required. And even then FireFox stopped working-
networking kubuntu
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Many years ago I set up a network of 4 Linux machines running RHEL 5. At the time it all seemed straight-forward. However, over the last few years, most of my work has required Windows. When I attach a Windows 7 or 10 machine to the network, everything just works. I now have project where the program only runs on Linux. So I installed Kubuntu 18.04 from a live image. Nothing related to networking functions and the messages I get make so little sense I have not been able to google a solution.
To start, all the machines are part of the domain td-research.com. The netmask is 255.255.255.0, I created an /etc/hosts file on the new machine and assigned it 172.24.2.65. The internal address of the modem that acts as the dns server is 172.24.2.2. Everything is hard-wired.
I then went to Configure Network Settings
Some of the terminology is not completely clear to me, but the settings I used were:
Method: Manual
DNS Servers: 172.24.2.2,8.8.8.8
Search Domains: td-research.com
Address: 172.24.2.65
Netmask: 255.255.255.0
Gateway: 172.24.2.1
and required IPv4, just to try and get this started.
I can ping vesta and it says it is pinging 172.24.2.70, which is correct from the hosts file.
I am not sure I believe it. If I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect. When I say yes, it says it connected, but 'hostname' returns themis- the LOCAL computer and using ls, it is clear that it logged into itself, not another computer.
resolv.conf has the search field for the domain, but it does not list the nameservers that I thought I setup earlier. The /etc/network/interfaces has nothing in it except the loopback interface. But ifconfig shows inet 172.24.2.65 netmask 255.255.255.0 broadcast 172.24.2.255. A netstat -r shows 172.24.2.0 as a destination with a gateway of 0.0.0.0 and a Genmask of 255.255.255.0.
I cannot rlogin or ssh from vesta to themis either, I just get host unreachable.
Most of the google hits refer to performing operations that no longer work or involve commands that don't exist.
Could any one suggest what to do in terms of debugging this or tutorial that actually explains the whys of the steps and is not just a bunch of magic commands to type? Or are there pieces of kubuntu that need to be installed?
I already installed net-tools and the ssh-server.
I do notice that when it 'connects' it says last login from 127.0.0.1 and not last login from 172.24.2.65. Whereas if I log in from vesta to one of my other RHEL machines, I'll see last login from vesta as the message.
If I look in resolv.conf I see a nameserver 127.0.0.53. I saw something that said that sudo systemctl disable systemd-resolved would remove that and fix my problem. When I rebooted, the network would not connect until I unchecked IPv4 is required. And even then FireFox stopped working-
networking kubuntu
networking kubuntu
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Dec 29 '18 at 19:55
asked Dec 29 '18 at 17:54
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 29 '18 at 17:54
Jon Swanson
11
asked Dec 29 '18 at 17:54
Jon Swanson
11
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit withCould not resolve hostname vesta: Name or service not known
– steeldriver
Dec 29 '18 at 18:06
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
That's completely normal, and nothing to do with/etc/hosts- it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established
– steeldriver
Dec 29 '18 at 18:35
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38
add a comment |
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit withCould not resolve hostname vesta: Name or service not known
– steeldriver
Dec 29 '18 at 18:06
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
That's completely normal, and nothing to do with/etc/hosts- it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established
– steeldriver
Dec 29 '18 at 18:35
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit with
Could not resolve hostname vesta: Name or service not known– steeldriver
Dec 29 '18 at 18:06
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit with
Could not resolve hostname vesta: Name or service not known– steeldriver
Dec 29 '18 at 18:06
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
That's completely normal, and nothing to do with
/etc/hosts - it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established– steeldriver
Dec 29 '18 at 18:35
That's completely normal, and nothing to do with
/etc/hosts - it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established– steeldriver
Dec 29 '18 at 18:35
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38
add a comment |
1 Answer
1
active
oldest
votes
Sorry everyone, it was my fault. There was a typo in the /etc/hosts file and I did not see it. Once I fixed it, the problem went away! I think if the rlogin had failed, I would have caught it faster.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Jon Swanson is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105419%2fresources-on-setting-up-my-local-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sorry everyone, it was my fault. There was a typo in the /etc/hosts file and I did not see it. Once I fixed it, the problem went away! I think if the rlogin had failed, I would have caught it faster.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Sorry everyone, it was my fault. There was a typo in the /etc/hosts file and I did not see it. Once I fixed it, the problem went away! I think if the rlogin had failed, I would have caught it faster.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Sorry everyone, it was my fault. There was a typo in the /etc/hosts file and I did not see it. Once I fixed it, the problem went away! I think if the rlogin had failed, I would have caught it faster.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Sorry everyone, it was my fault. There was a typo in the /etc/hosts file and I did not see it. Once I fixed it, the problem went away! I think if the rlogin had failed, I would have caught it faster.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 29 '18 at 20:27
Jon Swanson
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 29 '18 at 20:27
Jon Swanson
11
answered Dec 29 '18 at 20:27
Jon Swanson
11
11
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jon Swanson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Jon Swanson is a new contributor. Be nice, and check out our Code of Conduct.
Jon Swanson is a new contributor. Be nice, and check out our Code of Conduct.
Jon Swanson is a new contributor. Be nice, and check out our Code of Conduct.
Jon Swanson is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105419%2fresources-on-setting-up-my-local-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"f I rlogin -4 vesta it says the vesta is not recognized and asked me if I want to connect." - what is the message, exactly? If it's a name resolution failure, rlogin should exit with
Could not resolve hostname vesta: Name or service not known– steeldriver
Dec 29 '18 at 18:06
Unfortunately, it asks once and then adds something to some configuration file. Here is the message: The authenticity of host 'vesta (127.24.2.70) can't be established. ECDSA key fingerprint is [big number]. Are you sure you want to continue? And if yes something gets updated somewhere and I don't see the message again.
– Jon Swanson
Dec 29 '18 at 18:24
Warning permanantly adding 'vesta' (ECDSA) to the list of known hosts. Though vesta is in /etc/hosts.
– Jon Swanson
Dec 29 '18 at 18:28
That's completely normal, and nothing to do with
/etc/hosts- it's just a way for SSH to flag possible MITM attacks - see for example The authenticity of host '103.35.202.76 (103.32.202.71)' can't be established– steeldriver
Dec 29 '18 at 18:35
yes, I didn't think that was my problem. However, when I rlogin vesta from themis and themis logs into itself instead, that is a problem.
– Jon Swanson
Dec 29 '18 at 18:38