Transmission of token-ring packets over ethernet by tunneling

• US 5,999,541 A
• Filed: 02/28/1997
• Issued: 12/07/1999
• Est. Priority Date: 02/28/1997
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Mancour, Timothy A., Hinchey, Kevin
• Primary Examiner(s): Pham, Chi H.
• Assistant Examiner(s): YAO, KWANG BIN
• Application Number:
  US08/807,267
• Time in Patent Office: 1,012 Days
• Field of Search: 370/389, 370/392, 370/401, 370/402, 370/403, 370/404, 370/405, 370/465, 370/466, 370/467, 370/469, 370/470, 370/474, 395/200.6, 395/200.61, 395/200.62, 395/200.66, 395/200.68, 395/200.75, 395/200.76, 395/200.79, 395/200.81
• US Class Current: 370/466
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Token Ring network packet having a header and an information field is prepared for transmission over an Ethernet network by the steps of removing the header information from the Token Ring packet, and associating a second header with the information field of the Token Ring packet, wherein the second header is compatible with the Ethernet network. More particularly, to prepare an IEEE 802.5 Token Ring network packet for transmission on an Ethernet network the Access Control ("AC") and Frame Control ("FC") fields are removed, the order of the destination address ("DA") field is reversed, the order of the source address ("SA") field is reversed, a Virtual Local Area Network ("VLAN") type field is added, a VLAN identification ("ID") field is added, and a length value field is added. The information field from the Token Ring packet is retained. However, if the newly formed tunneled packet would otherwise be smaller than the minimum size for an Ethernet packet the information field may be padded with null bits until the minimum size for an Ethernet packet is achieved.

Claims

1. A method for converting a first network protocol packet to a second network protocol compatible packet for transmission on a second network protocol segment running a second network protocol, comprising:

modifying a header portion of the first network protocol packet to generate a modified header that is compatible with the second network protocol, wherein the header portion of the first network protocol packet includes an Access Control field, a Frame Control field with at least three priority bits, a Source Address field with a Routing Information Indicator bit and a first Frame Check Sequence field, and wherein the modified header includes 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 second network protocol compatible packet has been converted from the first network protocol packet, and wherein the modifying step includes removing the Access Control field from the header portion of the first network protocol packet;

preserving the data portion of the first network protocol packet as the data portion of the second network protocol compatible packet; and

associating the modified header with the second network protocol compatible packet data portion to generate the second network protocol compatible packet,

whereby the second network protocol compatible packet may be transmitted on the second network protocol segment.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

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

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

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

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

12. 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.

13. 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.

14. 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.

15. 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.

16. A method for conveying a Token Ring packet from a Token Ring network segment to an Ethernet network segment containing a plurality of Ethernet packets each with a respective destination address field by generating an Ethernet compatible packet from the Token Ring packet, 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 field, a Source Address field with a Routing Information Indicator bit and a first Frame Check Sequence field, comprising the steps of:

modifying 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, wherein the VLAN type field includes 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 modifying step includes removing the Access Control field from the Token Ring packet;

preserving the Information field of the Token Ring packet as an Ethernet compatible Information field;

associating the modified header portion with the Ethernet compatible Information field to generate the Ethernet compatible packet; and

transmitting the Ethernet compatible packet on the Ethernet network segment.

17. 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.

18. 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.

19. 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.

20. 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.

21. 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.

22. 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.

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

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

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

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

27. 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.

28. 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.

29. 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.

30. 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.

31. 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.

32. 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.

33. 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.

34. 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.

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

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

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

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

39. 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.

40. 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.

41. 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.

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

43. 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.