All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: a sun <asun@saul4.u.washington.edu>
To: jhart@abacus.bates.edu
Cc: MBoie@Adobe.COM, rspell@bates.edu,
	linuxppc-dev@lists.linuxppc.org, netatalk-admins@umich.edu
Subject: Re: Netatalk  bug?, too many routes/iface
Date: Tue, 27 Jul 1999 12:32:39 -0700 (PDT)	[thread overview]
Message-ID: <199907271932.MAA28492@saul4.u.washington.edu> (raw)
In-Reply-To: <199907271901.PAA22932@abacus.bates.edu> (jhart@abacus.bates.edu)


   I presume, then, that this is a bug in the Appletalk code in LinuxPPC, 
   even though it's numbered 0.18, as compared to 0.17 in the Redhat 5.2 
   we're running on our Intel machines.  The Intel machines have no problem 
   with our network numbering ranges, which, according to our network 
   administrator, can legally go from 1 to 65535.

i think that it might have been an endianness bug, but i'm not
sure. if it still happens with linux-2.2.10, let me know, and i'll
look into it. oh yeah, your administrator is wrong about the range of
possible network numbers. numbers from 65280 to 65534 are reserved for
routerless networks.

-a



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-07-27 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-27 19:02 Netatalk bug?, too many routes/iface jhart
1999-07-27 19:32 ` a sun [this message]

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=199907271932.MAA28492@saul4.u.washington.edu \
    --to=asun@saul4.u.washington.edu \
    --cc=MBoie@Adobe.COM \
    --cc=jhart@abacus.bates.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=netatalk-admins@umich.edu \
    --cc=rspell@bates.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.