From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
debian-devel@lists.debian.org, submit@bugs.debian.org,
dhd@debian.org
Subject: netatalk refuses to start with ethernet aliasing
Date: Wed, 22 Nov 2000 17:39:38 -0600 [thread overview]
Message-ID: <3A1C593A.253A2707@mnsu.edu> (raw)
Hello,
I'm using Debian Potato with linux-2.2.18pre22. This version of Potato
uses netatalk (1.4b2+asun2.1.3).
Everything works just fine if I have the two interfaces:
lo
eth0
As soon as I alias eth0 and have the interfaces:
lo
eth0
eth0:0
eth0:1
eth0:2
netatalk refuses to start and I receive this in syslog:
Nov 22 17:01:23 files atalkd[177]: restart (1.4b2+asun2.1.3)
Nov 22 17:01:24 files atalkd[177]: zip_getnetinfo for eth0
Nov 22 17:01:25 files atalkd[177]: zip gnireply from 275.241 (eth0 12)
Nov 22 17:01:26 files atalkd[177]: zip_packet configured eth0 from
275.241
Nov 22 17:01:26 files atalkd[177]: setifaddr: eth0:0: No such device
Nov 22 17:01:26 files atalkd[177]: difaddr(65280.0): No such device
Nov 22 17:01:26 files atalkd[177]: difaddr(0.0): No such device
Nov 22 17:01:26 files atalkd[177]: difaddr(0.0): No such device
Nov 22 17:01:26 files atalkd: difaddr(0.0): No such device
Nov 22 17:01:26 files last message repeated 2 times
Nov 22 17:01:27 files afpd[180]: main: atp_open: Cannot assign requested
address
My current work around is:
1. start the interfaces:
lo
eth0
2. start netatalk
3. create my eth0 aliases.
This works fine... but is a little strange.
Thanks for your help,
Jeffrey Hundstad
jeffrey.hundstad@mnsu.edu
Minnesota State University, Mankato
http://www.mnsu.edu/jeffrey/
-
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-11-23 0:10 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=3A1C593A.253A2707@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=debian-devel@lists.debian.org \
--cc=dhd@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=submit@bugs.debian.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