Subject: Re: [netatalk-admins] bind: Cannot assign requested address
From: Markus Boie (Markus.Boie@golive.de)
Date: Thu Aug 05 1999 - 09:12:07 EDT
Hello,
we had the same problem (too many routes/if). Konstantin Reznitsky <rkv@alpha1.gmslaw.com> came up with what turned out to be the solution:
"The problem may really be that you have a too wide network range."
On our AppleTalk router (Helios on a Sun) we had defined a network range of 1-60000. Setting this to 1-200 was all I needed to do to make atalkd on the Linux box start.
Markus
>I'm getting the same problem on another RH6.0 installation. Here's some
>more info (this is without an atalkd.conf file).
>
>atalkd[4317]: restart (1.4b2+asun2.1.3)
>atalkd[4317]: zip_getnetinfo for eth0
>atalkd[4317]: zip gnireply from 38893.150 (eth0 12) <- this is my seeding
> router
>atalkd[4317]: setifaddr: eth0: Invalid argument
>atalkd: difaddr(0.0): No such device
>kernel: Too many routes/iface
>
>Anybody with any clues?
>On Tue, 3 Aug 1999 bmahlock@gmti.gannett.com wrote:
>
>> Hi Admins,
>>
>> I've run into an appletalk situation where something on the network is
>> preventing atalkd from starting on a RH6.0 server. I know it's on the
>> network, because it starts ok if I plug the server and one Mac into a hub
>> all alone.
>>
>> When starting the atalk from the command line, i get
>>
>> bind: Cannot assign requested address
>>
>> /var/log/messages says:
>>
>> Aug 3 17:20:03 DC-Archive atalkd[2761]: restart (1.4b2+asun2.1.0)
>> Aug 3 17:20:04 DC-Archive atalkd[2761]: zip_getnetinfo for eth0
>> Aug 3 17:20:04 DC-Archive atalkd[2761]: zip gnireply from 281.170 (eth0 12)
>> Aug 3 17:20:05 DC-Archive kernel: Too many routes/iface.
>> Aug 3 17:20:05 DC-Archive atalkd[2761]: setifaddr: eth0: Invalid argument
>> Aug 3 17:20:05 DC-Archive atalkd: AppleTalk not up! Child exited with 1.
>> Aug 3 17:20:05 DC-Archive atalk: atalkd startup failed
>>
>> The atalk.conf file is currently configured with the following line (but
>> I've been through dozens of configurations with similar results):
>>
>> eth0 -phase 2 -net 10-20 -addr 10.5 -zone "the road"
>>
>> The ifconfig of the eth0 looks like this:
>>
>> eth0 Link encap:Ethernet HWaddr 00:50:04:77:85:37
>> inet addr:10.1.45.11 Bcast:10.1.45.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500
>> Metric:1
>> RX packets:70931 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:6950 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:168
>>
>> The netcard is a 3c905(a or b) using the 3c59x driver.
>>
>> Any clues anybody can provide would be greatly appreciated.
>>
>> Cheers,
>> Bill Mahlock
>>
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:17:01 EST