Skip to main content

Posts

Featured Post

5G Network Simulation in NS3 using mmWave | NS3 Tutorial 2024

5G Network Simulation in NS3 Using mmWave This post shows the installation of ns3mmwave in Ubuntu 24.04 and simulates 5G networks in ns3. Installation of #5g networks in ns3 namely mmWave for #ns3 #TSP #pradeepkumar #pradeepkumarts Prerequisites: 1. Ubuntu OS (I used Ubuntu 24.04) 2. mmWave software from github To know the complete process, follow the video given below Open a new Terminal and try these commands $ sudo apt update $ sudo apt install g++ python3 cmake ninja-build git gir1.2-goocanvas-2.0 python3-gi python3-gi-cairo python3-pygraphviz gir1.2-gtk-3.0 ipython3 tcpdump wireshark libsqlite3-dev qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools openmpi-bin openmpi-common openmpi-doc libopenmpi-dev doxygen graphviz imagemagick python3-sphinx dia imagemagick texlive dvipng latexmk texlive-extra-utils texlive-latex-extra texlive-font-utils libeigen3-dev gsl-bin libgsl-dev libgslcblas0 libxml2 libxml2-dev libgtk-3-dev lxc-utils lxc-templates vtun uml-utilities ebtables bridg...
Post a Comment
Read more
Recent posts

Simulation of a large enterprise network with RIP and generate routing trace metrics | NS3 Project 7

Simulate a large enterprise network (40 nodes) with RIP and generate routing trace metrics Prompt : Prompt (Claude): You are an expert in ns-3 simulation and network protocol analysis. i need a complete, error-free, fully functional NS-3 C++ program for the following experiment: Title: RIP routing overhead analysis in a large enterprise network Objective: to simulate a large enterprise network (minimum 40 nodes) using the rip routing protocol and analyze routing overhead using trace metrics. strict requirements (non-negotiable): Output requirements: The program must generate: netanim animation file: filename: rip_overhead.xml must show all nodes clearly arranged (grid layout) must show packet flow trace file: ascii trace (.tr file) enable using asciitracehelper data files for graphs (.dat): overhead.dat for routing overhead vs time txrate.dat for packet transmission rate vs time   Network topology:   minimum 40 nodes (pre...
Post a Comment
Read more

Comparison of Routing Information Protocol vs. static routing using NS3 | NS Project 6

AIM: To simulate and compare Static Routing and RIP in a 6-router network under link failure using NS-3. NETWORK TOPOLOGY: The simulation consists of 6 routers connected in a mesh topology. Multiple paths exist between the source (Node 0) and the destination (Node 5). A link between routers is intentionally broken during simulation to test routing behaviour. Network Design WORKING: Static Routing: Routes are manually configured. When link fails, packets are dropped and communication stops. RIP Routing: Dynamic routing protocol. Automatically updates routes and finds alternate path after link failure. NetAnim: The above animation represents a 6-router network topology where data packets are transmitted from the source node (Node 0) to the destination node (Node 5). The arrows indicate the direction of packet flow through intermediate routers. Initially, packets follow the shortest available path based on RIP routing. During the simulation, a link disturbance i...
Post a Comment
Read more

Simulation and Analysis of the Effect of Explicit Congestion Notification (ECN) on TCP Reno using NS3 | NS3 Project 5

1. Aim To simulate a dumbbell network topology using NS-3 and analyse the effect of Explicit Congestion Notification (ECN) on TCP Reno by comparing congestion window behaviour, throughput, end-to-end delay, and packet loss rate under congested network conditions with ECN enabled and disabled. 2. Introduction Congestion control is one of the fundamental challenges in modern computer networks. When multiple flows compete for a limited-bandwidth bottleneck link, packets accumulate in router queues and are eventually dropped, leading to degraded throughput and increased latency. Traditional TCP mechanisms such as TCP Reno rely on packet loss as an implicit congestion signal — a reactive approach that wastes bandwidth already consumed in transit. Explicit Congestion Notification (ECN), standardised in RFC 3168, addresses this limitation by allowing routers to signal congestion proactively before the queue overflows. Instead of dropping a packet, a congestion-experiencing r...
Post a Comment
Read more