"Element not found" error when trying to define static IPv6 route

Answered "Element not found" error when trying to define static IPv6 route

  • Thursday, December 01, 2011 2:36 PM
     
     

    I'm building a UAG/DirectAccess server which requires the internal NIC not to have a default gateway. We have a number of internal subnets and I'm trying to define static routes for the IPv6 addressing of those subnets but it always fails with an "Element not found" error.

    Our /48 network has been divided into a number of /64 subnets. The command I'm using is:

    netsh interface ipv6 add route 2001:aaa:bbb:ccc::/64 "Internal" 2001:aaa:bbb:ggg::1

    but it just gives me that very unhelpful error message.

    What am I overlooking or what do I need to do to get the route to be applied?

    Many thanks.

    Philip

     

All Replies

  • Friday, December 09, 2011 3:24 PM
     
     

    Nobody?

    Has anyone successfully added an IPv6 static route?

    Philip

     

  • Sunday, December 11, 2011 11:57 PM
     
     Answered

    I have done this, sing the following syntax:

    run 'netsh int ipv6 sh int'  to get the interface idx number for your interface called "Internal"

    netsh interface ipv6 add route 2001:aaa:bbb:ccc::/64 interface=<interface_idx> 2001:aaa:bbb:ggg::1

     

    Let us know if that works :-)

    Cheers...Jeff

     

     


    jeff carrell
    • Marked As Answer by Philip Colmer Monday, December 12, 2011 8:48 AM
    •  
  • Monday, December 12, 2011 8:48 AM
     
     

    I have done this, sing the following syntax:

    run 'netsh int ipv6 sh int'  to get the interface idx number for your interface called "Internal"

    netsh interface ipv6 add route 2001:aaa:bbb:ccc::/64 interface=<interface_idx> 2001:aaa:bbb:ggg::1

     

    Let us know if that works :-)

    Cheers...Jeff

     

     


    jeff carrell


    Thank you! That has done the trick.

    Philip

     

  • Friday, September 14, 2012 2:06 PM
     
     
    Thanks !!! really helped me..
  • Thursday, October 11, 2012 3:11 PM
     
     

    Just had the same issue with a client, he was actually entering the wrong lan interface  name

    http://www.techieshelp.com/ipv6-element-not-found/