Link Local Address on BGP

I recently start to have IPv6 BGP Peer, at first I try to block all the link local address at my interface incoming ACL but after a while I notice that there has many match log on the deny link local address. I want to know is it a correct thing to not block link local address even the link is upstream link to my ISP?
My IPv6 BGP is formed by using Global IPv6 address!

Do you actually have a business need to block Link Local addresses ? This should not be done as the IPv6 control plane relies on link local addresses. e.g. each time you do a Neighbour Discovery on Ethernet. Link Local are also non routeable so they cannot traverse the router (assuming that is the intent of the ACL)
I would recommend against blocking Link Local addresses in ACLs however if you must do this you should be selective about the ones you allow through. e.g.
permit link_local_bgp_peer
deny all link_local
permit global uinicast
Though just beware that even then, if the upstream link local address changes, as in the upstream router swaps or replaces its interface then the ACL will have no effect as the Link Local address would have changed.

Similar Messages

  • IPv6 link-local address on point-to-point interface

    Hello,
    I'm a little bit confused. I know that there are two ways of assigning an IPv6 link-local address on interface. We can add it manually, or it is by default created automatically using modified EUI-64. But how is this address made when there is no MAC address on point-to-point link?
    Thanks.
    Martin

    Hello,
    sorry but I don't think that these reasons are reasonable. Why do they need to remember these addresses when are they used only on a link with internal processes? They cannot be used for management purposes, so I would say that it is easier for me to configure one loopback with global address at each router which would be easy to remember, announce it to IGP and it can be used for management, so as for BGP..and I don't need to care about all link local addresses I'm using in my network, which might contain hundreds of links..

  • Getting error while accessing a webpage by using link local address of ipv6

    Hello,
    I want to access my login.jsp by using ipv6 address.
    when i am accessing my web page by using loop back or localhost6(like the following) it is working.
    http://[::1]:8080/test/login.jsp //for loopback
    http://localhost6:8080/test/login.jsp
    But when i am accessing my webpage by using link local address as following i am not getting my web page.
    http://[fe80::201:6cff:fe0f:d7ae%eth0]:8080/test
    or
    http://[fe80::201:6cff:fe0f:d7ae]:8080/test
    For the above case is there any solutions????

    Whatever i have mentioned these are correct. My ipv6 address is also correct.From browser only i am accessing.>
    Not a Java issue, then. Your problem I'm afraid.
    But how do you know they're correct? Given that one of them isn't working, I'd triple check it if I were you.

  • IPv6 Link-local addresses: EUI-64 or Static?

    Hello Everyone.
    What is the best practice? Configuring a static link-local address on the interface, or letting the router pick an eui-64 one?
    From a dynamic routing process point of view, does it really matter which type of link local address is used in a production network?
    I know that static addresses are more convinient for humans. But what about the IOS?
    Any other considerations?
    Thank you all.

    Hello,
    I would say that as you already know when you use a routing protocol on IPv6 the neighbor will always be the link local address from the interface from the neighbor itself,
    So I would say why to use Dynamic( Cause it's easy,it's scalable as it's based on a unique value)
    Why to use Static ( So you can create your own system to identify the neighbor, I have read that for security purposes you can use a mechanism that will create random EUI-64 based on a hash but as this is only for Link-Local address I would say it does not apply here)
    Regards

  • Why use link-local addressing for HSRP in IPv6?

    I have scoured the internet for an answer to this question, and am no closer to having it answered.  Am hoping someone here can help!
    * Why do we use link-local (or autoconfig) addresses for the standby IP in FHRPs?  If you are forwarding a packet towards a link-local destination address, wouldn't the source address then have to be a link-local address from the same prefix, which according to scope, should not route beyond the local link?  How do you route an IP packet that has a link-local address for a source address?
    Any insight would be much appreciated.
    Thank you in advance.

    Dougles,
    next hop is used for reaching "gateway" that know where to send packets farther (read it as "next hop to the destination")... routing in IPvX is hopping between nodes where every hop is closer to destination... This is theory behind.
    So as machine that needs to send packet to "not directly connected destination" you only need to send packet to gateway leading to this destination...
    so you need to send packet so, that "gateway" will recieve this packet and gateway then send this packet farther... it is not important what IP address this gateway has.
    On ethernet you only need to know MAC address of this gateway and you send packet (with your source IPv6 address and intended destination IPv6 address) encapsulated with "destination MAC address" of gateway. When gateway recieve ethernet frame, and this frame is for it (destination MAC address is its MAC address), the gateway will proceed IP header (inside IP header the gateway see IT is not final destination for this packet, and gateway will route this packet).
    So configuring IP address as next hop is just "hleper for simpler administration".. MAC address of gateway is important. In IPv4 address resolution protocol (ARP) is used to automaticly get MAC address of gateway if you configure next hop as IP address. In IPv6 there is neighbor discovery protocol(ND) used for this task.
    conclusion: you can use link local address as nex hop address for addresses from any scope ... next hop is just next hop, it is not used just for the same scope communication.
    And question is... if we need just information about MAC address of gateway, why to ask using global address?
    We need to get MAC address... that is information important just "locally"... so to ask for local information, why not use link local address ?
    HSRP is the same case... really just need MAC address to send packets correctly.

  • It is possible ssh from a router to another, to its ipv6 link-local address?

    Hi 
    R1 and R2 are connected by serial links, with IPV6 address global unicast and link-local every link.
    I can do ping between them. When I do ping to link-local address next router, I need to specify outgoing interface, ping is succesful.
    However I can not do SSH v2 from a router to another to its link-local address. 
    OS R1 and R2: c2900-universalk9-mz.SPA.151-1.M4.bin 
    R1
    Serial0/3/0                [up/up]
        FE80::1
        2001:1200:CAFE:BEBA::1
    R2
    Serial0/3/0                [up/up]
        FE80::2
        2001:1200:CAFE:BEBA::2
    Thank you

    Hi Cesar, 
    you should be able to use "%source_itf" at the end of the target IPv6 LL address. 
    Example with telnet : 
    R1#ping FE80::302              
    Output Interface: Ethernet0/0                 
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80::302, timeout is 2 seconds:
    Packet sent with a source address of FE80::301%Ethernet0/0
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
    R1#telnet FE80::302%Ethernet0/0
    Trying FE80::302 ... Open
    Password required, but none set
    [Connection to FE80::302%Ethernet0/0 closed by foreign host]
    R1#

  • SG300 cant change the Link Local address for an IPv6 interface

    There seems to be no apparent way to change the Link Local address for an IPv6 interface
    If I create more than one interface they all appear to have the same Link Local address

    Never mind, I figured it out
    By adding a Link Local address to an interface, it overides the existing one on the interface

  • DFSDiag TestDCs Warning - Site Association by IPv6 Link Local Addresses?!?

    Why is DFSDiag
    using IPv6 Link Local Addresses (fe80::/64) for /TestDCs Site Association test?
    C:\Users\Administrator\Documents>dfsdiag /testdcs
    DFSDIAG_INFO - APPL - Client Domain found to be BRREX.
    Starting TestDcs ....
    Validating DFS Service ....
    Validating DFS Service on FINCH.
    DFSDIAG_INFO - APPL - DFS Service on FINCH is OK.
    Validating SiteCostedReferrals Key ....
    Validating SiteCostedReferrals in FINCH.
    DFSDIAG_INFO - APPL - SYSVOL/NETLOGON referrals are site costed.
    Validating Registry Entries ....
    BRREX has a single domain controller.
    Validating SiteAssociation ....
    Validating SiteAssociation of FINCH in every DC.
    DFSDIAG_WARNING - APPL - SiteName from IP - fe80::a402:d343:baa3:5f5e%12 of FINCH in DC - FINCH is NULL while in ADSite it is GoGrid,
    this can lead to different referral ordering.
    DFSDIAG_WARNING - APPL - SiteName from IP - fe80::7473:f9f8:c5c3:17e6%13 of FINCH in DC - FINCH is NULL while in ADSite it is GoGrid,
    this can lead to different referral ordering.
    Finished TestDcs.
    C:\Users\Administrator\Documents>
    DFSDiag problems with IPv6 Link Local addresses has occurred
    three (3) other times.
    My best guess is either AD DS or DFS don't like running on server routing IPv6 via
    6in4 tunnel.
    IPCONFIG follows:
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : finch
    Primary Dns Suffix . . . . . . . : brrex.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : brrex.com
    grid-store.brrex.com
    grid-node.brrex.com
    Ethernet adapter Private:
    Connection-specific DNS Suffix . : grid-store.brrex.com
    Description . . . . . . . . . . . : SUSE Network Driver for Windows #2
    Physical Address. . . . . . . . . : 00-16-6E-00-0B-1E
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:470:841e:1::100(Preferred)
    Link-local IPv6 Address . . . . . : fe80::a402:d343:baa3:5f5e%12(Preferred)
    IPv4 Address. . . . . . . . . . . : 10.113.0.40(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 2001:470:841e:1::100
    ::1
    10.113.0.40
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter Public:
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : SUSE Network Driver for Windows
    Physical Address. . . . . . . . . : 00-16-6E-00-0B-1D
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 173.1.67.212(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.240
    Default Gateway . . . . . . . . . : 173.1.67.209
    DNS Servers . . . . . . . . . . . : 173.1.67.212
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 9:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter IP6Tunnel:
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:470:1f04:53f::2(Preferred)
    Link-local IPv6 Address . . . . . : fe80::7473:f9f8:c5c3:17e6%13(Preferred)
    Default Gateway . . . . . . . . . : 2001:470:1f04:53f::1
    DNS Servers . . . . . . . . . . . : 173.1.67.212
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 12:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : isatap.grid-node.brrex.com
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Local Area Connection* 13:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : grid-store.brrex.com
    Description . . . . . . . . . . . : isatap.grid-store.brrex.com
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    ROUTE PRINT follows:
    ===========================================================================
    Interface List
    12 ...00 16 6e 00 0b 1e ...... SUSE Network Driver for Windows #2
    11 ...00 16 6e 00 0b 1d ...... SUSE Network Driver for Windows
    1 ........................... Software Loopback Interface 1
    10 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
    13 ...00 00 00 00 00 00 00 e0 Microsoft Direct Point-to-point Adapater
    14 ...00 00 00 00 00 00 00 e0 isatap.grid-node.brrex.com
    15 ...00 00 00 00 00 00 00 e0 isatap.grid-store.brrex.com
    ===========================================================================
    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 173.1.67.209 173.1.67.212 266
    10.0.0.0 255.0.0.0 10.113.0.1 10.113.0.40 11
    10.113.0.0 255.255.255.0 On-link 10.113.0.40 266
    10.113.0.40 255.255.255.255 On-link 10.113.0.40 266
    10.113.0.255 255.255.255.255 On-link 10.113.0.40 266
    127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
    127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
    127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    173.1.67.208 255.255.255.240 On-link 173.1.67.212 266
    173.1.67.212 255.255.255.255 On-link 173.1.67.212 266
    173.1.67.223 255.255.255.255 On-link 173.1.67.212 266
    224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
    224.0.0.0 240.0.0.0 On-link 10.113.0.40 266
    224.0.0.0 240.0.0.0 On-link 173.1.67.212 266
    255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    255.255.255.255 255.255.255.255 On-link 10.113.0.40 266
    255.255.255.255 255.255.255.255 On-link 173.1.67.212 266
    ===========================================================================
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    10.0.0.0 255.0.0.0 10.113.0.1 1
    0.0.0.0 0.0.0.0 173.1.67.209 Default
    ===========================================================================
    IPv6 Route Table
    ===========================================================================
    Active Routes:
    If Metric Network Destination Gateway
    13 266 ::/0 2001:470:1f04:53f::1
    1 306 ::1/128 On-link
    13 266 2001:470:1f04:53f::/64 On-link
    13 266 2001:470:1f04:53f::2/128 On-link
    12 266 2001:470:841e:1::/64 On-link
    12 266 2001:470:841e:1::100/128 On-link
    13 266 fe80::/64 On-link
    12 266 fe80::/64 On-link
    13 266 fe80::7473:f9f8:c5c3:17e6/128
    On-link
    12 266 fe80::a402:d343:baa3:5f5e/128
    On-link
    1 306 ff00::/8 On-link
    13 266 ff00::/8 On-link
    12 266 ff00::/8 On-link
    ===========================================================================
    Persistent Routes:
    If Metric Network Destination Gateway
    0 4294967295 ::/0 2001:470:1f04:53f::1
    ===========================================================================
    Thanks in advance!

    Did you solve this? I'm having the same problem.

  • Seeking clarification in IPv6 Link & Site local addresses please

    Hi All
    Just wondering if anybody with IPv6 knowledge can put me straight. I am currently studying for my CCNP (BSCI) and am just going over the IPv6 stuff again.
    Now I understand that for the CCNP I will likely just need to know the basic theory of IPv6, however I cannot get my head around the Link-Local and Site-Local addresses.
    Routing TCP/IP Vol 1 (Jeff Doyle) 2nd edition, page 54, has a table showing the high order bits of various IPv6 addresses and lists the following.
    Link-Local = 1111 1110 10 which equates to FE80::/10
    Site-Local = 1111 1110 11 which equates to FEC0::/10
    Now the part I can not get my head around is this.
    The first 10 high order bits equate to 2 1/2 (10 bits) nibbles, but for the Link-Local address to be FE80 would require 4 nibbles (16 bits) or
    1111 1110 1000 0000. Like wise with the Site-Local address of FEC0 which would be 1111 1110 1100 0000. This would mean that the prefix should be /16 if remaining 6 bits can not be turned on.
    So I am trying to understand what happens to the remaining 6 bits in these Local IPv6 addresses or to the IPv6 addresses from FE81 to FEBF and from FEC1 to FECF? Are they just ignored?
    If so it would appear that nothing was learned from what happened with the initial wasteful assignment of IPv4 addresses!!
    Can anybody put me out of my misery please :)
    Best Regards,
    Michael

    Hi Narayan
    Thank you for your post and the information contained within.
    When I went through IPv6 initially for my CCNP (BSCI) studies I understood that as the Link-Local and Site-Local addresses had a prefix of /10. I thought that once I kept the initial 10 bits of the address as specified in the RFC, I could change any and all of the other 118 bits in the address.
    However my study material (which now also includes "Routing TCP/IP Vol 1&2, by Jeff Doyle) also states that Link-Local addresses will always start with "FE80" and Site-Local addresses will always start with "FEC0". This accounts for the first 16 bits, which to me (as just a CCNA with knowledge of IPv4 only) meant that the Link-Local and Site-Local addresses should actually have a prefix of /16.
    After further investigation into IPv6 I am further confused as it appears that the Link and Site local addresses are derived by using the 48 bit MAC address of an interface, injecting "FFFE" between the OUI portion and the local portion and then inverting the 7th bit to reach the modified EUI-64 identifier.
    This in turn means that the Link and Site Local addresses would have a prefix of /64, as the actual addresses would start off with
    FE80:0000:0000:0000: or FE80::
    FEC0:0000:0000:0000: or FEC0::.
    Also while searching the web for more information I came across this site
    http://www.tcpipguide.com/free/t_IPv6SpecialAddressesReservedPrivateLinkLocalSiteLo-3.htm
    which suggests as you mentioned above that all addresses between FE80:: and FEBF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF can be Link-Local addresses and that all addresses between FEC0:: and FEFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF can be Site-Local addresses.
    I then read through RFC3513 (IPv6 Addressing Architecture) http://www.faqs.org/rfcs/rfc3513.html and can find no mention of these "ranges" for the Link-Local and Site-Local addresses. It seems to suggest in section 2.5.6 (and I am no expert at reading and understanding RFC's) the the Link-Local address has the first 10 bits of "1111111010" the next 54 bits set to "0" and the final 64 bits are the interface ID (modified EUI-64 ID). Again to me this suggests that the prefix should be /64
    However with the Site-Local address the first 10 bits are "1111111011" the next 54 bits are the "Subnet ID" and the final 64 bits are the interface ID (Modified EUI-64 ID) which again suggests to me a prefix of /64, but also that I can manipulate the middle 54 bits.
    I think the more I try to understand this the more I confuse myself. I know this is probably gone way outside what I am expected to know for my BSCI exam, but I just like to understand how things that I read in my studies are arrived at. I don't like just taking things on blind faith :)
    However I think after reading the RFC that I am also getting to hung up on the fact that the texts I am reading use a /10 prefix for these addresses. I understand the the Link-Local addresses are like the addresses Microsoft OS's use when they cannot get a DHCP addresses (169.254/16) and that Site-Local addresses are equivalent to RFC1918 private addresses.
    Therefore I can except that the Link-local addresses will always start FE80:0000:0000:0000: and I am assuming that the lowest Site-Local address will start with FEC0:0000:0000:0000 but can be anything up to FEFF:FFFF:FFFF:FFFF, which will define the subnet.
    Sorry for such a long post, but I see now why network administrators are not rushing to implement IPv6 :) I think it will take time to get my head around this.
    Again thank you for your input.
    Best Regards and Best Wishes for the 2008 and beyond,
    Michael

  • Can a hosts be in the same subnet yet not be link local (trouble with Bonjour) ?

    I'm trying to print through a D-Link DVA G3810 BN from the wireless side with a Macbook Pro to the wired side HP C6280 . Apparently mDNS (Bonjour} communicates with hosts that are link-local and on the same subnet ? Is there an assumption that hosts on the same subnet are link-local ? My testing suggests to me that connections from the wireless to the wired side of the D-Link are routed and the hosts are NOT link-local . It will only allow me to add hosts , regardless of being fixed or via DHCP , within the same address range and subnet . I found a statement that for hosts to be link-local , their communications cannot be routed (pass thru a router) . I can't see the HP printer in trying to set it up and always get the 'Network host is busy ; will retry in X seconds'  state if I do configure it as an IP type . I can't figureout a way around this issue with the hardware that I have to work with .

    Link-local addresses are usually the self assigned IP address that a device will set when a DHCP server cannot be found. These are the addresses with 169.254.x.x subnet.
    If the router is assigning IP addresses for your network, then they will usually have a different IP subnet, possibly 192.168.0 for D-Link. And this subnet would be for the wired and wireless connections. So it would be more a case of bridging the two network topolgies rather than routing them.
    The network host is busy message could be more to do with the driver and the IP protocol selected when creating the queue than the connection being broken between the Mac and printer. If you were to open Network Utility and select the Ping tab, enter the IP address of the HP and set the pings to 4, pressing the Ping button will soon show if there is a path through the wireless to the printer.
    If you get a response to the ping you could then open Safari and type the ip address as the URL. This would then connect to the internal web page of the printer and possibly let you enable an IP protocol like LPR so that you can use LPD on the Mac instead of Bonjour to connect to the printer.
    As for the driver, you could look at using a Gutenprint driver instead of the HP driver or the hpijs package to get past the limitations that some printer drivers have with network connections.

  • Link local ip

    What is the purpose for this link-local address?
    What causes it to show up? Is it because my printer is on my network and is connected in this way.
    I wondered, because I have never seen this before in my network security map under my computer. It shows my IP address, plus this link-local IP above it.
    And the only answers on the web state the function of it to be, communication with in a network between nodes.

    Do you mean that you receive the local link IPv6 fe80::25ce:dfd6:etc?
    No, I mean it is now showing up in my network security map, and it was not before, just the IP4 address showed before. Now it shows both.
    I thought it might be showing now that we bought a new wireless router (Asus RT N66R), or that we now have a new printer connected to the wireless network.
    And here is a screen shot of my network, and details.
    If you use Obtain an IPv6 address automatically, but you don’t have a DHCPv6 server, you will get the fe80:: address.
    I don`t understand what a DHCPv6 server is, or if I have one. What my wireless network consist of this; The cable internet modem-wireless router-and all that connects to the wireless router-5 computers-2 TV`s-2 phones-1 printer
    If your environment use IPv4, and then you don’t need to pay attention to the IPv6.
    You can disable the like the following screenshot.
    What environment uses IPv6?
    I read somewhere, that in networks home group uses ipv6, and if you turn off/leave homegroup, ipv6 address does not show up anymore on your network as shown in the first screen shot. When I check in
    network-homegroup-, it states, (If you leave homegroup, you wont be able to get to shared libraries or devices.)
    So I don`t think that the ipv6 address is showing in my network security map, unless it`s being used for something?
    Thanks Fangzhou
    P.S. who, where, and what internet provider gives you 10gbps???? that's fast! just wondering from your screen shot.

  • Route IGMP link-local groups

    There are two VLANs in network:
    VLAN 30: 192.168.1.0/24
    VLAN 40: 192.168.2.0/24
    A IGMP multicast group 224.0.0.251 is used for devices in both VLANs.
    I try to configure the router to enable the multicast routing, but it seems the router cannot join that multicast group:
    ip multicast-routing distributed
    3560g-client(config-if)#ip igmp join-group 224.0.0.251
    Illegal multicast group address
    So is there anyway to make that multicast group routable?
    Thank you.

    The multicast address, you are trying to join is a link-local multicast address and does not follow normal procedures of join. Any multicast address which belongs to 224.0.0.x is link-local address and few are reserved for protocols which runs over a link, like 224.0.0.9 is used for RIP and 224.0.0.10 is for EIGRP. and similarly 224.0.0.251 is used of mDNS. We will same error message for all these groups.
    R6_ASR6(config-if)#ip igmp join-group 224.0.0.9
    Illegal multicast group address
    R6_ASR6(config-if)#ip igmp join-group 224.0.0.10
    Illegal multicast group address
    R6_ASR6(config-if)#
    http://en.wikipedia.org/wiki/Multicast_address
    http://en.wikipedia.org/wiki/Multicast_DNS
    --- Please don't forget to rate helpful posts -----
    Regards,
    Akash

  • Link Local BGP peering between Cisco and Juniper (M-Series)

    Hi,
    has anybody successfully managed to get a working IPv6 session between a Cisco and a Juniper router using Link Local IPs?
    I got it working between two cisco routers and two Juniper Routers but not with the two different vendors.
    Configuration on the Juniper site:
       family inet6 {
           address FE80::1/64;
      protocols {
          bgp {
              group customer_ipv6 {
                  neighbor fe80::2 {
                      local-interface at-2/0/0.119;
                      peer-as 65300;
                      as-override;
    Configuration on the Cisco site:
    interface ATM0/0/0.1 point-to-point
    bandwidth 2033
    ip address 10.194.235.42 255.255.255.252
    ip access-group AL-SECURITY-WAN out
    ip mtu 1500
    ipv6 address FE80::2 link-local
    ipv6 enable
    bfd interval 999 min_rx 999 multiplier 15
    pvc 1/32
      vbr-nrt 2244 2244 1
      tx-ring-limit 3
      encapsulation aal5snap
    router bgp 65300
    bgp router-id 10.213.58.185
    bgp log-neighbor-changes
    no bgp default ipv4-unicast
    neighbor FE80::1%ATM0/0/0.1 remote-as 65300
    neighbor FE80::1%ATM0/0/0.1 version 4
    neighbor FE80::2%GigabitEthernet0/1 remote-as 65300
    neighbor FE80::2%GigabitEthernet0/1 version 4
    address-family ipv4
    exit-address-family
    address-family ipv6
      neighbor FE80::1%ATM0/0/0.1 activate
      neighbor FE80::1%ATM0/0/0.1 advertisement-interval 5
      neighbor FE80::1%ATM0/0/0.1 soft-reconfiguration inbound
      neighbor FE80::1%ATM0/0/0.1 route-map NH6 out
      neighbor FE80::2%GigabitEthernet0/1 activate
      neighbor FE80::2%GigabitEthernet0/1 advertisement-interval 5
      neighbor FE80::2%GigabitEthernet0/1 soft-reconfiguration inbound
      neighbor FE80::2%GigabitEthernet0/1 route-map NH6 out
    exit-address-family
    CE_HOSTNAME# show ip bgp ipv6 uni su
    BGP router identifier 10.213.58.185, local AS number 65300
    BGP table version is 7, main routing table version 7
    4 network entries using 656 bytes of memory
    4 path entries using 320 bytes of memory
    1/1 BGP path/bestpath attribute entries using 128 bytes of memory
    2 BGP AS-PATH entries using 48 bytes of memory
    2 BGP community entries using 48 bytes of memory
    0 BGP route-map cache entries using 0 bytes of memory
    0 BGP filter-list cache entries using 0 bytes of memory
    BGP using 1200 total bytes of memory
    BGP activity 34/12 prefixes, 38/12 paths, scan interval 60 secs
    Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    FE80::1%ATM0/0/0.1
                    4        65300       0       0        1    0    0 never    Idle
    FE80::2%GigabitEthernet0/1
                    4        65300      15      16        7    0    0 00:10:59        4
    CE_HOSTNAME#
    The console monitoring states the following:
    Nov 10 06:30:33.023 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 06:30:33.023 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 06:30:33.023 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    de-ipc-ulmdon-ce-02#
    Nov 10 06:30:33.023 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    The Cisco Router is running IOS 15.2, the Juniper Site JunOS 10.4
    Any Ideas how I can get this to work?
    Thanks in advance!

    Marcin,
    I updated the debugging log, the previous one was created using override-capability-neg on the neighbor (experimental).
    >>0) Do you see similar scenario for working session? (Between two Cisco routers)
    The working connection between two cisco routers doesn't show any output
    >>1) What verion of IOS are you running? Something failrly recent I hope?
    Show Version:
    Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.2(1)T1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2011 by Cisco Systems, Inc.
    Compiled Mon 19-Sep-11 16:24 by prod_rel_team
    ROM: System Bootstrap, Version 15.0(1r)M9, RELEASE SOFTWARE (fc1)
    CE_HOSTNAME uptime is 2 weeks, 5 days, 21 hours, 35 minutes
    System returned to ROM by reload at 18:43:21 MET(S) Fri Oct 21 2011
    System restarted at 18:44:50 MET(S) Fri Oct 21 2011
    System image file is "flash:c1900-universalk9-mz.SPA.152-1.T1.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    Cisco CISCO1941/K9 (revision 1.0) with 446464K/77824K bytes of memory.
    Processor board ID FCZ1504C0G8
    1 DSL controller
    2 Gigabit Ethernet interfaces
    1 ATM interface
    1 terminal line
    DRAM configuration is 64 bits wide with parity disabled.
    255K bytes of non-volatile configuration memory.
    250880K bytes of ATA System CompactFlash 0 (Read/Write)
    License Info:
    License UDI:
    Device#   PID                   SN
    *0        CISCO1941/K9          FCZ1504C0G8
    Technology Package License Information for Module:'c1900'
    Technology    Technology-package           Technology-package
                  Current       Type           Next reboot
    ipbase        ipbasek9      Permanent      ipbasek9
    security      None          None           None
    data          datak9        Permanent      datak9
    Configuration register is 0x2102
    >>2) Can we have some more info from Juniper side (logs/debugs).
    Sadly not. The Juniper Traceoptions don't show anything
    All I can offer you at this point is the neighbor show command:
    user@Juniper> show bgp neighbor fe80::2 instance vrf-test
    Peer: fe80::2 AS 65300         Local: unspecified AS 20570
      Type: External    State: Idle           Flags:
      Last State: NoState       Last Event: NoEvent
      Last Error: None
      Export: [ pol-standard-bgp-export ] Import: [ pol-standard-bgp-import ]
      Options:
      Options:
      Address families configured: inet6-unicast
      Path-attributes dropped:  128
      Holdtime: 90 Preference: 170
      Number of flaps: 0
      Trace options:  all
      Trace file: /var/log/bgp_ipv6_ll_20111110 size 131072 files 10
    user@Juniper> show bgp summary instance vrf-test
    Groups: 2 Peers: 2 Down peers: 1
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    vrf-2.inet.0          37         16          0          0          0          0
    vrf-.inet6.0           0          0          0          0          0          0
    vrf-24.mdt.0           0          0          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.194.235.42         65300       1149       1076       0       1     8:44:00 Establ
      vrf-test.inet.0: 6/7/7/0
    fe80::2               65300          0          0       0       0     9:38:32 Idle
    >>3)
    CE_HOSTNAME#
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) Keep alive timer fired.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) service keepalive IO request.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) Keep alive timer fired.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) service keepalive IO request.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:52.850 MET: BGP: 10.194.235.41 received KEEPALIVE, length (excl. header) 0
    CE_HOSTNAME#
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 active went from Idle to Active
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 open active, local address FE80::2
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Adding topology IPv6 Unicast:base
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send OPEN
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active went from Active to OpenSent
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active sending OPEN, version 4, my as: 65300, holdtime 180 seconds, ID AD53AB9
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 1, length (excl. header) 10
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive OPEN
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN, version 4, holdtime 90 seconds
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN w/ OPTION parameter len: 0
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from OpenSent to Closing
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send NOTIFICATION 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 3, length (excl. header) 2
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive NOTIFICATION 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active bad state change from Closing to Closing
    Nov 10 15:35:54.702 MET: -Traceback= 21B3370Cz 21B33C74z 21B34258z
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Multicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF delete stale NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF no stale paths state is NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active closing
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Session close and reset neighbor FE80::1%ATM0/0/0.1 topostate
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from Closing to Idle
    Nov 10 15:35:54.702 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    CE_HOSTNAME#CE_HOSTNAME#
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) Keep alive timer fired.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:49.574 MET: BGP: ses global 10.194.235.41 (0x2970EDA4:1) service keepalive IO request.
    Nov 10 15:35:49.574 MET: BGP: 10.194.235.41 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) Keep alive timer fired.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE requested (bgp_keepalive_timer_expired)
    Nov 10 15:35:50.598 MET: BGP: ses global FE80::2%GigabitEthernet0/1 (0x316FBDDC:1) service keepalive IO request.
    Nov 10 15:35:50.598 MET: BGP: FE80::2%GigabitEthernet0/1 KEEPALIVE write request serviced in BGP_IO
    CE_HOSTNAME#
    Nov 10 15:35:52.850 MET: BGP: 10.194.235.41 received KEEPALIVE, length (excl. header) 0
    CE_HOSTNAME#
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 active went from Idle to Active
    Nov 10 15:35:54.694 MET: BGP: FE80::1%ATM0/0/0.1 open active, local address FE80::2
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Adding topology IPv6 Unicast:base
    Nov 10 15:35:54.698 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send OPEN
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active went from Active to OpenSent
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active sending OPEN, version 4, my as: 65300, holdtime 180 seconds, ID AD53AB9
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.698 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active KEEPALIVE write request serviced in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active service 2 read request in BGP_IO
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 1, length (excl. header) 10
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive OPEN
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN, version 4, holdtime 90 seconds
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv OPEN w/ OPTION parameter len: 0
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from OpenSent to Closing
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: sent to neighbor FE80::1%ATM0/0/0.1 active 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Send NOTIFICATION 2/7 (unsupported/disjoint capability) 0 bytes
    Nov 10 15:35:54.702 MET: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from FE80::1%ATM0/0/0.1:
    FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 505A 005A 52D2 C023 00
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active rcv message type 3, length (excl. header) 2
    Nov 10 15:35:54.702 MET: %BGP-3-NOTIFICATION: received from neighbor FE80::1%ATM0/0/0.1 active 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Receive NOTIFICATION 2/5 (authentication failure) 0 bytes
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active bad state change from Closing to Closing
    Nov 10 15:35:54.702 MET: -Traceback= 21B3370Cz 21B33C74z 21B34258z
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv4 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl VPNv6 Unicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: tbl IPv4 Multicast:base Service reset requests
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF delete stale NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) NSF no stale paths state is NSF not active
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active closing
    Nov 10 15:35:54.702 MET: BGP: ses global FE80::1%ATM0/0/0.1 (0x296337B4:0) act Session close and reset neighbor FE80::1%ATM0/0/0.1 topostate
    Nov 10 15:35:54.702 MET: BGP: nbr_topo global FE80::1%ATM0/0/0.1 IPv6 Unicast:base (0x296337B4:0) Resetting ALL counters.
    Nov 10 15:35:54.702 MET: BGP: FE80::1%ATM0/0/0.1 active went from Closing to Idle
    Nov 10 15:35:54.702 MET: %BGP_SESSION-5-ADJCHANGE: neighbor FE80::1%ATM0/0/0.1 IPv6 Unicast topology base removed from session  BGP Notification sent
    CE_HOSTNAME#

  • Virtual Switch adapter getting link-local IP address (apipa)

    Hi Everyone,
    Not sure what I am doing wrong here.
    I have installed an Hyper-V 2012 R2 core server on a brand new Dell server.
    I then went to use Virtual Switch Manager via Hyper-V Manager to create a virtual switch adapter, selected external (I want to share my existing server NIC), allow management operating system to share this network adapter.
    Then I configured my virtual machine to use this.
    When I start the virtual machine I get a 169 type IP address, cannot ping gateway or host. The VM does not even get a proper IP using DHCP. DHCP is working fine from another physical server.
    When I check the hyperv core host and select 8 for  "Network Settings", I get:
    15    192.168.20.44   Broadcom NetXtreme Gigabit Ethernet #5
    22    169.254.101.167 Hyper-V Virtual Ethernet Adapter #2
    Why is hyperv creating a virtual adapter with an Apipa address which is not usable?
    I followed all the steps correctly, but it does not work.
    Can anyone point me into the right direction to solve this problem?
    Thanks and regards
    Ipnotech

    This is what IPCONFIG /ALL shows (There is a functonal DHCP server in place):
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : cmshyperv1
       Primary Dns Suffix  . . . . . . . : newcms.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : newcms.local
    Ethernet adapter vEthernet (Virtual Switch 1 ):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-62
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::6ca4:68e9:a171:65a7%25(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.101.167(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 855640823
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter NIC4:
       Connection-specific DNS Suffix  . : newcms.local
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #8
       Physical Address. . . . . . . . . : F8-BC-12-35-A2-8F
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5daf:241d:7e00:f758%20(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.20.147(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
       Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
       Default Gateway . . . . . . . . . : 192.168.20.1
       DHCP Server . . . . . . . . . . . : 192.168.20.5
       DHCPv6 IAID . . . . . . . . . . . : 351845394
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
       DNS Servers . . . . . . . . . . . : 192.168.20.5
       Primary WINS Server . . . . . . . : 192.168.20.5
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter NIC3:
       Connection-specific DNS Suffix  . : newcms.local
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #7
       Physical Address. . . . . . . . . : F8-BC-12-35-A2-8E
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::91ae:2c7d:ebf3:f71c%19(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.20.138(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
       Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
       Default Gateway . . . . . . . . . : 192.168.20.1
       DHCP Server . . . . . . . . . . . : 192.168.20.5
       DHCPv6 IAID . . . . . . . . . . . : 335068178
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
       DNS Servers . . . . . . . . . . . : 192.168.20.5
       Primary WINS Server . . . . . . . : 192.168.20.5
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter NIC2:
       Connection-specific DNS Suffix  . : newcms.local
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #6
       Physical Address. . . . . . . . . : F8-BC-12-35-A2-8D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::7cb8:c761:b73:2274%18(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.20.136(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
       Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
       Default Gateway . . . . . . . . . : 192.168.20.1
       DHCP Server . . . . . . . . . . . : 192.168.20.5
       DHCPv6 IAID . . . . . . . . . . . : 318290962
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
       DNS Servers . . . . . . . . . . . : 192.168.20.5
       Primary WINS Server . . . . . . . : 192.168.20.5
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter NIC1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #5
       Physical Address. . . . . . . . . : F8-BC-12-35-A2-8C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::3c95:1710:4969:d6d5%17(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.20.44(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.20.1
       DHCPv6 IAID . . . . . . . . . . . : 603503634
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
       DNS Servers . . . . . . . . . . . : 192.168.20.5
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter SLOT 2 Port 2:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #4
       Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-61
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter SLOT 2 Port 4:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #3
       Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-63
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter SLOT 2 Port 1:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
       Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-60
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.newcms.local:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : newcms.local
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{CBA3B939-0F6F-40F2-9F1A-4433D5B36865}:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{DA0EA386-57B7-4441-AB8F-1760F00FD0A6}:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

  • Link Local Unicast Addresses and Link Local Multicast Addresses

    I am trying to get a hold on Link Local Multicast addressing.  I know that Link Local Unicast Addressing is the equivalent of an APIPA address but can anyone tell me what Local Link Multicast addressing is used for and hopefully provide an example of
    it's use?  Beg your pardon if this is a stupid question.  Thanks.
    Michael T. Glenn

    Hi Michael,
    Obviously, this is not a stupid question.
    The link local multicast addresses are the equivalent of 224.0.0.0/24, which are reserved for the local subnet and are not forwarded by IP routers regardless of the Time to Live (TTL) in the IP header.
    They are used for routing protocol or other well-known multicast based communication.
    For detailed information, please refer to the link below,
    IPv6 Multicast Address Assignments
    http://tools.ietf.org/html/rfc2375
    Best Regards.
    Steven Lee
    TechNet Community Support

Maybe you are looking for