Since now app03 and app04 are on different network range than jump host so you are not able to SSH into those hosts from jump host. To make SSH work make required changes on jump host.
a. Assign a new IP address 172.16.239.10/24 to jump host with same network range which app03 and app04 are using.
b. Now you will be able to SSH into all apps from jump host.
NOTE After the change, you may experience a delay when trying to SSH from the jump server to the app servers.
Question:How to ssh into all apps
lab 9
Now jump host is able to access all four apps. But if you try to ping app03 or app04 from app01 or app02 or vice versa you will see ping is not working. So now we want to use jump host as a router so that app01 and app02 can access app03 and app04 and vice versa, lets add some routing table entries on these hosts to make it work.
a. Add a routing table entry in app01 and app02 hosts so that these hosts can reach app03 and app04 hosts via jump host.
b. Add a routing table entry in app03 and app04 hosts so that these hosts can reach app01 and app02 hosts via jump host.
c. Now try to ping app03 and app04 from app01 and app02 and vice versa, every app should be able to ping each other.
Verify app01 is able to ping app02, app03 and app04
Verify app02 is able to ping app01, app03 and app04
Verify app03 is able to ping app01, app02 and app04
Verify app04 is able to ping app01, app02 and app0
Hi everyone, I just started this course.
I’m confused about this cmd “sudo ip route add 172.16.238.0/24 via 172.16.239.10” in Q9.
I don’t understand where are these 172.16.238.0/24 and 172.16.239.10 from? Can I use other ip address such as 172.16.238.2/24 or 172.16.239.13 ?
Hi @spur You need to be on the main thor@jump_host ~$ and here you need to type:
thor@jump_host ~$ ip route
default via 172.16.238.1 dev eth0
172.16.238.0/24 dev eth0 proto kernel scope link src 172.16.238.10
172.16.239.0/24 dev eth0 proto kernel scope link src 172.16.239.10
as you can see you find the linking IP addresses 172.16.238.10 and 172.16.239.10
What step in the lab are you in at this point? Assuming you assigned each of the app* hosts to the right IP address previously, this would suggest that you cannot get to app03 and app04 but that you should be able to ssh to app01 and app02. This is true until you assign an additional IP to jumphost that’s on the same network as app03 and app04.
If you can’t ssh into app01 and app02, it’s probably because you made an error of some kind before that point.
What step in the lab are you at the point of your image, and how did you get there?
Im running into this same issue. I dont see a response to @ashhadali2019 issue. I need to ssh into app01 and app02 and run the ip addr add command for to link both networks but i get “no route to host”
What host are you doing the command from? Key point: the ssh key that gets you the different appXX servers resides only on jumphost. So you need to be on jumphost to ssh into those hosts w/o a password.
right! Im running the command from the jumphost. running the command from the other hosts require a password. I was able to configure app03 and app04 but Im not able to access app01 and app02.
Has this changed over the course of the lab? If you’ve done things correctly as of Q8, then jumphost should be on both the 172.16.238.0/24 and 172.16.239.0/24 networks, having the addresses of 172.16.238.10 and 172.16.239.10 respectively. And your routing table should look like this:
thor@jumphost ~$ ip route
default via 172.16.238.1 dev eth0
172.16.238.0/24 dev eth0 proto kernel scope link src 172.16.238.10
172.16.239.0/24 dev eth0 proto kernel scope link src 172.16.239.10
172.17.0.0/16 dev eth1 proto kernel scope link src 172.17.0.4
