Q. Create An Html5 Page Which Will Display Names of Indian cricket team with all the different text styles(bold, italic and underlined) and its combinations on separate lines. State style of each line in its text.
HTML Code
<HTML>
<HEAD><TITLE>Indian Cricket Team</TITLE></HEAD>
<BODY>
<BIG><CENTER>Names of Players of Indian Cricket Team</BIG><BR>
<font size="4" face="arial" color="red"><B>Sachine Tendulker</B></font><BR>
<font size="4" face="arial" color="blue"><I>M.S.Dhoni</I></font><BR>
<font size="4" face="arial" color="yellow"><U>Virat Kholi</U></font><BR>
<font size="4" face="arial" color="orange"><B>Suresh Raina</B></font><BR>
<font size="4" face="arial" color="green"><I>Rohit Sharma</I></font><BR>
</BODY>
</HTML>
Output:
5 Comments
Credible Information. The Article over here is very much impressive and contains good and valuable information. At Stumpsandbails you can know who will win match today and today cricket match prediction visit stumps and bails. Also, We aim to provide 100% accurate & free cricket match prediction tips and cricket live score.
ReplyDeletePRACTICAL 8
ReplyDeletePACKET CAPTURE AND ANALYSIS USING WIRESHARK
WHAT YOU WILL COMPLETE
Capture network traffic on your Windows laptop, generate test traffic, and use Wireshark display filters to inspect Ethernet, IP, TCP, UDP, ICMP, HTTP and DNS packets.
2. INSTALL WIRESHARK
1. Open the official download page: https://www.wireshark.org/download.html
2. Download the Windows x64 Installer for a 64-bit Windows laptop.
3. Open the downloaded installer from Downloads.
4. Follow the installation wizard and keep the standard components selected.
5. When asked about Npcap, allow it to be installed. Npcap is required for live packet capture.
6. Finish the installation and open Wireshark.
3. SELECT THE CORRECT NETWORK INTERFACE
1. Open Wireshark.
2. On the start screen, find the available network interfaces.
3. Choose the interface currently carrying your internet connection. It may be named Wi-Fi or Ethernet.
4. If unsure, look for the interface whose activity graph is moving while you browse the internet.
5. Double-click that interface to begin capture, or select it and click the shark-fin Start button.
4. GENERATE NETWORK TRAFFIC WHILE CAPTURING
Do not close Wireshark. Open Windows Command Prompt:
1. Press Windows+R.
2. Type cmd and press Enter.
3. Run:
ping 8.8.8.8
This generates ICMP traffic. If your network blocks this test, ping your router's gateway address instead.
4. Run:
nslookup example.com
This generates DNS request and response traffic.
5. Open a web browser and visit an HTTP website if available. The journal asks you to generate HTTP traffic. Some websites automatically redirect HTTP to HTTPS; if that happens, you may see TLS rather than readable HTTP. Do not assume every website will show HTTP packets.
5. STOP THE CAPTURE
1. Return to Wireshark.
2. Click the red Stop button.
3. The captured packets remain in the packet list for analysis.
4. Save the capture using File > Save As if you need to keep it. Use a name such as Practical_8_Capture.pcapng.
6. USE THESE DISPLAY FILTERS
Click the display filter bar near the top, type one filter and press Enter. Clear the filter before trying another.
eth
Shows Ethernet frames. Select a packet and expand Ethernet II to view source and destination MAC addresses.
ip
Shows IPv4 packets. Expand Internet Protocol Version 4 to view source IP, destination IP, TTL and protocol.
tcp
Shows TCP packets. Expand Transmission Control Protocol to view ports, sequence numbers and flags such as SYN and ACK.
udp
Shows UDP packets. Expand User Datagram Protocol to view source port, destination port and length.
icmp
Shows ping request and reply packets. Look for Echo request and Echo reply.
http
Shows packets Wireshark identifies as HTTP. This filter may show no results if the website used HTTPS instead.
dns
Shows DNS query and response packets.
More filters from the journal:
ip.addr == 192.168.1.2
Shows IP packets where that address is the source or destination. Replace the address with an address actually used on your network.
tcp.port == 80
Shows TCP traffic using port 80, commonly used for HTTP.
dns.qry.name == "example.com"
Shows DNS queries for example.com.
7. HOW TO READ A PACKET
1. Click one packet in the top packet list.
2. In the middle details pane, expand Ethernet II to inspect MAC addresses.
3. Expand Internet Protocol to inspect source and destination IP addresses.
4. Expand TCP, UDP, ICMP or DNS to inspect protocol-specific information.
5. The bottom pane shows the packet bytes.
RESULT
Live network traffic was captured and examined using Wireshark. Display filters were used to identify protocol packets and inspect their headers.
QUICK VIVA
Q: What is Wireshark? A: A tool used to capture and analyse network packets.
Q: What is a display filter? A: A filter that controls which captured packets are shown.
Q: What does ICMP show? A: Network control messages such as ping requests and replies.
Q: What does DNS do? A: Resolves domain names to IP addresses.
Q: What is the purpose of Npcap? A: It lets Wireshark capture packets from network interfaces on Windows.
PRACTICAL 9
ReplyDeleteBASIC NETWORK SECURITY: ACL, FIREWALL RULES AND SSH/TELNET
Build two LANs connected by one router. First block one PC using a standard ACL. Then allow only HTTP traffic to a server using an extended ACL. Finally configure SSH and test that Telnet is not allowed.
1. DEVICES YOU NEED
- One Cisco 1941 router (R1).
- Two Cisco 2960 switches (Switch-LAN1 and Switch-LAN2).
- Two PCs in LAN1: PC-BLOCKED and PC-ALLOWED.
- One Server-PT in LAN2.
- Five Copper Straight-Through cables to connect the router, switches, PCs and server.
3. PLACE THE DEVICES
1. Open Packet Tracer > File > New.
2. Place one 1941 router.
3. Place two 2960 switches.
4. Place two PCs and one Server-PT.
5. Arrange PC-BLOCKED and PC-ALLOWED near Switch-LAN1; put the server near Switch-LAN2; put R1 between the switches.
4. CONNECT THE DEVICES
Choose Connections > Copper Straight-Through.
PC-BLOCKED FastEthernet0 to Switch-LAN1 Fa0/1.
PC-ALLOWED FastEthernet0 to Switch-LAN1 Fa0/2.
Switch-LAN1 Fa0/24 to R1 GigabitEthernet0/0.
R1 GigabitEthernet0/1 to Switch-LAN2 Fa0/24.
Server FastEthernet0 to Switch-LAN2 Fa0/1.
Wait for green links.
5. CONFIGURE PC AND SERVER ADDRESSES
PC-BLOCKED > Desktop > IP Configuration > Static:
IP 192.168.1.5 | Mask 255.255.255.0 | Gateway 192.168.1.1
PC-ALLOWED:
IP 192.168.1.6 | Mask 255.255.255.0 | Gateway 192.168.1.1
Server-PT:
IP 192.168.2.10 | Mask 255.255.255.0 | Gateway 192.168.2.1
On Server-PT, open Services > HTTP and turn HTTP On. This lets the browser test the HTTP rule.
6. CONFIGURE ROUTER INTERFACES
Click R1 > CLI. Type no if asked about the initial configuration dialog, then press Enter. Enter:
enable
configure terminal
hostname R1
interface gigabitEthernet 0/0
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface gigabitEthernet 0/1
ip address 192.168.2.1 255.255.255.0
no shutdown
exit
end
7. TEST BASIC CONNECTIVITY BEFORE ACLs
From PC-ALLOWED > Desktop > Command Prompt, run:
ping 192.168.2.10
The server should reply before the ACL rules are added. If not, fix the IP addresses and cables first.
8. STANDARD ACL - BLOCK PC 192.168.1.5 FROM LAN2
On R1 CLI, enter:
enable
configure terminal
access-list 10 deny host 192.168.1.5
access-list 10 permit any
interface gigabitEthernet 0/1
ip access-group 10 out
end
9. EXTENDED ACL - ALLOW ONLY HTTP FROM LAN1 TO THE SERVER
On R1, enter:
configure terminal
ip access-list extended FIREWALL
permit tcp 192.168.1.0 0.0.0.255 host 192.168.2.10 eq 80
deny ip any any
exit
interface gigabitEthernet 0/0
ip access-group FIREWALL in
end
TEST EXTENDED ACL:
1. From PC-ALLOWED, open Desktop > Web Browser.
2. Enter http://192.168.2.10 and click Go. The server's HTTP page should open.
3. From PC-ALLOWED Command Prompt, run ping 192.168.2.10. It should fail because ICMP is not allowed by this HTTP-only ACL.
4. On R1, run show access-lists.
The standard ACL remains applied on G0/1. Therefore PC-BLOCKED is still denied from reaching LAN2.
CONFIGURE SSH ON R1
The HTTP-only ACL on G0/0 blocks non-HTTP traffic arriving from LAN1, including SSH. Temporarily remove that extended ACL from the interface for the SSH test:
configure terminal
interface gigabitEthernet 0/0
no ip access-group FIREWALL in
exit
Now configure SSH:
hostname R1
enable secret Network@123
ip domain-name college.local
username admin secret Admin@123
ip ssh version 2
crypto key generate rsa modulus 1024
line console 0
password Cisco@123
login
exit
line vty 0 4
password Cisco@123
login local
transport input ssh
end
If the router asks for an RSA key size, enter 1024.
SSH AND TELNET
From PC-ALLOWED > Desktop > Command Prompt, run:
ssh -l admin 192.168.1.1
When asked for the password, enter:
Admin@123
The password may not appear while typing. That is normal.
Then try:
telnet 192.168.1.1
Telnet should fail because the router VTY lines accept SSH only.
SECURITY SETTINGS
On R1:
show access-lists
show ip interface brief
show running-config
PRACTICAL 10
ReplyDeleteMINI SKILL DEVELOPMENT PROJECT: SECURE ENTERPRISE NETWORK (COLLEGE)
Build a small college network with Admin, Faculty, Computer Lab and Server Room VLANs. Configure router-on-a-stick, DHCP, DNS, an ACL that blocks Lab-to-Admin traffic and SSH management.
1. DEVICES YOU NEED
- One Cisco 1941 router (R1).
- Five Cisco 2960 switches: one CORE switch and one access switch for each of Admin, Faculty, Lab and Server Room.
- Four PCs: one Admin PC, one Faculty PC, one Lab PC and one Server Room PC (optional for testing the server VLAN).
- One Server-PT for DHCP and DNS.
- Ten Copper Straight-Through cables for the connections listed below.
3. PLACE THE DEVICES
1. Open Packet Tracer > File > New.
2. Place one Cisco 1941 router and name it R1.
3. Place five Cisco 2960 switches. Name them CORE, ADMIN-SW, FACULTY-SW, LAB-SW and SERVER-SW.
4. Place one PC near each department switch: ADMIN-PC, FACULTY-PC, LAB-PC and SERVER-PC.
5. Place one Server-PT near SERVER-SW.
6. Keep CORE in the middle, R1 above CORE, and the four department switches around CORE.
4. CONNECT THE DEVICES
Use Copper Straight-Through for all links in this topology.
1. R1 GigabitEthernet0/0 to CORE Fa0/1.
2. CORE Fa0/2 to ADMIN-SW Fa0/24.
3. CORE Fa0/3 to FACULTY-SW Fa0/24.
4. CORE Fa0/4 to LAB-SW Fa0/24.
5. CORE Fa0/5 to SERVER-SW Fa0/24.
6. ADMIN-PC FastEthernet0 to ADMIN-SW Fa0/1.
7. FACULTY-PC FastEthernet0 to FACULTY-SW Fa0/1.
8. LAB-PC FastEthernet0 to LAB-SW Fa0/1.
9. SERVER-PC FastEthernet0 to SERVER-SW Fa0/1.
10. Server-PT FastEthernet0 to SERVER-SW Fa0/2.
Wait for the links to become green. The router-to-core and core-to-department links will be configured as trunks.
5. CREATE THE FOUR VLANs ON EACH SWITCH
Do this on CORE, ADMIN-SW, FACULTY-SW, LAB-SW and SERVER-SW. Click the switch > CLI. Enter:
enable
configure terminal
vlan 10
name Admin
exit
vlan 20
name Faculty
exit
vlan 30
name Computer_Lab
exit
vlan 40
name Server_Room
exit
end
6. CONFIGURE TRUNK PORTS ON CORE
On CORE switch CLI, enter:
enable
configure terminal
interface range fastEthernet 0/1-5
switchport mode trunk
end
7. CONFIGURE TRUNK PORTS ON THE FOUR DEPARTMENT SWITCHES
On ADMIN-SW CLI:
enable
configure terminal
interface fastEthernet 0/24
switchport mode trunk
exit
interface fastEthernet 0/1
switchport mode access
switchport access vlan 10
end
On FACULTY-SW CLI:
enable
configure terminal
interface fastEthernet 0/24
switchport mode trunk
exit
interface fastEthernet 0/1
switchport mode access
switchport access vlan 20
end
On LAB-SW CLI:
enable
configure terminal
interface fastEthernet 0/24
switchport mode trunk
exit
interface fastEthernet 0/1
switchport mode access
switchport access vlan 30
end
On SERVER-SW CLI:
enable
configure terminal
interface fastEthernet 0/24
switchport mode trunk
exit
interface range fastEthernet 0/1-2
switchport mode access
switchport access vlan 40
end
8. CONFIGURE ROUTER-ON-A-STICK
Click R1 > CLI. Enter:
enable
configure terminal
hostname R1
interface gigabitEthernet 0/0
no shutdown
exit
interface gigabitEthernet 0/0.10
encapsulation dot1Q 10
ip address 192.168.10.1 255.255.255.0
ip helper-address 192.168.40.10
exit
interface gigabitEthernet 0/0.20
encapsulation dot1Q 20
ip address 192.168.20.1 255.255.255.0
ip helper-address 192.168.40.10
exit
interface gigabitEthernet 0/0.30
encapsulation dot1Q 30
ip address 192.168.30.1 255.255.255.0
ip helper-address 192.168.40.10
exit
interface gigabitEthernet 0/0.40
encapsulation dot1Q 40
ip address 192.168.40.1 255.255.255.0
exit
end
9. SET A STATIC IP ON THE SERVER
Click Server-PT > Desktop > IP Configuration > Static.
IP Address: 192.168.40.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.40.1
DNS Server: 192.168.40.10
10
ReplyDelete10. CONFIGURE DHCP POOLS ON THE SERVER
Click Server-PT > Services > DHCP. Turn DHCP On. Add these four pools. Use the Add/Save button after entering each pool.
Pool ADMIN:
Pool Name: ADMIN
Default Gateway: 192.168.10.1
DNS Server: 192.168.40.10
Start IP: 192.168.10.100
Subnet Mask: 255.255.255.0
Maximum Users: 50
Pool FACULTY:
Pool Name: FACULTY
Default Gateway: 192.168.20.1
DNS Server: 192.168.40.10
Start IP: 192.168.20.100
Subnet Mask: 255.255.255.0
Maximum Users: 50
Pool LAB:
Pool Name: LAB
Default Gateway: 192.168.30.1
DNS Server: 192.168.40.10
Start IP: 192.168.30.100
Subnet Mask: 255.255.255.0
Maximum Users: 50
Pool SERVER-ROOM:
Pool Name: SERVER-ROOM
Default Gateway: 192.168.40.1
DNS Server: 192.168.40.10
Start IP: 192.168.40.100
Subnet Mask: 255.255.255.0
Maximum Users: 50
11. CONFIGURE DNS
On Server-PT > Services > DNS:
1. Set DNS service to On.
2. Add an A Record:
Name: www.college.com
Type: A Record
Address: 192.168.40.10
3. Click Add.
12. SET THE PCs TO DHCP
On ADMIN-PC, FACULTY-PC, LAB-PC and SERVER-PC:
1. Click the PC > Desktop > IP Configuration.
2. Select DHCP.
3. Wait for an IP address to appear.
4. Check that the address matches that PC's VLAN network:
Admin: 192.168.10.x
Faculty: 192.168.20.x
Lab: 192.168.30.x
Server Room: 192.168.40.x
The DNS server should be 192.168.40.10.
13. CONFIGURE THE LAB-TO-ADMIN ACL
On R1 CLI, enter:
enable
configure terminal
ip access-list extended LAB-POLICY
deny ip 192.168.30.0 0.0.0.255 192.168.10.0 0.0.0.255
permit ip any any
exit
interface gigabitEthernet 0/0.30
ip access-group LAB-POLICY in
end
This blocks traffic from the Computer Lab VLAN (30) to the Admin VLAN (10). The permit ip any any line allows other traffic that is not denied by this ACL.
14. CONFIGURE SSH ON THE ROUTER
On R1 CLI, enter:
configure terminal
hostname R1
enable secret Network@123
ip domain-name college.local
username admin secret Admin@123
ip ssh version 2
crypto key generate rsa modulus 1024
line console 0
password Cisco@123
login
exit
line vty 0 4
password Cisco@123
login local
transport input ssh
end
If asked for key size, enter 1024. The lab username and password are sample credentials; do not reuse them for real systems.
15. CONFIGURE SSH ON THE SWITCHES
Do the following on CORE, ADMIN-SW, FACULTY-SW, LAB-SW and SERVER-SW. Use a different management IP on each switch. All management addresses are in VLAN 40.
CORE management address: 192.168.40.2
ADMIN-SW: 192.168.40.3
FACULTY-SW: 192.168.40.4
LAB-SW: 192.168.40.5
SERVER-SW: 192.168.40.6
On each switch, replace SWITCH-IP in the commands with that switch's address:
enable
configure terminal
interface vlan 40
ip address SWITCH-IP 255.255.255.0
no shutdown
exit
ip default-gateway 192.168.40.1
hostname COLLEGE-SW
enable secret Network@123
ip domain-name college.local
username admin secret Admin@123
crypto key generate rsa modulus 1024
ip ssh version 2
line console 0
password Cisco@123
login
exit
line vty 0 4
password Cisco@123
login local
transport input ssh
end
16. TEST THE COMPLETE NETWORK
A. Check DHCP on each PC:
Open its Command Prompt and run:
ipconfig
Confirm the IP address belongs to that PC's VLAN.
B. Check DNS from a PC:
nslookup www.college.com
C. Check server connectivity from Admin and Faculty PCs:
ping 192.168.40.10
These should be allowed by the LAB-POLICY because it only blocks traffic from VLAN 30 to VLAN 10.
D. Check the ACL:
From LAB-PC, run:
ping 192.168.10.100
E. Check VLANs and routes:
On a switch:
show vlan brief
show interfaces trunk
On R1:
show ip interface brief
show ip route
show access-lists
F. Test SSH from an Admin or Faculty PC:
ssh -l admin 192.168.40.1
Enter the sample password Admin@123. (The router's VLAN 40 subinterface address is 192.168.40.1.)
To test SSH to the CORE switch, run:
ssh -l admin 192.168.40.2
Enter Admin@123. The other switches can be tested using their management IPs .3, .4, .5 and .6.
RESULT
A college network with Admin, Faculty, Computer Lab and Server Room VLANs was configured. Inter-VLAN routing, DHCP, DNS, the Lab-to-Admin ACL and SSH management were tested.