Date: Tue, 17 Nov 1998 19:20:18 +0100 (CET) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: John Hay <jhay@mikom.csir.co.za>, freebsd-net@FreeBSD.ORG, "Matthew N. Dodd" <winter@jurai.net> Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Message-ID: <XFMail.981117192018.asmodai@wxs.nl> In-Reply-To: <199811171747.MAA26273@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17-Nov-98 Garrett Wollman wrote:
> <<On Tue, 17 Nov 1998 11:41:53 -0500 (EST), "Matthew N. Dodd"
> <winter@jurai.net> said:
>
>> struct ifframe {
>> int frame; /* frame type */
>> struct ifaddr *if_addrlist; /* address of interface */
>> struct ifnet *ifa_ifp; /* back-pointer to interface */
>> struct ifframe *iff_next; /* next frame type */
>> };
>
> Given the limited utility, I would rather see this information simply
> stored as a part of the interface address struct for IPX.
I am bound to have missed a RFC, but here goes ;)
It's a must to send/receive RFC 894 Eth encapsulation.
It should be able to receive 802.2/3 encapsulation
May send 802.2/3, yet default to RFC 894.
So as far as I can see it really ought to be in the `if' sources. Except the
two things we're bound to get is: put it in the struct of IPX and make IPX
support later on tougher (integration with NDS et al) put it in the if stuff
and be prone to break TCP/IP.
What is wisdom? =)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl | Cum angelis et pueris,
Junior Network/Security Specialist | fideles inveniamur
*BSD & picoBSD: The Power to Serve... <http://www.freebsd.org>;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.981117192018.asmodai>