Date: Fri, 28 Nov 1997 11:17:32 -0800 From: David Greenman <dg@root.com> To: Mike <mike@seidata.com> Cc: Julian Elischer <julian@whistle.com>, freebsd-questions@FreeBSD.ORG Subject: Re: rtinit Message-ID: <199711281917.LAA19093@implode.root.com> In-Reply-To: Your message of "Fri, 28 Nov 1997 13:17:18 EST." <Pine.BSF.3.96.971128131012.15105A-100000@seidata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Fri, 28 Nov 1997, Julian Elischer wrote: > >> do you have appletalk? > >We do have one Mac system setup on our LAN. Appletalk is active on the >Mac to allow it to communicate with PCs on the LAN via PC/MacLAN, but it >uses TCP/IP (Open Transport) to communicate with the server. We were >initially getting arp lookup errors... so we used arp to add entries for >the systems on our LAN. This did not fix the problems, probably because I >used arp incorrectly. We changed the subnet our LAN was using to >255.255.255.252 and the arp lookup errors went away - for our PC-based >systems, that is. The Mac would not allow us to change the subnet to .252 >but insisted it remain 255.255.255.0 in TCP/IP. Would something I did >with arp be causing this problem or do I need to configure either the >server or the Mac in some way? Thanks for any insight... The Macs that are outside of the .252 subnet are probably trying to talk with the FreeBSD on the ethernet. When FreeBSD tries to resolve the destination (probably when it is trying to respond to the arp who-has from the Mac), it can't find it. The botton line is that all of the hosts on the ethernet need to agree on the subnet mask. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711281917.LAA19093>