Assigning a /32 to an interface that connects to something else doesn't make any sense. You can assign the /32 to a loopback interface:
interface Loopback0
ip address 192.168.1.1 255.255.255.255
If you want to assign the 192.168.10.1
address to the GigabitEthernet0/0 interface which uses 192.168.10.0/24
:
interface GigabitEthernet0/0
ip address 192.168.10.1 255.255.255.0
This results in the network 192.168.10.0/24
entry in the routing table as a connected route (C
). I suppose it depends on the IOS version, but you can also get a local (not link local which is something else, entirely) route to the specific (/32
) address assigned to an interface in your router. My IOS does this. The version you have doesn't show the L
in the codes, whereas mine does as the first entry:
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override
`
Based on you comments, it seems that you first problem is that you don't know how to subnet, and you need to divide your 23.12.0.0/24
network into four subnets. You can do this by using /26
networks.
Assign a different /26
network to each of the sites, and you will need a network different than the site-assigned networks for you router-to-router link. Usually, you will use a /30
or /31
network for a point-to-point link like you have between the routers.
Once you have the networks correctly assigned, you can set up your routing. Each router will inherently know about the networks directly connected to it, but the router will need to be told about the networks on the other side of the other router. You can do this with static routes (this doesn't scale well), or you can run a common routing protocol between the routers that will automatically tell each router about the networks connected to to the other router.
Best Answer
Check the routing tables on these devices to confirm these routes exist.