Re: Ether Type and Protocol Type

Good question.
Logically speaking there is no need for the protocol identifier to be 94 if
its IP in IP ;)

http://www.cloudshark.org/captures/b3aa8046f410

Best Regards,
Tharak Abraham Luke

On Thu, Dec 29, 2011 at 12:35 PM, Routing Freak <routingfreak_at_gmail.com>wrote:

> Hi Abraham,
>
> I guess IP within IP protocol number is 94 dude.
>
> I have seen in the table where i can see 94 is the protocol number for IP
> over IP encapsulation and not 4 .Correct me if a m wrong
>
>
>
>
> On Thu, Dec 29, 2011 at 12:24 PM, CCIE KID <eliteccie_at_gmail.com> wrote:
>
>> Hi Abraham Thank u for the link.
>>
>> One question is when there are two tags in Q in Q, What will be the TPID
>> for the outer tag and inner tag
>>
>> I guess the outer TAG has a tag protocol identifier of 9100 and the inner
>> vlan TAG has TPID of 8100 .
>>
>> So i am not very sure that this may be true.
>>
>> i guess 8100 is used for a single tag and 9100 is used for Q in Q tag :)
>>
>> So the outer tag has TPID of 9100 and inner tag has TPDI of 8100
>>
>>
>> On Thu, Dec 29, 2011 at 12:08 PM, Abraham, Tharak <
>> tharakabraham_at_gmail.com> wrote:
>>
>>> The value of TPID for Q in Q depends on the stack implementation from
>>> different vendors
>>> For Eg: Alcatel and Juniper uses 0x9100 and Cisco uses 0x8100
>>>
>>> In the case of IP in IP the Protocol number would be 4, which denotes
>>> IPv4
>>>
>>> http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml
>>>
>>> You may have to g00gle for more details and for other specific info.
>>>
>>> Best Regards,
>>> Tharak Abraham Luke
>>>
>>>
>>> On Wed, Dec 28, 2011 at 10:25 PM, Routing Freak <routingfreak_at_gmail.com
>>> >wrote:
>>>
>>> > Hi all
>>> >
>>> > When will u find the ether type as Dot 1Q (0x8100) and Q in Q
>>> (0x9100)
>>> >
>>> > Wat s the protocol field in IP header when the payload it carries is
>>> also
>>> > another IP header ( in case of IP in IP tunnel).
>>> >
>>> > Can anyone send me a link for different values of protocol types ?
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Dec 27, 2011 at 3:16 AM, Jochen Bartl <jochen.bartl_at_gmail.com
>>> > >wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > my preferred way for getting answers to those questions is watching
>>> > > frames/packets in Wireshark. If the Wireshark code of a particular
>>> > > protocol is not broken, it is a very convenient way to find out about
>>> > > the truth ;-)
>>> > > Sample capture files for the protocols you have mentioned are
>>> > > available on the following sites:
>>> > >
>>> > > http://packetlife.net/captures/ (Direct links to CloudShark)
>>> > > - Example:
>>> > >
>>> >
>>> http://www.cloudshark.org/view?url=http://packetlife.net/captures/802.1Q_tunneling.cap
>>> > > * Ethernet(eth-type 0x8100)/802.1q (TPID 0x8100)/802.1q (TPID
>>> > > 0x8000)/IPv4 (proto 1)/ICMP
>>> > > http://wiki.wireshark.org/SampleCaptureshttp://pcapr.net/
>>> > >
>>> > > Best regards,
>>> > >
>>> > > Jochen
>>> >
>>> >
>>> > Blogs and organic groups at http://www.ccie.net
>>> >
>>> > _______________________________________________________________________
>>> > Subscription information may be found at:
>>> > http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> With Warmest Regards,
>>
>> CCIE KID
>> CCIE#29992 (Security)

Blogs and organic groups at http://www.ccie.net
Received on Thu Dec 29 2011 - 18:54:31 ART