public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Drobnak <mdrobnak@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: IPv6 anomolies on the PowerPC platform
Date: Mon, 25 Mar 2002 16:09:16 -0500	[thread overview]
Message-ID: <3C9F91FC.5040104@optonline.net> (raw)

Hello all, this is my first posting to the kernel mailing list, so 
please bear with me...

	I have a Apple Power Macintosh 7200/120, which is a PowerPC 601 based 
computer, running Debian Testing. I was using Yellow Dog Linux 2.1 
before, running kernel 2.4.17. I currently use 2.4.16-newpmac from Debian.

	When running 2.4.17, if you tried to make a connection to the machine via 
IPv6 it would work sometimes, but fail most of the times. Taking the 
interface down and bringing it back up would fix the problem for 
approximately 1 - 2 minutes. It also did not pick up an address, as it 
should have, as I run radvd on my router (linux also). Note this was 
with IPv6 compiled in, not a module.

	I had hoped it was something other than kernel related, so I re-installed 
linux, using Debian, over this past weekend. Now, however, problems are 
worse. As well as not getting an address, even manually configuring the 
address does not work. It is not pingable at all using IPv6, nor do any 
connections (like to apache) work.

	Any pointers on where to start debugging this would be appreciated, as I 
would like to try and get it working correctly. I am not the most 
experienced programmer in the world, but I would try and make a best 
effort attempt to help in any way that I can to help resolve this 
matter. I also have a G3 iBook (tangerine) that I have not tested, as I 
did not get around to recompiling a kernel for yet.


Thank you for your time,

-Matthew Drobnak


                 reply	other threads:[~2002-03-25 21:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C9F91FC.5040104@optonline.net \
    --to=mdrobnak@optonline.net \
    --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