Member Avatar for silvercats

. In this image there is a network diagram

All rooms (shown by 1,2,3.....,11) should be in different networks.
X,Y,Z are the router's ports. What IP addresses should I put them?(Is it a must to put an IP to xyz parts?)
A is the router. what IP should I give it too?
Also I am hoping to give different IP addresses to other ports too (which leads to 1,2,3,.....11 rooms). That is not a much problem.but above ones are.

  • 3 Contributors
  • 2 Replies
  • 315 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by JorgeM

Dani AI

Generated

As drawn by the goal is eleven separate L3 networks (rooms 1–11). If X, Y and Z are router interfaces that must route between a subnet and the rest of the network, each of those interfaces needs an IP in the subnet it serves (that IP will act as the subnet’s gateway). If the physical ports are only switching ports on an access switch, the gateway can instead be an SVI on the switch or a routed SVI on the upstream device; the router itself only needs an address on the link to that switch in that case. ’s sizing idea and ’s note about the IT‑box router are both good starting points; the gaps to fill are link addressing (router↔router), gateway convention, DHCP placement and documentation.

A pragmatic, easy‑to‑operate plan (example using a private 10.0.0.0 space): inventory expected hosts per room, choose a subnet size for each room (small rooms get very small prefixes, larger rooms get /24s), and allocate a dedicated, very small subnet for any router‑to‑router links. Pick a consistent host position for the gateway in every subnet (for instance, reserve the third usable address as the gateway) and record the mapping in a spreadsheet. Example mapping (illustrative only):

Room 1 -> 10.0.1.0/24    gateway 10.0.1.3
Room 2 -> 10.0.2.0/24    gateway 10.0.2.3
...
Router A <-> IT router Z -> 10.0.254.0/30
Management VLAN -> 10.0.100.0/24   router mgmt 10.0.100.2

Operational notes and cautions: avoid overlapping address space, keep a single authoritative spreadsheet of port→VLAN→subnet→gateway→DHCP scope, reserve static addresses for printers/APs/servers, and put router management in a separate management VLAN. For isolation use ACLs or VRFs rather than relying on firewall rules alone. Troubleshooting is straightforward when documented: verify link status and VLAN tagging, ping the gateway from a host, inspect ARP and routing tables, and confirm DHCP scope/gateway alignment.

Recommended Answers

All 2 Replies

Member Avatar for donami

for the labs use 172.16.0.0/26 i.e this gives you 62 host in each subnet,172.16.0.1 to 172.16.0.62,172.16.0.65 to 172.16.0.126,172.16.0.129 to 172.16.0.190,172.16.0.193 to 172.16.0.254,172.16.1.1 to 172.16.1.62,172.16.1.65 to 172.16.1.126,172.16.1.129 to 172.16.1.190 and so on, an dyou can use a class c private address space for the other departments possibly 192.168.0.0/26 which allows you to have 62 host in each of th subnets

Member Avatar for JorgeM

It looks like based on the diagram that the expectation is that you further subnet the 192.168.1.x and 192.168.2.x subnets. Create subnets based on the number of hosts in each location, allowing for some room to grow.

The only other thing you have to consider is that a router was placed in the IT department box. That means that you have to create a segement between A and Z, then assign a subnet to the IT department box.

I have a subnet calculator that I built..you are free to use it to figure out the subnets and number of hosts... http://www.itgeared.com/tools/ip-subnet-calculator/

With regard to your question about what IP on the router's ports... the IP you will use will be the "default gateway" for each segement. To maintain consistnency, pick either the first available IP in each subnet or the last available IP in each subnet.

I hope this gets you going. I am hesitant to give you more information as this is a learning experience that you should definately grasp if network administration is what you are working on.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.