# IPv6 ISATAP (Intra Site Automatic Tunnel Addressing Protocol)

**URL:** https://forum.networklessons.com/t/ipv6-isatap-intra-site-automatic-tunnel-addressing-protocol/2662
**Category:** Lessons Discussion
**Created:** [January 5, 2018, 1:51pm UTC](https://forum.networklessons.com/t/ipv6-isatap-intra-site-automatic-tunnel-addressing-protocol/2662 "2018-01-05T13:51:23Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![lagapidis](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/lagapidis/32/4949_2.png) [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [August 21, 2019, 4:19am UTC](https://forum.networklessons.com/t/ipv6-isatap-intra-site-automatic-tunnel-addressing-protocol/2662/3 "2019-08-21T04:19:36Z")

</div>

Hello Giovanni

According to Cisco documentation, when configuring ISATAP:

> The IPv6 tunnel interface must be configured with a modified EUI-64 address  
> because the last 32 bits in the interface identifier are constructed using the IPv4 tunnel source address.

If you were to specify the address fully, the ISATAP operation would not function.

Also, when you configure `tunnel mode ipv6ip isatap` on the headend, there is no need to specify the mode in which the tunnel will be functioning on the client. On the client, you also set `ipv6 address autoconfig`, which means that it will obtain the IPv6 address (and the mode of the tunnel) from the headend.

I hope this has been helpful!

Laz

---

_[View the full topic](https://forum.networklessons.com/t/ipv6-isatap-intra-site-automatic-tunnel-addressing-protocol/2662)._