linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher R. Johnson" <cjohnson@gcctech.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: netatalk with appletalk on ppc
Date: Mon, 03 May 2004 08:39:33 -0400	[thread overview]
Message-ID: <40963D85.6090805@gcctech.com> (raw)


Ok, perhaps this should be posted elsewhere, but I figure someone here
might have tried this:

I'm using netatalk - trying to get the atalkd component up.  I've done
this in the past with older kernels, but this time I'm on 2.4.23rc1.
 I'm using the on-chip ethernet support on the 405, and its working
great with IP based stuff.  I've tried two different versions of
netatalk with identical results.

When atalkd starts up it does aarp probing to see if it can come up with
an Appletalk network address.  The probe is sent out on the wire, but
something wierd happens.  the aarp_rcv code gets invoked right away, and
when I look at the packet its examing, its the exact packet that was
just sent out.  This code sees this as an aarp probe being done by some
other network entity (why?  the mac address is mine) and fails the
probe.  The aarp code then moves on to another address to try, and the
whole thing happens again, forever.  Its definitely going to eth0, and
as I mentioned I see the aarp probe go out on the wire.  Running similar
code on my intel desktop works fine, the probes happen 10 times, .1
seconds apart, no one answers, and the code adopts that Appletalk
address (the expected behavior).  I'm trying to wind my way through the
net_tx_action and net_rx_action code to see why this is happening, but
its slow going.

Suggestions?


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-05-03 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 12:39 Christopher R. Johnson [this message]
2004-05-03 19:58 ` netatalk with appletalk on ppc Christopher R. Johnson

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=40963D85.6090805@gcctech.com \
    --to=cjohnson@gcctech.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).