public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Toscano <pete@research.netsol.com>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux ipv6 questions.  bugs?
Date: Wed, 13 Dec 2000 16:25:12 -0500	[thread overview]
Message-ID: <20001213162512.N1139@tesla.admin.cto.netsol.com> (raw)
In-Reply-To: <20001213144558.L1139@tesla.admin.cto.netsol.com> <200012132027.XAA15957@ms2.inr.ac.ru>
In-Reply-To: <200012132027.XAA15957@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Wed, Dec 13, 2000 at 11:27:00PM +0300

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]


On Wed, 13 Dec 2000, kuznet@ms2.inr.ac.ru wrote:

> Hello!
> 
> > 0.  whenever i ping6 the loopback interface (::1/128), all echo requests
> > seem to be dropped and i get no echo replies.  is this correct?
 
> Your guess? 8) Of course, it is incorrect. I even have no idea
> how it is possible to put system into such sad state.

well, just power it on, it seems.  but then again, this is just a guess.
=;]

> Though... probably, you forgot to up loopback.

doesn't look it:

[root@nsv6 /root]# ifconfig lo
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:7952  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
[root@nsv6 /root]# ping6 ::1
PING ::1(::1) from ::1 : 56 data bytes

--- ::1 ping statistics ---
156 packets transmitted, 0 packets received, 100% packet loss

...and this is right after boot.

> > the destination mac address is set to the linux box's mac address and
> > the source mac address is set to 0:0:0:0:0:0.
> 
> I think it is consequence of above. When loopback interface is missing,
> networking does not work.
> 
> 
> > other way around?  this would explain why the openbsd box doesn't
> > respond to the linux box's n.s. until it starts looking at all the
> > packets in promisc mode, right?
> 
> Rather it means that openbsd is buggy, its stack accepts packets
> not destined to it. It cannot react to those strange packets, which
> you have just described.

that may very well be, but shouldn't the neighbor solisitation packets
from the linux box have the source mac address set to its mac address
and the destination mac address set to 0:0:0:0:0:0 and not the other way
around?

thanks,
pete

-- 
Pete Toscano    p:sigsegv@psinet.com     w:pete@research.netsol.com
GPG fingerprint: D8F5 A087 9A4C 56BB 8F78  B29C 1FF0 1BA7 9008 2736

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-12-13 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 19:45 linux ipv6 questions. bugs? Pete Toscano
2000-12-13 20:27 ` kuznet
2000-12-13 21:25   ` Pete Toscano [this message]
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
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=20001213162512.N1139@tesla.admin.cto.netsol.com \
    --to=pete@research.netsol.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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