03-22-2023 03:51 PM
In class I made a network with 6 smaller ones and one router for each two networks. I have everything fine and labelled for the networks and connected the serials. The issue is that when I try to add static routes to the routers, it says "%inconsistent address and mask". My professor checked mine and was also confused, everything SHOULD be working. So I'm wondering if anyone can load up the file and figure out what I'm missing. The networks are using .224 subnets and routers just 10.0.0.0. Here is the packet tracer file below.
03-22-2023 03:53 PM
PS R1 10.0.0.1 should connect to R2 10.0.0.2 | R2 11.0.0.1 to R3 11.0.0.2 | R3 12.0.0.1 to R1 12.0.0.2 | but none work.
03-22-2023 04:16 PM
Hello,
I cant open your file at the moment but I will a lot of times that happens its usually because people will put something like:
ip route 10.0.0.1 255.255.255.224 <next hop IP or exit interface>
The problem with that is the 10.0.0.1 is an exact IP address and not a network. You need to make sure you are putting the network address for the subnet you are trying to route to with the correct mask.
So it should look like:
ip route 10.0.0.0 255.25.255.224 <next hop IP or exit interface>
-David
03-22-2023 07:02 PM
Hey David,
Thanks for the info, ill try that. Since you cant open the file I attached a photo below if that helps with labelling.
03-22-2023 07:34 PM
Great! Can you give an example (or screenshot) of the command you enter and the device you enter it on?
03-22-2023 07:50 PM
Yes, here's a screenshot of some commands I put in. For some context, the subnet of the networks are 255.255.255.224 and the routers are 255.0.0.0. In the screenshot I'm in R1 (router 1) trying to add a static route to a network in R2 (router 2). I have some in the CLI too.
03-22-2023 07:52 PM
In case of confusion the mask I have in the screenshot isn't used (240) I was using 255.0.0.0 in CLI
03-22-2023 09:21 PM - edited 03-22-2023 09:21 PM
Yup. Just as I mentioned in my first post. You are trying to route to a specific IP address of 192.168.1.65 which is the IP of an interface of R2. Thats a valid IP but the router knows better and you need a nmask statement to match it. So you stement would read:
ip route 192.168.1.65 255.255.255.255 <next hop IP>
If you want the whole network you need this:
ip route 192.168.1.64 255.255.255.240 10.10.10.1
*check your labeling. YOu show R1 as having the IP of 10.0.0.1 when in fact R2 does and R1 has 10.0.0.2
Successful ip route statement and ping from R1
Just remember when putting in the IP route statement. Whatever you put in the mask MUST match the intent. If its a single IP then the mask is 255.255.255.255. If its a whole network you want to reach then you must supply the mask used to configure the network with. Therouter knows!
I will say I surprised your professor didn't catch it.
Hope that helps
-David
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide