Transmission of token-ring packets over ethernet by tunneling

Claim 3

The method of claim 1 wherein the associating step includes the further step of padding the second network protocol compatible data portion with null bits until the second network protocol compatible packet is compatible with second network protocol size requirements.

Claim 4

The method of claim 2 wherein the second network protocol segment is connected to a third segment running the first network protocol, and including the further step of modifying the header portion of the second network protocol compatible packet to generate a header that is compatible with the first network protocol, removing any existing padding bits from the data portion and transmitting a resultant second network protocol compatible packet on the third segment.

Claim 5

The method of claim 1 including the further step of preserving source routing information from the header portion of the first network protocol packet in the modified header.

Claim 6

The method of claim 1 wherein the modifying step includes the further step of storing the priority bits of the Frame Control field in the VLAN Identification field.

Claim 7

The method of claim 5 wherein the modifying step includes the further step of reversing the order of each bit in each byte of the Destination Address field of the first network protocol packet to provide the Destination Address field of the second network protocol compatible packet.

Claim 8

The method of claim 6 wherein the modifying step includes the further step of removing the Routing Information Indicator from the Source Address field and reversing the order of each remaining bit in each byte of the Source Address field to create the modified Source Address field.

Claim 9

The method of claim 7 wherein the modifying step includes the further step of adding the VLAN Type field.

Claim 10

The method of claim 8 wherein the modifying step includes the further step of adding the VLAN Identification field.

Claim 11

The method of claim 9 wherein the modifying step includes the further step of adding the Length field.

Claim 12

The method of claim 10 wherein the modifying step includes the further step of determining whether the first network protocol packet is source routed.

Claim 13

The method of claim 11 wherein the first network protocol packet includes a Routing Information Field with a route control field and route descriptor fields, and the modifying step includes the further step of employing the route control field of the Routing Information Field as the Route Control field of the second network protocol packet and employing the route descriptors of the Routing Information field as the Route Descriptor field of the second network protocol packet, provided the first network protocol packet is determined to be source routed.

Claim 14

The method of claim 11 wherein the modifying step includes the further step of employing the Routing Information Indicator of the first network protocol packet Source Address field to generate the Route Control field of the second network protocol packet, provided the first network protocol packet is determined not to be source routed.

Claim 15

The method of claim 13 wherein the employing step includes the further step of generating a three bit broadcast indicator field to indicate whether the first network protocol packet is source routed.

Claim 16

The method of claim 11 wherein the modifying step includes the further step of removing the Frame Check Sequence field and generating the new Frame Check Sequence field.

Claim 19

The method of claim 16 wherein the associating step includes the further step of padding the Ethernet compatible Information field with null bits until the Ethernet compatible packet is compatible with Ethernet minimum size requirements.

Claim 20

The method of claim 16 including the further step of preserving source routing information from the header portion of the Token Ring packet in the Ethernet compatible header.

Claim 21

The method of claim 18 wherein the Ethernet network segment is connected to a third segment running the Token Ring network protocol, and including the further step of modifying the header portion of the Ethernet compatible packet to generate a header that is compatible with the Token Ring network protocol, removing any existing padding bits from the Information field and transmitting a resultant Token Ring network protocol compatible packet on the third segment.

Claim 22

The method of claim 16, wherein the modifying step includes the further step of storing the at least three priority bits of the Frame Control field in the VLAN Identification field and then removing the Frame Control field.

Claim 23

The method of claim 20 wherein the modifying step includes the further step of reversing the order of each bit within each byte of the Token Ring Destination Address field to create the Destination Address field of the Ethernet compatible packet.

Claim 24

The method of claim 21 wherein the modifying step includes the further step of removing the Routing Information Indicator from the Source Address field and reversing the order of each remaining bit of the Source Address field to create the modified Source Address field.

Claim 25

The method of claim 22 wherein the modifying step includes the further step of adding the VLAN Type field.

Claim 26

The method of claim 23 wherein the modifying step includes the further step of adding the VLAN Identification field.

Claim 27

The method of claim 24 wherein the modifying step includes the further step of adding the Length field.

Claim 28

The method of claim 25 wherein the modifying step includes the further step of determining whether the Token Ring packet is source routed.

Claim 29

The method of claim 26 wherein the Token Ring packet includes a Routing Information Field with a route control field and route descriptor fields, and the modifying step includes the further step of employing the route control field of the Routing Information Field as the Route Control field of the Ethernet compatible packet and employing the route descriptors of the Routing Information field as the Route Descriptor field of the Ethernet compatible packet, provided the Token Ring packet is determined to be source routed.

Claim 30

The method of claim 26 wherein the modifying step includes the further step of employing the Routing Information Indicator of the Token Ring packet Source Address field to generate the Route Control field of the Ethernet compatible packet, provided the Token Ring packet is determined not to be source routed.

Claim 31

The method of claim 26 wherein the employing step includes the further step of generating a three bit broadcast indicator field to indicate whether the Token Ring packet is source routed.

Claim 32

The method of claim 29 wherein the modifying step includes the further step of removing the Frame Check Sequence field and generating the new Frame Check Sequence field.

Claim 33

An interface circuit having a driver for creating an Ethernet compatible packet from a Token Ring packet from a Token Ring network segment for transmission on an Ethernet network segment containing Ethernet packets, the Token Ring packet including an information field and a header portion with an Access Control field, a Frame Control field with at least three priority bits, a Destination Address, a Source Address field with a Routing Information Indicator bit and a Frame Check Sequence field, comprising: a first function that modifies the Token Ring header portion to generate a modified header portion that is Ethernet compatible, the modified header including a modified Source Address field, a VLAN Identification field, a Length field, a Route Control field, a Route Descriptor field, a new Frame Check Sequence field, and a VLAN type field, the VLAN type field having a predetermined value stored therein, the predetermined value indicating that the Ethernet compatible packet has been converted from the Token Ring packet, and wherein the first function removes the Access Control field from the Token Ring packet; wherein the first function pads the Ethernet compatible Information field with null bits until the Ethernet compatible packet is compatible with Ethernet minimum size requirements; a second function that preserves the Information field of the Token Ring packet as an Ethernet compatible Information field; and a third function that associates the modified header portion with the Ethernet compatible Information field to generate an Ethernet compatible packet, whereby the Ethernet compatible packet may be transmitted on the Ethernet network segment and coexist with native Ethernet packets.

Claim 34

An interface circuit having a driver for creating an Ethernet compatible packet from a Token Ring packet from a Token Ring network segment for transmission on an Ethernet network segment containing Ethernet packets, the Token Ring packet including an information field and a header portion with an Access Control field, a Frame Control field with at least three priority bits, a Destination Address, a Source Address field with a Routing Information Indicator bit and a Frame Check Sequence field, comprising: a first function that modifies the Token Ring header portion to generate a modified header portion that is Ethernet compatible, the modified header including a modified Source Address field, a VLAN Identification field, a Length field, a Route Control field, a Route Descriptor field, a new Frame Check Sequence field, and a VLAN type field, the VLAN type field having a predetermined value stored therein, the predetermined value indicating that the Ethernet compatible packet has been converted from the Token Ring packet, and wherein the first function removes the Access Control field from the Token Ring packet; wherein the first function pads the Ethernet compatible Information field with null bits until the Ethernet compatible packet is compatible with Ethernet minimum size requirements; a second function that preserves the Information field of the Token Ring packet as an Ethernet compatible Information field; and a third function that associates the modified header portion with the Ethernet compatible Information field to generate an Ethernet compatible packet, whereby the Ethernet compatible packet may be transmitted on the Ethernet network segment and coexist with native Ethernet packets.

Claim 35

The interface circuit of claim 31 wherein the first function stores the at least three priority bits of the Frame Control field in the VLAN Identification field and then removes the Frame Control field.

Claim 36

The interface circuit of claim 32 wherein the first function reverses the order of each bit in each byte of the Destination Address field of the Token Ring packet to create the Destination Address field of the Ethernet compatible packet.

Claim 37

The interface circuit of claim 33 wherein the first function removes the Routing Information Indicator from the Source Address field and reverses the order of each remaining bit of the Source Address field to create the modified Source Address field.

Claim 38

The interface circuit of claim 34 wherein the first function creates the VLAN Type field.

Claim 39

The interface circuit of claim 35 wherein the first function creates the VLAN Identification field.

Claim 40

The interface circuit of claim 36 wherein the first function creates the Length field.

Claim 41

The interface circuit of claim 37 wherein the first function determines whether the Token Ring packet is source routed.

Claim 42

The interface circuit of claim 38 wherein the Token Ring packet includes a Routing Information Field with a route control field and route descriptor fields, and the first function employs the route control field of the Routing Information Field as the Route Control field of the Ethernet compatible packet and employs the route descriptors of the Routing Information field as the Route Descriptor field of the Ethernet compatible packet, provided the Token Ring packet is determined to be source routed.

Claim 43

The interface circuit of claim 39 wherein the first function employs the Routing Information Indicator of the Token Ring packet Source Address field to generate the Route Control field of the Ethernet compatible packet, provided the Token Ring packet is determined not to be source routed.

Claim 44

The interface circuit of claim 40 wherein the first function generates a three bit broadcast indicator field to indicate whether the Token Ring packet is source routed.

Claim 45

The interface circuit of claim 41 wherein the first function removes the Frame Check Sequence field and generates the new Frame Check Sequence field.

Claim 46

The interface circuit of claim 31 wherein the Ethernet network segment is connected to a third segment running the Token Ring network protocol, and wherein the third segment includes a driver which modifies the header portion of the Ethernet compatible packet to generate a header that is compatible with the Token Ring network protocol and removes any existing padding bits from the Information field.