Re: ipv6 question

2011-03-11 Thread Valdis . Kletnieks
On Fri, 11 Mar 2011 11:15:36 PST, ann kok said:

 inet6 addr: fe80::20c:29ff:fe3c:92a1/64 Scope:Link

This is a link level address, only valid on one interface.  So you need to look
at which interface it is attached to in the ifconfig output.

 ping6 fe80::20c:29ff:fe3c:92a1
 connect: Invalid argument

ping6 wants the interface name for link-scope addresses, because on some
hardware setups, the same MAC is used for all interfaces, which means that
each interface has the same link-scope address.  So to disambiguate it,
you have to feed it the interface name so it knows which link to use.

On my laptop, I currently have:

wlan0 Link encap:Ethernet  HWaddr 00:24:D6:53:C5:BA
inet6 addr: fe80::224:d6ff:fe53:c5ba/64 Scope:Link

% ping  fe80::224:d6ff:fe53:c5ba%wlan0
 ping6  fe80::224:d6ff:fe53:c5ba%wlan0
PING fe80::224:d6ff:fe53:c5ba%wlan0(fe80::224:d6ff:fe53:c5ba) 56 data bytes
64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=1 ttl=64 time=0.072 ms
64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=2 ttl=255 time=0.081 ms
64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=3 ttl=255 time=0.090 ms
^C
--- fe80::224:d6ff:fe53:c5ba%wlan0 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.072/0.081/0.090/0.007 ms



pgpkHDgW3pDcv.pgp
Description: PGP signature


Re: ipv6 question

2011-03-11 Thread ann kok
Hi

Thank you. I try your way.  the ipv6 address is on eth0 interface.

I try to run ping6 the fe80::20c:29ff:fe3c:92a1%eth0

lt is same problem!

Any idea?

Thank you


2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0c:29:3c:92:a1 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.12/24 brd 192.168.1.255 scope global eth0
inet6 fe80::20c:29ff:fe3c:92a1/64 scope link tentative 
   valid_lft forever preferred_lft forever


# ping6  fe80::20c:29ff:fe3c:92a1
connect: Invalid argument
# ping6  fe80::20c:29ff:fe3c:92a1%eth0
connect: Invalid argument


--- On Fri, 3/11/11, valdis.kletni...@vt.edu valdis.kletni...@vt.edu wrote:

 From: valdis.kletni...@vt.edu valdis.kletni...@vt.edu
 Subject: Re: ipv6 question
 To: ann kok oiyan...@yahoo.ca
 Cc: nanog@nanog.org
 Received: Friday, March 11, 2011, 2:21 PM
 On Fri, 11 Mar 2011 11:15:36 PST, ann
 kok said:
 
  inet6 addr: fe80::20c:29ff:fe3c:92a1/64 Scope:Link
 
 This is a link level address, only valid on one
 interface.  So you need to look
 at which interface it is attached to in the ifconfig
 output.
 
  ping6 fe80::20c:29ff:fe3c:92a1
  connect: Invalid argument
 
 ping6 wants the interface name for link-scope addresses,
 because on some
 hardware setups, the same MAC is used for all interfaces,
 which means that
 each interface has the same link-scope address.  So to
 disambiguate it,
 you have to feed it the interface name so it knows which
 link to use.
 
 On my laptop, I currently have:
 
 wlan0     Link encap:Ethernet 
 HWaddr 00:24:D6:53:C5:BA
     inet6 addr: fe80::224:d6ff:fe53:c5ba/64
 Scope:Link
 
 % ping  fe80::224:d6ff:fe53:c5ba%wlan0
  ping6  fe80::224:d6ff:fe53:c5ba%wlan0
 PING
 fe80::224:d6ff:fe53:c5ba%wlan0(fe80::224:d6ff:fe53:c5ba) 56
 data bytes
 64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=1 ttl=64
 time=0.072 ms
 64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=2 ttl=255
 time=0.081 ms
 64 bytes from fe80::224:d6ff:fe53:c5ba: icmp_seq=3 ttl=255
 time=0.090 ms
 ^C
 --- fe80::224:d6ff:fe53:c5ba%wlan0 ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time
 1999ms
 rtt min/avg/max/mdev = 0.072/0.081/0.090/0.007 ms
 
 





Re: ipv6 question

2011-03-11 Thread ann kok
Hi

What is this meaning?

ping6 -l eth0 fe80::20c:29ff:fe3c:92a1
ping: bad preload value, should be 1..65536

Thank you


--- On Fri, 3/11/11, Jason Bertoch ja...@i6ix.com wrote:

 From: Jason Bertoch ja...@i6ix.com
 Subject: Re: ipv6 question
 To: nanog@nanog.org
 Received: Friday, March 11, 2011, 3:31 PM
 On 2011/03/11 3:19 PM, ann kok
 wrote:
  Thank you. I try your way.  the ipv6 address is
 on eth0 interface.
 
  I try to run ping6 the fe80::20c:29ff:fe3c:92a1%eth0
 
  lt is same problem!
 
 Try ping6 -I eth0 fe80::20c:29ff:fe3c:92a1
 
 -- 
 /Jason
 
 





Re: ipv6 question

2011-03-11 Thread ann kok
Hi Jason

Thank you. Can I know what is wrong?

ping6 -I eth0 fe80::20c:29ff:fe3c:92a1
connect: Cannot assign requested address

Thank you

--- On Fri, 3/11/11, Jason Bertoch ja...@i6ix.com wrote:

 From: Jason Bertoch ja...@i6ix.com
 Subject: Re: ipv6 question
 To: nanog@nanog.org
 Received: Friday, March 11, 2011, 3:41 PM
 On 2011/03/11 3:36 PM, ann kok
 wrote:
  What is this meaning?
 
  ping6 -l eth0 fe80::20c:29ff:fe3c:92a1
  ping: bad preload value, should be 1..65536
 
 That was a capital i not a lower case L. man ping6
 -- 
 /Jason
 
 





Re: ipv6 question

2011-03-11 Thread Jason Bertoch

On 2011/03/11 3:51 PM, ann kok wrote:

ping6 -I eth0 fe80::20c:29ff:fe3c:92a1
connect: Cannot assign requested address


Maybe duplicate address detection?  Are you statically assigning this 
address?  Have you checked your kernel log?


--
/Jason



Re: ipv6 question

2011-03-09 Thread imNet Administrator
On 3/9/2011 8:41 AM, ann kok wrote:
 Hi
 
 I read ipv6forum.pdf about ipv6
 
 It said 
 
 MTU must be at least 1280 bytes (1500+)
 Does it mean to set the mtu over 1500

No, it simply means that the minimum MTU for IPv6 is 1280.

 
 I set my linux box eth0 as 2001:db8:cafe:::12/64 but I can't ping it
 inet6 2001:db8:cafe:::12/64 scope global tentative 
 
 ls it this problem? Thank you

Where are you pinging it from? also, the 2001:db8::/32 prefix is used
for documentation purposes and might be handled differently by the
TCP/IP stack.

 
 
 # ping6 2001:db8:cafe:::12
 PING 2001:db8:cafe:::12(2001:db8:cafe:::12) 56
   
 
 data bytes
 
 
From ::1 icmp_seq=1 Destination unreachable:
   
 
 Address unreachable
 
 
From ::1 icmp_seq=2 Destination unreachable:
   
 
 Address unreachable
 
 
 
 
 
 




signature.asc
Description: OpenPGP digital signature


Re: ipv6 question

2011-03-09 Thread Karl Auer
On Wed, 2011-03-09 at 09:01 -0600, imNet Administrator wrote:
 Where are you pinging it from? also, the 2001:db8::/32 prefix is used
 for documentation purposes and might be handled differently by the
 TCP/IP stack.

Works fine in Linux - I've been using it (in an isolated training room
setup) for years.

Regards, K.

-- 
~~~
Karl Auer (ka...@biplane.com.au)   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156


signature.asc
Description: This is a digitally signed message part


Re: ipv6 question

2011-03-09 Thread Mark Andrews

In message 1299711449.2109.98.camel@karl, Karl Auer writes:
 On Wed, 2011-03-09 at 09:01 -0600, imNet Administrator wrote:
  Where are you pinging it from? also, the 2001:db8::/32 prefix is used
  for documentation purposes and might be handled differently by the
  TCP/IP stack.
 
 Works fine in Linux - I've been using it (in an isolated training room
 setup) for years.
 
 Regards, K.

It is not a good idea to use the documentation prefix for anything
other than documentation.  How hard is it to generate a ULA and use
it?

 --=20
 ~~~
 Karl Auer (ka...@biplane.com.au)   +61-2-64957160 (h)
 http://www.biplane.com.au/kauer/   +61-428-957160 (mob)
 
 GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
 Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
 
 --=-nDQtqdgDW08ncP39wFQZ
 Content-Type: application/pgp-signature; name=signature.asc
 Content-Description: This is a digitally signed message part
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 
 iEYEABECAAYFAk14BdEACgkQMAcU7Vc29oc3ewCffqKqCJQ67ytpAHeAT7iZ834G
 5SMAniLZpqhnAS8Nk3HRcZzhaRrF1c0L
 =PFHP
 -END PGP SIGNATURE-
 
 --=-nDQtqdgDW08ncP39wFQZ--
 
 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org



Re: ipv6 question

2011-03-09 Thread Karl Auer
On Thu, 2011-03-10 at 11:43 +1100, Mark Andrews wrote:
 In message 1299711449.2109.98.camel@karl, Karl Auer writes:
  On Wed, 2011-03-09 at 09:01 -0600, imNet Administrator wrote:
   Where are you pinging it from? also, the 2001:db8::/32 prefix is used
   for documentation purposes and might be handled differently by the
   TCP/IP stack.
  
  Works fine in Linux - I've been using it (in an isolated training room
  setup) for years.
  
  Regards, K.
 
 It is not a good idea to use the documentation prefix for anything
 other than documentation.  How hard is it to generate a ULA and use
 it?

I suppose I took/take the view that it *is*, in a sense, being used for
documentation.

The network is a training network, isolated from the Internet, and used
for demonstration purposes. It's a good way to engrave the doco prefix
in the students' minds. It also allows all the slides, exercises and
other documentation to use the documentation prefix and yet directly
match the demonstration network.

ULA prefixes have little internal logic and are hard to remember. Not a
problem in production, but just another barrier in a training
environment. 2001:db8::/32 is very easy to remember (I guess that's
the point) and easy to add easy-to-use subnets into.

However, I do appreciate that it's a bit of an edge case. In my training
I specifically draw the students' attention to this fact.

Thanks, K.

-- 
~~~
Karl Auer (ka...@biplane.com.au)   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156


signature.asc
Description: This is a digitally signed message part