NMTUI

[Jwilliam]

When changing a connection on nmtui on say eth0, activating the connection will freeze it up, and then opening a new terminal and trying to SSH back into the server will fail giving port errors, what is the fix to this? is it something to do with cloud init?

Specifically its changing the IP and DNS, disabled cloud init, still does it. Not sure what else it could be?

[Jason_R_Preston · Accepted solution]

You should not ssh into the server for this task. You should instead use the "Open Console" button to the desired server. I made this same mistake myself, so I know your frustration.

Example: You are logged in on Server A and need to change the configuration on Server B. If you ssh from Server A to Server B you will have exactly the problem you describe. Instead, use the "Open Console" button for Server B to make the changes.

[Jwilliam]

Awesome, I appreciate you Jason! Now my question is, in the test environment if its requested to do the same, would it be a possability to just "open console" like that? 

Wonder why SSHing into the server and doing the changes causes it to do that, is there any technical reasoning for that? 

[Jason_R_Preston · Accepted solution]

First, to respect the NDA, I cannot say what is on the exam. I can say that if you are presented with a similar task on the exam, it is only logical that they would provide a reasonable way to accomplish the task, and in my opinion, a mechanism like "Open Console" would be reasonable option. At the beginning of the exam, take a few minutes to familiarize yourself with the interface, and this should not be an issue.

Second, it breaks your ssh connnection because you changed the network configuration. When you connect to Server B, that hostname resolves to a specific IP address. When you change the IP of Server B, your ssh session is now pointing to an invalid IP address. This is why you must make this change via the "Show Console" button.

[Jwilliam]

Appreciate it jason, one last question, after doing this it does work, but still cannot reach port 22 from servera sshing into serverb, is there something missing there? i readded SSH through firewall-cmd, reloaded, reloaded Netmanager, am I missing something?

[Jason_R_Preston]

Off the top of my head, I don't have enough information to troubleshoot this. What exercise are you working thru?

[Jwilliam]

its rh124, review 4 in the last chapter

[Jason_R_Preston]

I just worked thru the review4 exercise, and everything worked as expected.

Send me a screenshot of your "static" configuration from nmtui, please.

[Jwilliam]

  

Here is the NMTUI config, i took the snippet before finishing the second ip, but i did add the /24 at the end of .211 , and here are the successful pings, if i do ssh x.x.x.x i can get in to the server, but doing the lab grade gives me the port 22 fail

[Jason_R_Preston · Accepted solution]

Two things come to mind. First, for completeness sake, you should add the /24 for the subnet mask to your 2nd IP address, i.e. 172.25.250.211/24. I do not know if this will impact the final grade or not, but it is the most correct configuration.

Second, it appears you did not complete the final step in the exercise...

• On serverb, restore the original network settings by activating the original network connection profile.

When I left Server B configured with the "static" configuration, I got the same message from the grading script. Activate the original configuration, and try the grading script again.

Edit: I just noticed a third problem. It seems you editied the orginal configuration instead of creating a new one called "static." I am looking at the first lne of the nmtui screenshot for this information where it says "System eth0."

You don't want to edit the existing configuration with a static IP, you need create a New configuration called "static" and give it a static IP.