Date: Tue, 12 Mar 1996 09:06:19 -0700 From: Eric Varsanyi <ewv@boom.bsdi.com> To: hackers@freefall.freebsd.org Subject: Re: hackers-digest V1 #974 Message-ID: <199603121606.JAA14843@boom.vars.com> In-Reply-To: Your message of "Mon, 11 Mar 1996 23:24:27 PST." <199603120724.XAA10173@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Content-Type: text/plain; charset=us-ascii >> I am also thinking of really hooking the driver to the ethernet code >> and just convert tokenring<->ethernet in my driver. So to the machine >> it will look like this is an ethernet driver but to the network >> it will look like its a tokenring. >> >> Yaser Doleh You also need to deal with 802.5 source routing and the various flavors of broadcast on token ring (local ring, single-route, and all-routes). Token ring MAC headers are of variable length so it makes sense to create a new set of routines to deal with it (if_tokensubr.c for instance) instead of trying to use the ethernet routines and tranlate in the driver. An easy way to handle the source route<->IP mappings is to use arp to cache the source routes (don't forget to update the 'netstat' and 'arp' commands too). For arp on a multi-ring network it seems the best strategy is to cache the source route to the first reply received and ignore the next few (the first route found this way should be the shortest). - -Eric -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCVAgUBMUWg+jxFdSMFRIw5AQGifgP9HHmBRWJFPoKasEaymOZbT5TB+gTjm/z0 vhDQZ63HDyjhhdSSYBH8Vyuvht00PpI3m4XZkrcGWonil45zVgJBdVN+CmPDJwUk GhmAwzJBRGALZhRio1fD7zP7P4FEUTC64xOcIMQejyZ5AoZyBy5BmRGDb2uP493z hrEaJzOdTKk= =JZgk -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603121606.JAA14843>