NetATalk atalkd[161]: addmulti: invalid argument????

NetATalk atalkd[161]: addmulti: invalid argument????

Post by Christ.. » Wed, 18 Feb 1998 04:00:00



hi all,
i've run into a little snag with netatalk.. i have 3.0 snap, from just
a few days ago.. mid last week.. all seems happy, got apache all set to
go, then went to put in netatalk.. and got the error as in subject.. i
looked in all the atalk conf type stuff that i could spot, and i did not
even see anything with "addmulti" in there.. i went to libexec area and
found atalkd, but it looks like a binary or something.. any ideas where
this addmulti is comin from??  better yet, any ideas on how to make the
error go away??

network card is
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x04
int a irq 5 on pci0.17.0

i've tried no atalkd.conf.
one with fxp0 -phase 2 -net 0-65534 -addr 65280.140

my appletalk control panels on the macs show stuff
like node: 173   network: 65280     network range: 0 to 65534  
i picked 140 at random, as the lowest of the macs has 152.. also i tried
numbers higher and lower but still get this addmulti error.. is it some
lower level stuff?? like the ethernet card and the driver??
the card is set to 10baset full duplex..


Sur-Tech / Ami-Tech    (408) 496-6348 Xt 247     Santa Clara CA 95050
                          www.Sur-Tech.com

 
 
 

NetATalk atalkd[161]: addmulti: invalid argument????

Post by Christ.. » Wed, 18 Feb 1998 04:00:00


Hey Steve, RE:Below




> > network card is
> > fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x04
> > int a irq 5 on pci0.17.0

> > i've tried no atalkd.conf.
> > one with fxp0 -phase 2 -net 0-65534 -addr 65280.140

> What ifconfig -a report about your fxp0 device?

> troutmask:kargl[221] ifconfig -a
> ep0: flags=c843<UP,BROADCAST,RUNNING,SIMPLEX,LINK2,MULTICAST> mtu 1500
>         inet 128.95.76.54 netmask 0xffffff00 broadcast 128.95.76.255
>         atalk 276.190 range 276-276 phase 2 broadcast 0.255
>         ether 00:20:af:28:08:03

> Make sure you have multicast support.

> --
> Steve


> http://troutmask.apl.washington.edu/~clesceri/kargl.html

bsd1# ifconfig -a
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.0.1.1 netmask 0xffffff00 broadcast 192.0.1.255
        atalk 66.110 range 0-65534 phase 2 broadcast 0.255
        ether 00:a0:c9:a0:80:21
        media: 10baseT/UTP
        supported media: autoselect 100baseTX <full-duplex> 100baseTX          
        10baseT/UTP <full-duplex> 10baseT/UTP

lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000
        atalk 0.0 range 0-0 phase 2

above is what i got from the ifconfig -a.. interesting it shows some
stuff about atalk in there.. i've tried kernel compiles with the line
for options NETATALK in and out.. any way i do it, i still get this
odd error, and bsd1 does not show up on atalk network.. bsd2 machine
has an ep0 card in it, and shows up just fine.. it has 2.2.5 in it..
looks like below..


lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.0.1.2 netmask 0xffffff00 broadcast 192.0.1.255
        atalk 66.6 range 0-65534 phase 2 broadcast 0.255
        ether 00:a0:24:69:b9:76
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
        inet 206.184.135.86 --> 204.156.128.1 netmask 0xffffff00
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000
        atalk 0.0 range 0-0 phase 2

I'm even more mystified now that i see both of these.. really makes me
think that it should be working..


Sur-Tech / Ami-Tech    (408) 496-6348 Xt 247     Santa Clara CA 95050
                          www.Sur-Tech.com

 
 
 

NetATalk atalkd[161]: addmulti: invalid argument????

Post by dannyma » Thu, 19 Feb 1998 04:00:00


I have the same trouble. I tried rebuilding netatalk from ports, and it
failed. :(

--

\\/yori   -=-    Information - http://www.uiuc.edu/ph/www/djhoward/   -=-
aiokomete -=-   Our Honored Symbol deserves an Honorable Retirement

 
 
 

NetATalk atalkd[161]: addmulti: invalid argument????

Post by Steven G. Kar » Thu, 19 Feb 1998 04:00:00




Quote:

> network card is
> fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x04
> int a irq 5 on pci0.17.0

> i've tried no atalkd.conf.
> one with fxp0 -phase 2 -net 0-65534 -addr 65280.140

What ifconfig -a report about your fxp0 device?

troutmask:kargl[221] ifconfig -a
ep0: flags=c843<UP,BROADCAST,RUNNING,SIMPLEX,LINK2,MULTICAST> mtu 1500
        inet 128.95.76.54 netmask 0xffffff00 broadcast 128.95.76.255
        atalk 276.190 range 276-276 phase 2 broadcast 0.255
        ether 00:20:af:28:08:03

Make sure you have multicast support.

--
Steve


http://troutmask.apl.washington.edu/~clesceri/kargl.html

 
 
 

NetATalk atalkd[161]: addmulti: invalid argument????

Post by dannyma » Thu, 19 Feb 1998 04:00:00



Quote:> What ifconfig -a report about your fxp0 device?
> troutmask:kargl[221] ifconfig -a
> ep0: flags=c843<UP,BROADCAST,RUNNING,SIMPLEX,LINK2,MULTICAST> mtu 1500
>         inet 128.95.76.54 netmask 0xffffff00 broadcast 128.95.76.255
>         atalk 276.190 range 276-276 phase 2 broadcast 0.255
>         ether 00:20:af:28:08:03

arh0300 23:31 ~> ifconfig -a
ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 130.126.72.10 netmask 0xfffffe00 broadcast 130.126.73.255
        atalk 18942.62 range 18942-18943 phase 2 broadcast 0.255
        ether 00:c0:0c:b0:ad:c6

... LINK2?

--

\\/yori   -=-    Information - http://www.uiuc.edu/ph/www/djhoward/   -=-
aiokomete -=-   Our Honored Symbol deserves an Honorable Retirement

 
 
 

NetATalk atalkd[161]: addmulti: invalid argument????

Post by Steven G. Kar » Thu, 19 Feb 1998 04:00:00





>> What ifconfig -a report about your fxp0 device?

>> troutmask:kargl[221] ifconfig -a
>> ep0: flags=c843<UP,BROADCAST,RUNNING,SIMPLEX,LINK2,MULTICAST> mtu 1500
>>         inet 128.95.76.54 netmask 0xffffff00 broadcast 128.95.76.255
>>         atalk 276.190 range 276-276 phase 2 broadcast 0.255
>>         ether 00:20:af:28:08:03

> arh0300 23:31 ~> ifconfig -a
> ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 130.126.72.10 netmask 0xfffffe00 broadcast 130.126.73.255
>         atalk 18942.62 range 18942-18943 phase 2 broadcast 0.255
>         ether 00:c0:0c:b0:ad:c6

> ... LINK2?

LINK2 tells ep0 to use the UTP port on the card.

--
Steve


http://troutmask.apl.washington.edu/~clesceri/kargl.html

 
 
 

1. atalkd won't load, "Invalid argument" (YDL/CS 1.2 on Gossamer)

OK, I brute-forced my way through, man'ing every filename in /usr/bin,
and I found the command I was looking for to find printers on the
network, nbplkup. When I ran it, no matter what I put in for a search
term, it gave me "nbp-lookup: Invalid argument".

Further digging revealed that atalkd was not listed in ps -A or in gtop.
At all. So I tried starting it manually -- and got the same error
message. If I type in atalkd, I get:

Socket: Invalid argument
Socket: Invalid argument

... and then a fail message.

I checked /etc/atalk/atalkd.conf, and everything is commented out, which
it says should auto-find the AppleTalk ports on most machines.
Apparently, not on mine.

What I want as a minimum is to get atalkd up and running to my printer
port, so I can use my HP LaserJet 4ML from within Linux. Since I suspect
there are other Macintosh users on the same cable-modem segment as me, I
wouldn't mind setting it up to auto-route between that and eth0. (I was
=very= pleased to see that atalkd, out of the box, can act as an
AppleTalk router.) What do I need to do to this box to get there? Any
help greatly appreciated.

--

J. Brad Hicks
U.S. Shamanics & Mechanical Zen

http://www.us-shamanics.com/brad/

2. pppd not terminating properly

3. Netatalk: atalkd don't start.

4. Communication between Indigo 2 and Solaris Sun Sparc 20

5. netatalk (atalkd) and the ethertap (tap0) interface

6. 2.4.21-rc3 link error: wolfson_init

7. getting bash to run on netbsd 161/sparc

8. restricting local ports

9. test 161

10. Port 161

11. Sample tests for 161

12. Probe to 161

13. SNMP daemon not active on port 161 (or anywhere); daemon loaded.