Date: Wed, 6 Dec 1995 06:16:29 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: julian@ref.tfs.com (Julian Elischer) Cc: terry@lambert.org, wollman@lcs.mit.edu, hackers@freebsd.org Subject: Re: ipx on 802.3 Message-ID: <199512060416.GAA12749@zibbi.mikom.csir.co.za> In-Reply-To: <199512052303.PAA09588@ref.tfs.com> from "Julian Elischer" at Dec 5, 95 03:03:39 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Yes it is possible to do both 802.3 and V2 on the same segment. You would use two (IPX) network addresses then, so that each has got its own logical net. (If you don't use different net adddresses hosts on the same segment but using different LLCs won't be able to talk directly to each other. ) But even for that you need some way to tell the networking code in the kernel which net is on 802.3 and which on V2. IPX don't have ARP, so I'm not sure what you mean when you say it should be stored in the ARP entry. (One of the segments connected to our Novell server run both 802.3 and V2, but we don't do it on all the segments because it generate too much traffic with all IPX RIP and SAP packets going out twice over that interface.) John -- John Hay -- John.Hay@csir.co.za > > > This is absolutly rubis.. (not what terry or garret ar anyone else is > saying, but the whole thread....) > > LLC usage shoud depend on the destination.. > I've seen 802.3 and V2 used on the same segment.. > it should be stored in the ARP entry.. > and decided dynamically. > > > > > > Once in, another cleanup could be done. The hard part on the 802.3 LLC > > > > is codifying the state table. I've seen companies buy code from Microsoft > > > > and hack COFF objects from MSVC 2.x into something usable by GCC to get > > > > an 802.3 before. > > > > > > Which is just fine, since we already have 99% of what's needed > > > anyway. The original question, which you seem to have never grasped, > > > is: > > > > > > How can you tell an Ethernet interface to use 802.3 > > > encapsulation rather than Ethernet v2? > > > > > > Or, to spell it out more explicitly: > > > > > > How can you tell an Ethernet interface to send an 802.3-style > > > length field and 802.3-style LLC header rather than the > > > two-byte type field specified in Ethernet v2? > > > > By linking the encapsulation with the address family of the socket used > > to do the ioctl(). > > > > If you get a LINK1 on an AF_INET socket, it's a physical media select. > > > > If you get one on an AF_IPX socket, it's an LLC select. > > > > Means you can't do 802.3 with IP until the thing is fixed correctly, but > > since the 802.3 is being added for IPX, IP can wait. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512060416.GAA12749>