Re: Please confirm (conf#249b47a782d5839462c69c1bfc940fc9)

On Mon, Nov 22, 2010 at 9:48 PM, Cisco certification <ccielab_at_groupstudy.com
> wrote:

> Hi,
>
> You have tried to post to a GroupStudy.com certification mailing list.
> Because
> the server does not recognize you as a confirmed poster, you will be
> required
> to authenticate that you are using a valid e-mail address and are not a
> spammer. By confirming this e-mail you certify that you are not sending
> Unsolicited Bulk Email (UBE).
>
> PLEASE DO NOT SEND YOUR ORIGINAL MESSAGE AGAIN! BY CONFIRMING THIS EMAIL
> YOUR ORIGINAL MESSAGE (WHICH IS NOW QUEUED IN THE SERVER) WILL BE POSTED.
>
>
> By confirming this e-mail you also certify the following:
>
> 1. The message does NOT break Cisco's Non-Disclosure requirements.
>
> 2. The message is NOT designed to advertise a commercial product.
>
> 3. You understand all postings become property of GroupStudy.com
>
> 4. You have searched the archives prior to posting.
>
> 5. The message is NOT inflammatory.
>
> 6. The message is NOT a test message.
>
> To confirm, simply reply to this message. No editing is necessary. Once
> confirmed, you will be able to post without additional confirmations.
>
>
> Welcome to GroupStudy.com!
>
>
> First time posters to GroupStudy.com are required to agree to the
> GroupStudy terms and conditions.
> Replying to this email, certifies you have read and agree to the GroupStudy
> posting guidelines and terms and conditions.
>
> --- Original Message Follows ---
>
> Date: Mon, 22 Nov 2010 21:48:01 +0100
> Subject: Calculating L2 encap overload
> From: Jakub Drwal <jakub.drwal_at_gmail.com>
> To: ccielab_at_groupstudy.com
>
> Hello,
>
> Is there any way to discover l2 overhead just by sitting on the router and
> try some debug commands?
> If we send ip packet and we know its size, if we receive it on the second
> side on the link and see its size with l2 overhead, it would be more than
> simple to calculate how much does it take.
>
> For example, i've been trying to ping one router from another through the
> HDLC connection:
>
> #ping 1.1.1.2 size 100 repeat 1
> (so we know, that we want to send 100 bytes of data, one packet)
>
> on the other side i just did debug ip packet on according acl, but what i
> saw was:
>
> *Nov 22 20:43:49.292: IP: s=1.1.1.1 (Serial0/1/0), d=1.1.1.2, len 100,
> input
> feature, MCI Check(63), rtype 0, forus FALSE, sendself FALSE, mtu 0
> *Nov 22 20:43:49.292: IP: tableid=0, s=1.1.1.1 (Serial0/1/0), d=1.1.1.2
> (Serial0/1/0), routed via RIB
> *Nov 22 20:43:49.292: IP: s=1.1.1.1 (Serial0/1/0), d=1.1.1.2 (Serial0/1/0),
> len 100, rcvd 3
> *Nov 22 20:43:49.292: IP: s=1.1.1.1 (Serial0/1/0), d=1.1.1.2, len 100, stop
> process pak for forus packet
>
> But it also shows length of 100. :/
> Is there any way to see it?
>
> regards,
>
> --
> Jakub Drwal
>
>
>
>

-- 
Jakub Drwal
Blogs and organic groups at http://www.ccie.net