From: Harald Welte <laforge@netfilter.org>
To: Yong Li <sdssly@sina.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipq_set_verdict problem in bridge+iptables
Date: Mon, 14 Jul 2003 10:07:28 +0200 [thread overview]
Message-ID: <20030714080728.GF6538@naboo> (raw)
In-Reply-To: <001901c348ec$6dbbc5d0$e84ce9db@win2ken>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Sun, Jul 13, 2003 at 11:11:16AM +0800, Yong Li wrote:
> Hello All,
>
> I encountered a problem with the ipq_set_verdict function. I want to modify
> the packet content and size using the ipq_set_verdict function. However, I
> found I cannot change the IP packet size more than 400+ bytes. Is it a known
> issue?
what do you mean by 'I cannot' ? What happens? Is an error returned to
the ipq_set_verdict() call? Is the packet silently discarded? Is the
packet truncated?
Anyway, it should work. But if you exceed the outgoing interface's MTU,
I could imagine that no fragmentation happens...
> Thanks in advance!
> Yong
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-14 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030712222620.28732.48265.Mailman@kashyyyk>
2003-07-13 3:11 ` ipq_set_verdict problem in bridge+iptables Yong Li
2003-07-14 8:07 ` Harald Welte [this message]
[not found] ` <001c01c34a6f$97af4fe0$8501a8c0@dev>
2003-07-15 3:24 ` Yong
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=20030714080728.GF6538@naboo \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sdssly@sina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.