[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#435387: marked as done (netatalk: Atalkd won't start up with Token Ring Interface)

Your message dated Fri, 26 Feb 2010 00:08:55 +0100
with message-id <20100225230855.GA16714@galadriel.inutil.org>
and subject line Re: Bug#435387: Redirect to Kernel?
has caused the Debian Bug report #435387,
regarding netatalk: Atalkd won't start up with Token Ring Interface
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
435387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435387
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: netatalk
Version: 2.0.3-4
Severity: important


After installing netatalk, stopping, putting tr0 (as it's the only
interface the machine has) and starting up again, syslog states:

setifaddr: tr0 (65280-65534): Protocol not supported. try specifying a smaller net range.

The above range is a range where atalk starts up every time to discover
the real net range afterwards. Seems as if atalkd doesn't support Token
Ring at all.

Accessing AFP over IP works just fine but there's no native AppleTalk
support available.

-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages netatalk depends on:
ii  libc6                    2.3.6.ds1-13    GNU C Library: Shared libraries
ii  libcupsys2               1.2.7-4         Common UNIX Printing System(tm) - 
ii  libdb4.2                 4.2.52+dfsg-2   Berkeley v4.2 Database Libraries [
ii  libgssapi4-heimdal       0.7.2.dfsg.1-10 Libraries for Heimdal Kerberos
ii  libkrb5-17-heimdal       0.7.2.dfsg.1-10 Libraries for Heimdal Kerberos
ii  libpam-modules           0.79-4          Pluggable Authentication Modules f
ii  libpam-runtime           0.79-4          Runtime support for the PAM librar
ii  libpam0g                 0.79-4          Pluggable Authentication Modules l
ii  libslp1                  1.2.1-6.2       OpenSLP libraries
ii  libwrap0                 7.6.dbs-13      Wietse Venema's TCP wrappers libra
ii  netbase                  4.29            Basic TCP/IP networking system
ii  perl                     5.8.8-7         Larry Wall's Practical Extraction 

Versions of packages netatalk recommends:
pn  db4.2-util                    <none>     (no description available)
pn  lsof                          <none>     (no description available)
pn  rc                            <none>     (no description available)
ii  slpd                          1.2.1-6.2  OpenSLP Server (slpd)

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, Dec 01, 2009 at 02:58:11PM +0100, Bjørn Mork wrote:
> Patrik Schindler <poc@pocnet.net> writes:
> 
> > Good point. But Token Ring Card drivers already exist, even if there
> > is likely not a very much bigger demand. :-)
> 
> Well, they do exist but they are probably going away too.  I don't see
> anyone really interested in hacking on them, so they are staying just as
> long as they continue to work.  Which may not be that long...
> 
> E.g. my nice triple lanstreamer card doesn't work after upgrading the
> rest of the system to 64bit, as the original driver does a whole lot of
> magic DMA access and no-one has cleaned it up for 64bit.  So the driver
> is disabled for 64bit systems.  I don't think anyone will bother to fix
> it.  I briefly looked at it, and found that there's definitely a reason
> why this was just disabled.  It's a mess.
> 
> The card is in the attic now, with the rest of my Token Ring stuff.
> Except for a Cisco 2612 which serves as an Ethernet/Serial only router.

Let's just close the bug, then.

Cheers,
        Moritz

--- End Message ---
Reply to: