RE: [netatalk-admins] netatalk-1.4b2+asun2.0a18.2 - IP works, eth ertalk doesn't?


Subject: RE: [netatalk-admins] netatalk-1.4b2+asun2.0a18.2 - IP works, eth ertalk doesn't?
From: Sean Page (spage@epsb.edmonton.ab.ca)
Date: Tue May 26 1998 - 15:20:06 EDT


Right you are.
So, I'm still wondering why it is that the Mac that is on the same
physical hub as the server (on the inside interface) cannot see the
server via standard EtherTalk. Is there something I haven't done in
order to make the server advertise via ethertalk on the inside
interface?

> ----------
> From: Hannu Krosing
> Sent: Tuesday, May 26, 1998 9:47 AM
> To: Sean Page
> Cc: 'Andras Kadinger'; 'netatalk list'
> Subject: Re: [netatalk-admins] netatalk-1.4b2+asun2.0a18.2 - IP
> works, eth ertalk doesn't?
>
> <<File: smime.p7s>>
> Sean Page wrote:
> >
> > Hi, Andras,
> >
> > No, there are no other routers, it is a very small test network
> > consisting of only the FreeBSD server (sitting between the Appletalk
> > network on ethernet and the Internet) and one mac workstation
> running OS
> > 8. Both of them are on the same hub on the inside network. It's very
> > strange. Even when I use the -seed option, the Mac can't see the
> server
> > in the chooser.
> >
> > Tried making the atalkd.conf file read only (great suggestion by the
> > way!), but that didn't work either. I also tried manually changing
> the
> > net address on the mac to be the same as the server (different node,
> of
> > course) and that also didn't help. I'm starting to think there is
> > something more fundamentally wrong. Any more suggestions?
>
> AFAIK there is no protocol for server advertizing that works over IP,
> so
> you can see only these machines in the chooser that advertize using
> ethertalk, not IP.
>
> To use ethertalk, you must have appletalk support in your OS.
>
> I'm not sure that this is the case for FreeBSD, at least not default
>
> Hannu
>



This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:45 EST