This study guide is intended to provide those pursuing the CCNA certification with a framework of what concepts need to be studied. This is not a comprehensive document containing all the secrets of the CCNP nor is it a “braindump” of questions and answers.
I sincerely hope that this document provides some assistance and clarity in your studies.
This study guide is intended to provide those pursuing the CCNA certification with a framework of what concepts need to be studied. This is not a comprehensive document containing all the secrets of the CCNP nor is it a “braindump” of questions and answers.
I sincerely hope that this document provides some assistance and clarity in your studies.
IPv4 (Internet Protocol Version 4). This silde will give u all information about IPv4.
Hope so you like it Freinds.
and
Sorry if i can fulfill ur wish in the given IPv4 Presentation.
This presentation gives a brief description about IP Address (Internet protocol address), Classes of IPv4. And also included, what is IPv4 and what is IPv6.
Overview of IPv6 protocol along with various transition scenarios for the migration from IPv4 to IPv6
IPv6 is the current and future Internet Protocol standard. As anticipated, IPv4 addresses became exhausted around 2012.
The IP address scarcity is the main driver for IPv6 protocol adoption.
IPv6 defines a much larger address space that should be sufficient for the foreseeable future, even taking into account Internet of Things scenarios with zillions of small devices connected to the Internet.
IPv6 is, however, much more than simply an expansion of the address space. IPv6 defines a clean address architecture with globally aggregatable addresses thus reducing routing table sizes in Internet routers.
IPv6 extension headers provide a standard mechanism for stacking protocols such as IP, IPSec, routing headers and upper layer headers such as TCP.
ICMP (Internet Control Message Protocol) is already defined for IPv4. ICMP was totally revamped for IPv6 and as ICMPv6 provides common functions like IP address and prefix assignment.
Lack of business drivers for migrating to IPv6 is responsible for sluggish adoption of IPv6 in carrier and enterprise networks.
Numerous transition mechanisms were developed to ease the transition from IPv4 to IPv6. Many of these mechanisms are complex and difficult to administer.
The transition mechanisms can be coarsely classified into dual-stack, tunneling and translation mechanisms.
CCNA ppt designed on project remote connectivity using frame relay, and many more... best for project purpose. anyone want project will also contact me..
IPv4 (Internet Protocol Version 4). This silde will give u all information about IPv4.
Hope so you like it Freinds.
and
Sorry if i can fulfill ur wish in the given IPv4 Presentation.
This presentation gives a brief description about IP Address (Internet protocol address), Classes of IPv4. And also included, what is IPv4 and what is IPv6.
Overview of IPv6 protocol along with various transition scenarios for the migration from IPv4 to IPv6
IPv6 is the current and future Internet Protocol standard. As anticipated, IPv4 addresses became exhausted around 2012.
The IP address scarcity is the main driver for IPv6 protocol adoption.
IPv6 defines a much larger address space that should be sufficient for the foreseeable future, even taking into account Internet of Things scenarios with zillions of small devices connected to the Internet.
IPv6 is, however, much more than simply an expansion of the address space. IPv6 defines a clean address architecture with globally aggregatable addresses thus reducing routing table sizes in Internet routers.
IPv6 extension headers provide a standard mechanism for stacking protocols such as IP, IPSec, routing headers and upper layer headers such as TCP.
ICMP (Internet Control Message Protocol) is already defined for IPv4. ICMP was totally revamped for IPv6 and as ICMPv6 provides common functions like IP address and prefix assignment.
Lack of business drivers for migrating to IPv6 is responsible for sluggish adoption of IPv6 in carrier and enterprise networks.
Numerous transition mechanisms were developed to ease the transition from IPv4 to IPv6. Many of these mechanisms are complex and difficult to administer.
The transition mechanisms can be coarsely classified into dual-stack, tunneling and translation mechanisms.
CCNA ppt designed on project remote connectivity using frame relay, and many more... best for project purpose. anyone want project will also contact me..
IPv6 is short for "Internet Protocol Version 6". IPv6 is the "next generation" protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 ("IPv4").
This manual will show you how to prepare an effective IPv6 addressing plan. In making that plan, you will need to make a number of important choices. Please think carefully about these choices to ensure that the addressing plan will meet the requirements of your organisation. The manual will provide suggestions to help you to make the right choices.
IPv6 Autoconfig full process from initial configuration of IPV6 Node. Refreshment of IPv6 Addresses using RA or DHCPv6. How to keep your home config everywhere you go and only logout when you want to, not when you move to a new access point.
10 IP VERSION SIX (6) WEEK TEN notes.pptxJoshuaAnnan5
IPV6 addressing solution was announced in the mid 1990s (RFC 2460) and was task in solving IPv4’s shortcomings
NB: Version 5 was already assigned to another developing protocol, this is the reason for the jump from version 4 to 6.
Although both versions function similarly, version 4 and version 6 use different types of packet header formatting and addressing lengths. Meanwhile IPV6 header are more efficient and greatly simplified compared to IPV4 header information . This helps to reduce processing overhead during transmission.
Larger address space:
The main limitations with IPv4 are the imposed address space limitations and eventual complete loss of addressing capability. IPv6 was designed to overcome IPv4’s 32-bit limitations by introducing much larger 128-bit addresses and providing an address pool that is virtually inexhaustible.
Stateless autoconfiguration:
A feature used to issue and generate an IP address without the need for a Dynamic Host Configuration Protocol
(DHCP) server:
• Routers send router advertisements (RAs) to network hosts containing the first half, or first 64 bits, of the 128-bit network address.
• The second half of the address is generated exclusively by the host and is known as the interface identifier. The interface identifier uses its own MAC address, or it may use a randomly generated number.
This allows the host to keep hardware addresses hidden for security reasons and helps an administrator mitigate security risks.
More efficient packet headers: IPv6 uses a simpler header design than IPv4. The enhanced design allows routers to analyze and forward packets faster. Fewer header fields must be read, and header checksums are completely discarded in IPv6. More efficient packet headers improve network performance and save valuable router resources
Changes in multicast operation: Support for multicasting in IPv6 is now mandatory instead of optional, as with IPv4. The multicasting capabilities in IPv6 completely replace the broadcasting functionality found in IPv4. IPv6 replaces broadcasting with an “all-host” multicasting group.
Increased security: Another optional feature found in IPv4, IP Security (IPsec) measures are now considered mandatory and implemented natively in IPv6.
What all this numbers translate into is, flexibility of assigning different functions on the network, without facing address exhaustion. It also allows for an improved network design and troubleshooting efficiency.
The hexadecimal address look like
Components of Computer Networks
In this tutorial, we will cover the components of Computer Networks.
A Computer Network basically comprises multiple computers that are interconnected to each other in order to share information and other resources. Multiple computers are connected either with the help of cables or wireless media.
So basically with the help of a computer network two or more devices are connected in order to share a nearly limitless range of information and services whic
the TCP/IP protocol suite involves several methods that enables communication of which IP addressing is one of those pertinent subjects that must be considered if communication must be successful.
IP Address is a unique identification given to Host, network device, server for data communication. IP
Address stand for Internet Protocol address, it is an addressing scheme used to identify a system on a
network. It is a unique address that certain electronic devices currently use to communicate with each
other on a network using internet protocol.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
4. INFT3007
IPv6 Address Space
128-bit address space
2128 possible addresses
340,282,366,920,938,463,463,374,607,431,768,2
11, 456 addresses (3.4 x 1038 or 340 undecillion)
6.65 x 1023 addresses for every square meter
of the Earth’s surface
128 bits to allow flexibility in creating a multi-
level, hierarchical, routing infrastructure
5. INFT3007
IPv6 Syntax
IPv6 address in binary form
0010000000000001000011011011100000000000000000000010111100111011
0000001010101010000000001111111111111110001010001001110001011010
Divided along 16-bit boundaries
0010000000000001 0000110110111000 0000000000000000 0010111100111011
0000001010101010 0000000011111111 1111111000101000 1001110001011010
Each 16-bit block is converted to hexadecimal
and delimited with colons
2001:0DB8:0000:2F3B:02AA:00FF:FE28:9C5A
Suppress leading zeros within each block
2001:DB8:0:2F3B:2AA:FF:FE28:9C5A
7. INFT3007
IPv6 notation
IPv6 uses hexadecimal rather than decimal, because
it is easier to convert between hexadecimal and
binary than it is to convert between decimal and
binary.
With IPv4, decimal is used to make the IPv4
addresses more palatable for humans
IPv6 addresses are so large that there is no attempt
to make them palatable to most humans.
Configuration of typical end systems is automated,
and end users will almost always use names
rather than IPv6 addresses.
8. INFT3007
Compressing Zeros
A single contiguous sequence of 16-bit blocks set to
0 can be compressed to “::” (double-colon)
Example:
FE80:0:0:0:2AA:FF:FE9A:4CA2 becomes
FE80::2AA:FF:FE9A:4CA2
FF02:0:0:0:0:0:0:2 becomes FF02::2
Cannot use zero compression to include part of a
16-bit block
FF02:30:0:0:0:0:0:5 does not become FF02:3::5, but
FF02:30::5
9. INFT3007
Compressing Zeros (contd.)
Can only use :: only once in IPv6 address
Otherwise, we cannot determine the original address
To determine how many 0 blocks are represented by
the ::, you can count the number of blocks in the
compressed address and subtract this number from
8.
For example, in the address FF02::2, there are two blocks
(the “FF02” block and the “2” block). The number of blocks
expressed by the :: is 6 (8 – 2).
10. INFT3007
IPv6 Prefixes
Typical IPv6 host is composed of a 64-bit subnet
prefix and a 64-bit interface identifier
A 50-50 split between subnet space and interface space).
IPv6 prefixes express routes, address spaces, or
address ranges
IPv6 always uses address/prefix-length notation
Similar to CIDR notation
Examples
2001:DB8:0:2F3B::/64 for a subnet prefix
2001:DB8:3F::/48 for a route prefix
12. INFT3007
Types of IPv6 Addresses
Unicast
Address of a single interface within a scope
Delivery to single interface
Multicast
Address of a set of interfaces
Delivery to all interfaces in the set
Anycast
Address of a set of interfaces
Delivery to a single interface in the set
No more broadcast addresses similar to IPv4
13. INFT3007
Types of Unicast Addresses
Global addresses
Link-local addresses
Unique local addresses
Special addresses
Compatibility addresses
14. INFT3007
Global unicast addresses
IPv6 global addresses are equivalent to public
IPv4 addresses.
They are globally routable and reachable on
the IPv6 Internet
The scope of a global address is the entire
IPv6 Internet.
Structure
Interface ID
64 bits
Subnet ID
45 bits
001 Global Routing Prefix
16 bits
15. INFT3007
Global unicast addresses
(contd.)
Fixed portion – 001
Global Routing Prefix - indicates the
global routing prefix for a specific
organization’s site.
The combination of the three fixed bits and
the 45-bit Global Routing Prefix is used to
create a 48-bit site prefix, which is
assigned to an individual site of an
organization
16. INFT3007
Global unicast addresses
(contd.)
Subnet ID - Used within an organization’s
site to identify subnets within its site.
The organization’s site can use these 16 bits
within its site to create 65,536 subnets or multiple
levels of addressing hierarchy and an efficient
routing infrastructure
Interface ID - indicates the interface on a
specific subnet within the site.
The interface ID in IPv6 is equivalent to the node
ID or host ID in IPv4.
17. INFT3007
Link-local addresses
Address scope is a single link
Equivalent to APIPA IPv4 addresses
FE80::/64 prefix
Used for:
Single subnet, routerless configurations
Neighbor Discovery processes
An IPv6 router never forwards link-local traffic
beyond the link
Interface ID
64 bits
1111 1110 1000 0000 . . . 0000
64 bits
18. INFT3007
Zone IDs for link-local
addresses
Link local addresses are not unique
(scope is a single link)
Therefore, it is possible for the
following:
HostA
Link 1 Link 2
NIC1 NIC2
HostA has two network interface cards connected to two different links.
Now it is possible for the same link-local address to exists in the two different
links. How can we distinguish between the different link-local addresses? Ans:
Zone ID
19. INFT3007
Zone IDs for link-local
addresses (contd.)
Zone ID is used to identify a specific link for link-local
addresses
Zone ID is set to the interface index of the sending
interface
Example:
ping fe80::2b0:d0ff:fee9:4143%3
Use the following to display the interface index:
Ipconfig
netsh interface ipv6 show interface
Get-NetIPInterface-AddressFamily IPv6 in Powershell
Zone ID
20. INFT3007
Unique Local Addresses
To provide a type of address that is
private to an organization and not
routable on the IPv6 Internet, yet
unique across all the sites of the
organization, unique local IPv6 unicast
address can be defined.
21. INFT3007
Unique Local Addresses
(contd.)
Structure
Prefix: FD00::/8
The Global ID identifies a specific site
within an organization and is set to a
randomly derived 40-bit value
1111 110 Interface ID
7 bits 64 bits
Global ID
40 bits
Subnet ID
16 bits
L
22. INFT3007
Unique Local Addresses
(contd.)
Organizations will not advertise their unique
local address prefixes outside of their
organizations or create DNS entries with
unique local addresses in the Internet DNS.
Organizations filter at their Internet
boundaries to prevent all unique local-
addressed traffic from being forwarded.
Because they have a global scope, unique
local addresses do not need a zone ID.
23. INFT3007
Unique Local Addresses
(contd.)
The global address and unique local address share
the same structure beyond the first 48 bits of the
address.
In both addresses, the 16-bit Subnet ID field identifies a
subnet within an organization.
Because of this, you can create a subnetted routing
infrastructure that is used for both local and global
addresses
Although the subnet identifier is the same for both
prefixes, routes for both prefixes must still be
propagated throughout the routing infrastructure so
that addresses based on both prefixes are reachable
24. INFT3007
Special Addresses
Unspecified Address
0:0:0:0:0:0:0:0 or ::
Similar to 0.0.0.0 in IPv4
Loopback Address
0:0:0:0:0:0:0:1 or ::1
Similar to 127.0.0.1 in IPv4
25. INFT3007
Compatible Addresses
To aid in the transition from IPv4 to IPv6 and the
coexistence of both types of hosts, the following
addresses are defined:
IPv4-compatible address
0:0:0:0:0:0:w.x.y.z or ::w.x.y.z
IPv4-mapped address
0:0:0:0:0:FFFF:w.x.y.z or ::FFFF:w.x.y.z
6to4 address
2002:WWXX:YYZZ:Subnet ID:Interface ID
ISATAP address
64-bit prefix:0:5EFE:w.x.y.z or 64-bit prefix:200:5EFE:w.x.y.z
Teredo address
Prefix of 2001::/32
27. INFT3007
Multicast Address
Starts with FF
Flags – indicate flags set in multicast address
Scope - indicates the scope of the IPv6 network for
which the multicast traffic is intended tobe delivered.
Defined multicast addresses
FF02::1 (Link-local scope all-nodes address)
FF02::2 (Link-local scope all-routers address)
1111 1111 Group ID
8 bits 112 bits
Flags
4 bits
Scope
4 bits
28. INFT3007
Solicited-Node Address
In IPv4, in order to find out the MAC address for a
specific IPv4 address, a broadcast is sent via ARP
which disturbs all nodes in the network segment.
To avoid this, IPv6 uses the Neighbor Solicitation
message to perform link-layer address resolution.
Instead of using the local-link scope all-nodes
multicast address as the Neighbor Solicitation
message destination, which would disturb all IPv6
nodes on the local link, the solicited-node multicast
address is used.
29. INFT3007
Solicited-Node Address
(contd.)
The solicited-node multicast address is constructed
from the prefix FF02::1:FF00:0/104 and the last 24
bits (6 hexadecimal digits) of a unicast IPv6 address.
Interface ID
64 bits
Unicast prefix
64 bits
FF02:
24 bits
:1:FF0:0:0:0
Unicast
address
Solicited-
Node
Multicast
address
30. INFT3007
Solicited-Node Address
(contd.)
Example
For example, Node A’s link-local address is
FE80::2AA:FF:FE28:9C5A, the corresponding
solicited-node multicast address is
FF02::1:FF28:9C5A
Node B on the local link must resolve Node A’s
link-local address FE80::2AA:FF:FE28:9C5A to its
corresponding link-layer address.
Node B sends a Neighbor Solicitation message to the
solicited-node multicast address of FF02::1:FF28:9C5A.
Because Node A is listening on this multicast address, it
processes the Neighbor Solicitation message and sends a
unicast Neighbor Advertisement message in reply.
31. INFT3007
Solicited-Node Address
(contd.)
The result of using the solicited-node multicast
address is that link-layer address resolutions, a
common occurrence on a link, are not using a
mechanism that disturbs all network nodes.
By using the solicited-node address, very few nodes
are disturbed during address resolution. In practice,
because of the relationship between the IPv6
interface ID and the solicited-node address, the
solicited node address acts as a pseudo-unicast
address for very efficient address resolution.
32. INFT3007
When sending IPv6 multicast packets on an Ethernet
link, the corresponding destination MAC address is
0x33-33-mm-mm-mm-mm, where mm-mm-mm-mm
is a direct mapping of the last 32 bits (8 hexadecimal
digits) of the IPv6 multicast address.
Mapping IPv6 Multicast
Addresses to Ethernet Addresses
34. INFT3007
Mapping IPv6 Multicast Addresses to
Ethernet Addresses (contd.)
Ethernet network adapters maintain a table of
interesting destination MAC addresses.
If an Ethernet frame with an interesting destination MAC
address is received, it is passed to upper layers for
additional processing.
By default, this table contains the MAC-level broadcast
address (0xFF-FF-FFFF- FF-FF) and the unicast MAC address
assigned to the adapter.
To facilitate efficient delivery of multicast traffic,
additional multicast destination addresses can be
added or removed from the table.
For every multicast address being listened to by the host,
there is a corresponding entry in the table of interesting
MAC addresses.
35. INFT3007
Mapping IPv6 Multicast Addresses to
Ethernet Addresses (contd.)
For example, an IPv6 host with the Ethernet MAC
address of 00-AA-00-3F-2A-1C (link-local address of
FE80::2AA:FF:FE3F:2A1C) adds the following
multicast MAC addresses to the table of interesting
destination MAC addresses on the Ethernet adapter:
The address of 33-33-00-00-00-01, which corresponds to the
link-local scope all-nodes multicast address of FF02::1 (fully
expressed as FF02:0000:0000:0000:0000:0000:0000:0001).
The address of 33-33-FF-3F-2A-1C, which corresponds to
the solicited-node address of FF02::1:FF3F:2A1C. Remember
that the solicited-node address is the prefix
FF02::1:FF00:0/104 and the last 24 bits of the unicast IPv6
address.
37. INFT3007
Anycast Addresses
An anycast address is assigned to multiple
interfaces.
Packets addressed to an anycast address are
forwarded by the routing infrastructure to the
nearest interface to which the anycast
address is assigned.
To facilitate delivery, the routing
infrastructure must be aware of the interfaces
that have anycast addresses assigned to
them and their distance in terms of routing
metrics.
38. INFT3007
Anycast Addresses (contd.)
Anycast addresses are used only as
destination addresses and are assigned only
to routers
Anycast addresses are assigned out of the
unicast address space, and the scope of an
anycast address is the scope of the type of
unicast address from which the anycast
address is assigned
It is not possible to determine whether a
given destination unicast address is also an
anycast address.
39. INFT3007
Subnet-Router Anycast
Address
The Subnet-Router anycast address is created
from the subnet prefix for a given interface.
When the Subnet-Router anycast address is
constructed, the bits in the subnet prefix are
fixed at their appropriate values and the
remaining bits are set to 0
Subnet Prefix 000 . . . 000
n bits 128 - n bits
40. INFT3007
Subnet-Router Anycast
Address (contd.)
All router interfaces attached to a
subnet are assigned the Subnet-Router
anycast address for that subnet.
The Subnet-Router anycast address is
used to communicate with the nearest
router connected to a specified subnet.
42. INFT3007
IPv6 Addresses for a Host
An IPv4 host with a single network
adapter typically has a single IPv4
address assigned to that adapter.
However, an IPv6 host usually has
multiple IPv6 addresses assigned to
each adapter.
43. INFT3007
IPv6 Addresses for a Host
(contd.)
The interfaces on a typical IPv6 host
are assigned the following unicast
addresses:
A link-local address for each interface
Additional unicast addresses for each
interface (which could be one or multiple
unique local or global addresses)
The loopback address (::1) for the
loopback interface
44. INFT3007
IPv6 Addresses for a Host
(contd.)
Additionally, each interface on an IPv6
host is listening for traffic on the
following multicast addresses:
The interface-local scope all-nodes
multicast address (FF01::1)
The link-local scope all-nodes multicast
address (FF02::1)
The solicited-node address for each unicast
address assigned
The multicast addresses of joined groups