From: Harsh <hanemade@gmail.com>
To: Neema <neema.network@gmail.com>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: help in using eth_change_mtu
Date: Tue, 25 Jan 2005 11:50:06 +0530 [thread overview]
Message-ID: <cfc9593605012422204db19d04@mail.gmail.com> (raw)
In-Reply-To: <41F5C109.7060801@gmail.com>
Hello ,
Extra info mean IPSEC headers. How can they sent in
2.4.24 kernel? where can i find Packets being using IPSEC headers and
is that require to reduce MTU by AH/ESP header bytes???
Also can you tellme in which condition eth_change_mtu used?
reagards,
Harsh.
On Tue, 25 Jan 2005 09:16:17 +0530, Neema <neema.network@gmail.com> wrote:
> Hi,
>
> What ever u may send,the maximum size of the packet in ethernet
> should be 1514bytes, that includes ethernet header (And also minimum is
> 82bytes).
> I think u are using old libnet version. That function sets the MTU with
> the given value if neither exceeded max and nor minimum.
>
> HTH,
> Neema
>
> Harsh wrote:
>
> >Hello,
> > If some extra information is required to be sent with each
> >packet then does that require to change Ethernet MTU 1500 to
> >1500-(Bytes in extra info) or its ok with 1500 value of MTU? While
> >checking source code of net_init.c in drivers/net dir i found one
> >function eth_change_mtu. I want to know does that helps? why its given
> >there in source code?
> >regards,
> >Harsh.
> >
> >static int eth_change_mtu(struct net_device *dev, int new_mtu)
> > {
> > if ((new_mtu < 68) || (new_mtu > 1500))
> > return -EINVAL;
> > dev->mtu = new_mtu;
> > return 0;
> > }
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-net" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> >
> >
>
> --
>
> Thanks & Regards,
> Neema
>
>
prev parent reply other threads:[~2005-01-25 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 8:59 help in using eth_change_mtu Harsh
2005-01-25 3:46 ` Neema
2005-01-25 6:20 ` Harsh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfc9593605012422204db19d04@mail.gmail.com \
--to=hanemade@gmail.com \
--cc=linux-net@vger.kernel.org \
--cc=neema.network@gmail.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).