Before security tools or application code make sense, you need to see how a computer gets an address, how a name becomes an IP, and how a packet crosses from one room’s network to another. At Computer Education And Cybernetics (CEC) you practise that on cables, switches, routers and your own packet captures — at our three Ahmedabad centres.
One lab visit, four hops
A PC asks for an address, a switch keeps it inside one VLAN, a router carries it to another subnet, and DNS turns the server’s name into an IP. When any step fails, the app looks broken.
Computer networking is the practice of giving devices addresses, moving packets between those addresses, and turning names into IPs with DNS. TCP/IP is the protocol suite that does this; the OSI model is the seven-layer map you use to say where a failure sits. At Computer Education And Cybernetics (CEC) in Ahmedabad you trace one lab connection this way and write which hop failed.
The OSI model is a seven-layer map for talking about networks. TCP/IP is the four-layer suite you actually see: application, transport, internet and link. You use the map to say where a failure sits, then you look at the real packets.
An IP address plus a mask says which bits name the network and which name the host. Variable length subnet masking (VLSM) lets you cut a block into pieces that match the number of hosts, instead of wasting a huge subnet on a small room.
A router forwards packets between networks. You start with a static route you type yourself. A routing protocol such as OSPF lets routers tell each other which networks they can reach, so you are not typing every path by hand.
A switch forwards frames inside a local network using MAC addresses. A VLAN splits one switch into separate logical networks. An access port sits in one VLAN. A trunk carries several VLANs between switches.
DHCP hands a PC an address, a mask and a gateway when it joins. DNS turns a name into an IP address. If either fails, the application looks “down” even when the cable is fine.
Wireshark records the packets on a lab interface. You filter for DHCP or DNS, read who spoke first, and write what the capture proves. A summary you cannot point to in a packet does not count.
You crimp a straight-through cable, test it, and watch link lights when it connects a PC to a switch. Then you set an interface address and a VLAN on lab routers and switches — gear in the room, not a diagram only.
A server is a machine offering a service: addresses, names, or files. You bring up a lab service, point a client at it, and confirm the client received an address and resolved a name.
A task before the next lab
Pick one website you are allowed to open from the lab PC. Write four lines: how the PC got its address, which DNS name it asked for, which gateway should forward the traffic, and what you would check first if the page did not load. We review that note with you before you touch VLAN configuration.
A /24 holds 254 hosts. Two small rooms do not each need that. VLSM gives each room a mask that matches its size. This plan is the one we ask you to calculate, then build.
Sales, about 50 PCs
62 usable addresses (.1–.62). Broadcast .63. Gateway .1.
Accounts, about 20 PCs
30 usable addresses (.65–.94). Broadcast .95. Gateway .65.
Fifty hosts need six host bits (2⁶ − 2 = 62), so a /26. Twenty hosts need five host bits (2⁵ − 2 = 30), so a /27. The second block starts at .64 because the first block occupies .0 through .63. You write network, first, last and broadcast before you configure the router.
A lab PC on the sales VLAN boots with no address. In Wireshark you see a DHCP discover, then an offer, a request and an acknowledgement. The PC now holds 172.16.20.20.
The PC asks DNS for the lab file server’s name. You note the query and the answer. If the name fails and the IP works, the fault is DNS, not the cable.
A ping to the accounts gateway, 172.16.20.65, fails. You check three things: the PC’s VLAN, the switch port’s VLAN, and whether the router has a path between .0/26 and .64/27.
Four lines: the address DHCP gave, the DNS result, which of the three checks was wrong, and the change that made the ping succeed. That note is the lab, not a screenshot with no sentence.
An honest limit: this course makes you accurate on a lab LAN — addressing, VLANs, a static path, DNS, DHCP and a capture you can explain. Large provider networks, data-centre fabrics and senior design work need years after this.
Three changes are already in the work. In class you still count the hosts yourself, including when an assistant drafted the first split.
Office networks and cloud networks still use addresses, masks, routes, DNS and filters. The screen changed. The questions — which network is this, and who can reach it — did not.
You can ask an assistant for a subnet split or a capture summary. It will mis-count hosts, invent a VLAN, or skip the packet that shows the failure. The check is still yours.
Templates push VLAN and address settings quickly. When a PC cannot reach a server, someone still has to read the capture and the route table and say which hop stopped.
Where an assistant still fails a network plan
The skill that stays valuable
Reading. You can say which address, which VLAN and which packet explain the failure. Consoles and templates change. That explanation is what a teammate still needs.
Computer networking is shifting onto cloud consoles and configuration templates, while addresses, routes, DNS and packet reading stay the same. Assistants can draft a subnet plan and still mis-count hosts. CEC trains you in Ahmedabad to calculate the plan and confirm it on lab gear and a capture.
About 80% of our training is practical. Our 25+ full-time corporate trainers check the plan, the link lights and the capture note — not a recited definition of the OSI model.
School learners of any grade start with counseling. After 12th anyone can apply, from any stream. We place you on the hardware bench when you can follow an address plan, and on foundations first when that plan is still new.
You make a straight-through cable, test every pair, label it, and connect a PC to a switch. Link lights are the first proof. A pretty diagram with a dead cable is not.
You create two VLANs, put access ports in them, give the router an address on each, and add the path between them. Then you ping across and keep the config notes.
You record DHCP and DNS on that same lab, circle the packets that prove the address and the name, and write the one-line fault if something fails.
You may ask for a first subnet split. You then count the hosts yourself and reject any mask that does not fit the room.
Trainers send back a plan or a capture note that skips the gateway, the VLAN, or the reason the ping failed. You leave with a corrected IP plan and a marked capture.
When you want the security path next, it continues in our Cyber Security & Ethical Hacking with AI course. Counseling decides the order.
Nishant Yadav
Hardware Networking · CEC Nikol · 3+ years
Cyber Security, Server Administration
At Computer Education And Cybernetics (CEC) in Ahmedabad, networking training means crimping and testing a cable, configuring VLANs and a route on lab switches and routers, calculating a VLSM plan, and marking a Wireshark capture of DHCP and DNS. Mentors review the notes. Labs are arranged at Maninagar, Nikol and Vatva. Visiting is optional.
Employers ask you to explain a fault. We help you show the plan and the capture, then we stay with you for the job search.
How we stay with you
More detail on placement support at CEC.
You can specialise later. You cannot skip the part where a name, a port and a route decide whether anything else works.
An alert is easier to trust when you can see the DNS lookup, the connection, and the address it came from. Cyber security practice at CEC builds on this, which is why we ask security learners to be comfortable with TCP/IP before they hunt for faults.
An app that “cannot connect” is often a wrong port, a DNS name that does not resolve, or a request waiting on a host that is up but unreachable. Developers who can read that failure fix it faster than developers who only restart the app.
Counseling is available at Maninagar, Nikol and Vatva, or by call, WhatsApp or email from anywhere. Visiting is optional.
~2 minutes from Maninagar Railway Station
2nd floor, Gopal Tower, Computer Education And Cybernetics, near Maninagar Railway Station Road, Maninagar, Ahmedabad, Gujarat 380008+91 75740 10176Near / opposite New DMart, Nikol (Satyam Plaza)
S -25/26, D-mart, Satyam Plaza, Raspan Cross Rd, opp. Suketu Residency, near Nikol, Ankur Chokadi, New India Colony, Nikol, Ahmedabad, Gujarat 382350+91 91049 37871Near Vatva Lake Garden; opposite Kashiben Hospital
1st Floor, Computer Education And Cybernetics, Opposite Kashiben Hospital Beside Khodiayar Vav, Near Vatva Lake Garden, Vinzol Crossing Rd, Deriya Para, Vatva, Ahmedabad, Gujarat 382440+91 91571 90839If you are choosing between networking, security and development, bring that question to counseling. We will say which lab to start with.
Your PC gets an address, usually from DHCP, then asks DNS to turn a name into an IP. A switch delivers frames inside one VLAN. A router forwards packets to another subnet. TCP/IP is the suite those steps use; the OSI model is the map you use to say which step failed. At Computer Education And Cybernetics (CEC) you watch this on a lab capture, not only on a slide.
Variable length subnet masking means each piece of a network can have its own mask. A room of 50 PCs needs a /26 (62 usable hosts). A room of 20 needs only a /27 (30 usable). Giving both a /24 wastes addresses and makes the plan harder to read. You calculate network, first host, last host and broadcast before you type anything on a router.
You crimp and test a straight-through cable, connect it, and confirm link lights. You create two VLANs, assign access ports, set router addresses, and prove a PC in one subnet can reach the other. The output is a working bench plus the notes that explain it.
Yes, on lab traffic you generate. You find the DHCP exchange that assigned an address and the DNS query that resolved a name. You write what those packets prove. A capture you cannot explain is not finished.
Yes, if you want the later security labs to make sense. Alerts, scans and logins all sit on addresses, ports and packets. Counseling can start you here and then move you into the cyber security course, or combine the two when you already have the basics.
Developers need enough to explain a failed connection: the name, the port, the address and the timeout. You do not have to choose a network-engineer job to use that. People aiming at support, security or development all start from the same labs.
Yes. After 12th anyone can apply, from any stream. If IP addresses are new, counseling starts with how a PC gets an address before VLANs and routing. School learners of any grade begin with counseling.
Cloud consoles and configuration templates changed the screen, not the questions: which network, which route, which name. Assistants can draft a subnet plan or a capture summary and still mis-count hosts or skip the packet that shows the fault. Counting and reading stay valuable either way.
You build a cable, configure a lab switch and router, calculate a VLSM plan, and mark a Wireshark capture. A trainer sends the note back if the gateway, the VLAN or the fault is missing. Counseling at Maninagar, Nikol or Vatva — or by phone — decides where you start. About 80% of training time is practical work.
This is the citywide networking course for learners after 12th, college students and career changers. The BCA page maps the same kind of labs to a BCA timetable. If you are in BCA, read that page too and bring both to counseling.
Networking labs are arranged through our three Ahmedabad centres — Maninagar, Nikol and Vatva. Counseling is also by call, WhatsApp or email on +91 75740 10176 or info@cecyours.org. Visiting is optional.
Tell us whether you are heading toward support, security or development. We will start you on the lab that matches — cables and addresses first.