* ipv6 route configuration
@ 2008-11-14 9:38 Mohan Lal Jangir
2008-11-14 18:09 ` Brian Haley
0 siblings, 1 reply; 2+ messages in thread
From: Mohan Lal Jangir @ 2008-11-14 9:38 UTC (permalink / raw)
To: netdev
[foo:/root] route -A inet6 add 2::/64 gw 2::1 dev eth5
SIOCADDRT: Invalid argument
[foo:/root]
Could someone please tell why route addition tells invalid argument ?
Gateway 2::1 is reachable.
[foo:/root] ping6 2::1
PING 2::1(2::1) 56 data bytes
64 bytes from 2::1: icmp_seq=0 ttl=64 time=0.755 ms
64 bytes from 2::1: icmp_seq=1 ttl=64 time=0.395 ms
--- 2::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1012ms
rtt min/avg/max/mdev = 0.395/0.575/0.755/0.180 ms, pipe 2
Thanks
-Mohan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ipv6 route configuration
2008-11-14 9:38 ipv6 route configuration Mohan Lal Jangir
@ 2008-11-14 18:09 ` Brian Haley
0 siblings, 0 replies; 2+ messages in thread
From: Brian Haley @ 2008-11-14 18:09 UTC (permalink / raw)
To: Mohan Lal Jangir; +Cc: netdev
Mohan Lal Jangir wrote:
> [foo:/root] route -A inet6 add 2::/64 gw 2::1 dev eth5
> SIOCADDRT: Invalid argument
> [foo:/root]
> Could someone please tell why route addition tells invalid argument ?
Because 2::1 is in the reserved address space (see
http://www.iana.org/assignments/ipv6-address-space) and the kernel needs
to have a unicast address for the gateway. You could try using the
link-local address (which is preferred) for that system instead. Or use
a real global prefix or generate a ULA.
-Brian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-11-14 18:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-14 9:38 ipv6 route configuration Mohan Lal Jangir
2008-11-14 18:09 ` Brian Haley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).