Subject: Re: AARP corruption/netatalk
From: Quant-X UNIX and Linux Support (lists@quant-x.com)
Date: Mon Feb 14 2000 - 11:54:32 EST
Hello,
I think that you should send this to the linux-kernel list as the code
which handles AARP resides in the kernel. This sounds like a serious
problem to me. Perhaps it could have much consequences much worse than
disappearing from the chooser. Anybody else seen it?
I'm afraid that otherwise I can't offer much help to you. AARP doesn't
smell good (by design). Too many broadcasts. Well, if this is not
happening at many installations I guess that some things are getting
lost on your network. Perhaps you can check cables and if the network
is OK in general. Is it that the server disappears only from certain
Macs?
Best regards,
Dejan
On Fri, Feb 11, 2000 at 07:00:10PM +0000, Alistair Riddell wrote:
> I have an annoying problem.
>
> I use Netatalk to serve files to a network of around 400 macs. From time
> to time the netatalk server disappears from the chooser. I have traced
> this to the AARP entries cached in the server not matching the actual
> address of the machines.
>
> Typically the machine's hardware address shows in /proc/net/aarp but the
> corresponding AppleTalk address does not match that found in the AppleTalk
> control panel.
>
> The annoying thing is there is no way that I can see of flushing/altering
> /proc/net/aarp without killing netatalk and doing rmmod
> appletalk. Obviously this is undesirable.
>
> Some more details:
>
> Server is running netatalk pre-asun2.1.4-37b.tar.gz; Linux kernel
> 2.3.42. However the problem has been present for some time even when using
> older netatalkd and kernel 2.2.
>
> machine is a dual-processor PIII; network card is a 3Com 3c905b plugged
> into a 3com CoreBuilder 3500 switch, which is configured as an AppleTalk
> router.
>
> Only machines in the same zone as the server have problems; other machines
> don't presumably because the 3500 router does the AARP stuff.
>
> These problems do not affect TCP/IP connectivity; I can ping both ways
> to/from affected machines and I can connect to the server by entering its
> IP address in the chooser.
>
> This only appears to affect a handful of machines at once.
>
> Although the network range is a single number there are nothing like 254
> machines in that network - the others are on the other side of the router.
>
> My /etc/atalkd/atalkd.conf looks like this:
>
> eth0 -phase 2 -net 12 -addr 12.152 -zone "Senior School South"
>
> I would be grateful for any suggestions.
>
>
> --
> Alistair Riddell - BOFH
> IT Support Department, George Watson's College, Edinburgh
> Tel: +44 131 447 7931 Ext 176 Fax: +44 131 452 8594
> Microsoft - because god hates us
--Dejan Muhamedagic mailto:dejan@quant-x.com UNIX and Linux Support mailto:support@quant-x.com
Quant-X Service & Consulting Ges.m.b.H. http://www.quant-x.com Phn: +43 4212 90555-0 Fax: 90555-20 Free: +800 90555 000
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:04 EST