mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: mgm@paktronix.com (Matthew G. Marsh)
Cc: pete@research.netsol.com, linux-kernel@vger.kernel.org
Subject: Re: linux ipv6 questions.  bugs?
Date: Thu, 14 Dec 2000 22:24:18 +0300 (MSK)	[thread overview]
Message-ID: <200012141924.WAA02993@ms2.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.10.10012141304150.16343-100000@netmonster.pakint.net> from "Matthew G. Marsh" at Dec 14, 0 01:11:06 pm

Hello!

> I have several different boxen (test11, test12) that do something very
> similar. They cannot ping6 the link-local addresses at all. As in:
> 
> [root@paksecuredX tech]# ping6 ::1
> PING ::1(::1) from ::1 : 56 data bytes
> 64 bytes from ::1: icmp_seq=0 hops=64 time=351 usec
> 64 bytes from ::1: icmp_seq=1 hops=64 time=200 usec

This does not look similar. I daresay it rather looks working well. 8)8)


> [root@paksecuredX tech]# ping6 fe80::210:5aff:fe05:e828
> connect: Invalid argument

Right, you forgot to tell what interface you expect.
Address is link local yet, it is invalid without interface.

ping6 -I eth0 fe80::210:5aff:fe05:e828


> Now from my local box which is running 2.2.12 I can ping the link-local of
> those boxes. IE:

It was bug, it is fixed.

Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-14 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 19:45 Pete Toscano
2000-12-13 20:27 ` kuznet
2000-12-13 21:25   ` Pete Toscano
2000-12-13 23:41     ` Pete Toscano
2000-12-14 17:40     ` kuznet
2000-12-14 19:11       ` Matthew G. Marsh
2000-12-14 19:24         ` kuznet [this message]
2000-12-14 12:10   ` Russell King
2000-12-14 19:31     ` kuznet
2000-12-14 19:37       ` Russell King
2000-12-14 19:46         ` kuznet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200012141924.WAA02993@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgm@paktronix.com \
    --cc=pete@research.netsol.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®