| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Hi there
I have a customer hwho has moved there rarp server onto fddi
it is an ultrix system but the same is for dec-unix. the rarpd
uses the packet filter. I have changed the daemon to filter for
fddi frames but find that my response on the ethernet side looks
like an 802.3 frame - i was hoping for ethernet.
i am going through a decswitch 900-ef ( i think ). The protocol
on ethernet rarp request is like
ddeessttiinnssoouurrccee8035and then rarp stuff
so on fddi in packet filter it becomes
00000050ddeessttiinnssoouurrcceeAAAA030000008035and then the rarp stuff
fC oui = 00-00-00
I send out my packet as
00000050ddeessttiinnssoouurrcceeAAAA030000008035 rarp response
and on ethernet I get
ddeessttiinnssoouurrccee0021000...000 and then middle of rarp stuff
I don't have a trace here and can't be sure how many zeros
but it looks to me like the packet on ethernet
is 802.3 with 0s fo snap-sap control oui type
My nieve assumption was to just send the same format out as came in
so I have a couple of questions
will our fddi bridges put out ethernet ( as opposed to 802.3 )
packets - I assume so ?
should I send out using "bridge tunnel" oui ?
because after this one is solved he wants his appletalk to work too?
A supplementary question
I though that a 00-00-00 oui in a snap-sap frame (aa-aa) should
become ethernet frames on the exit lan ??
thanks for the impending laughter
chow
Tom King MCS Sydney.
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1784.1 | this is what I saw and sent !! | GIDDAY::KING | ..and then there were two.. | Fri Aug 18 1995 05:15 | 25 |
FDDI
Received
00 00 00 50 ff ff ff ff ff ff aa 00 04 00 87 ee aa aa 03 00 00 00 80 35 \
00 01 08 00 06 04 00 03 aa 00 04 00 87 ee 00 00 00 00 aa 00 04 00 87 ee \
00 ...
I sent
00 00 00 50 aa 00 04 00 87 ee 08 00 2b b0 9d 07 aa aa 03 00 00 00 80 35 \
00 01 08 00 06 04 00 04 08 00 2b b0 9d 07 10 99 20 42 aa 00 04 00 87 ee \
10 99 20 4b 00 ...
I looked at the source to if_ethersubr.c on osf
it does the test
if (LLC_IS_ENCAP_ETHER(ll))
type = ntohs(l->llc_snap.ether_type);
so I checked in my program and it should work.
e.g. in dbx
(dbx) print l->llc_un.type_snap.ether_type
0x3580
bummer!!
I am using a decbridge 900 MX with
sw v1.5.0 and hw v0/2 and ro v0.2
digital unix 3.2 with a defta card
| |||||