[Uwimana Jean Lambert]

hello every one

[Uwimana Jean Lambert]

hello every one

[Uwimana Jean Lambert]

Thanks

[Uwimana Jean Lambert]

this question is somehow challenging

[Uwimana Jean Lambert]

Need Help Verifying NDP Threat Mappings to Host, Router, or Both
================================================

Hi everyone,

I’m working on a network security exercise about IPv6 Neighbor Discovery Protocol (NDP) threats and I’m having trouble with a specific drag-and-drop question. I need to match each NDP threat to the device type it affects: Hosts, Routers, or Both.

The threats are:

• Replay attacks

• Malicious Router on the link

• Attack against DAD (Duplicate Address Detection)

• Attack against MAC address resolution

• Spoofed Redirect Message

Could someone please clarify the correct mapping? Any help would be appreciated. Thanks

[Uwimana Jean Lambert]

welcome

[Uwimana Jean Lambert]

hello

same as here

thanks

[Uwimana Jean Lambert]

my opinion : BGP’s core vulnerability is its trust-based model. It’s like a postal system where anyone can write any return address on a envelope, and the mail carriers will believe them.

[Uwimana Jean Lambert]

hello Shekhan

[Uwimana Jean Lambert]

• The ISP assigns each customer an IPv6 address that is derived from their own public IPv4 address.

• The customer’s router encapsulates IPv6 packets inside IPv4 packets and sends them over the ISP’s IPv4 network.

• These packets are routed to a 6rd relay router at the ISP, which decapsulates them and forwards the native IPv6 traffic to the IPv6 internet.

[Uwimana Jean Lambert]

That’s a great question. Tunneling is a technique used in networking to encapsulate one type of network packet within another. It allows the transmission of packets of one protocol (such as IPv6) through a network that only supports another protocol (such as IPv4). Tunneling is often used to solve compatibility issues between networks or to securely transmit data across a public or untrusted network

[Uwimana Jean Lambert]

thanks for the feature

[Uwimana Jean Lambert]

[Uwimana Jean Lambert]

[Uwimana Jean Lambert]

me too i am stacked with this issue

[Uwimana Jean Lambert]

Emmanuel You are on the right track, but on my view let me clarify the structure of IPv6 link-local addresses:

Correct prefix: Link-local addresses actually use fe80::/64 for the network portion, not /10 at the individual address level.

The breakdown is:

<ul type=”disc”>

[Uwimana Jean Lambert]

which of these two rules do you think provides more benefit in practice? For me, the zero compression (::) makes the biggest difference when dealing with typical IPv6 addresses that often have long zero blocks.

[Uwimana Jean Lambert]

Hello everyone 👋,

I was practicing how to shorten IPv6 addresses and worked on this example:
2001:0db8:0000:0000:0000:ff00:0042:0029

After removing leading zeros and replacing consecutive zero blocks with ::, I got 2001:db8::ff00:42:29.

Can someone please confirm if this is the correct shortened form? And are there any common mistakes to watch out for when using the double colon (::) rule?

Thanks in advance! 🙏

[Uwimana Jean Lambert]

Given IPv6:
2001:0db8:0000:0000:0000:ff00:0042:0029

Step 1: Remove leading zeros in each block

<ul type=”disc”>

[Uwimana Jean Lambert]

Dear Monica You have clearly captured the core aspects of IPv6: mainly, the extended 128-bit address and the introduction of address types, such as unicast, multicast, and anycast. I would add that one of the key features of IPv6 is that it does not require NAT, thus providing true end-to-end connectivity, which increases performance and simplifies the communication between devices.

Interesting how IPv6’s auto-configuration, stateless address auto-configuration, and the inherent IPsec support make the networks more secure and scalable for the future internet; definitely a big leap from IPv4.