From: Todor Todorov <root@4vendeta.com>
To: Patrick McHardy <kaber@trash.net>,
netfilter@vger.kernel.org, kadlec@netfilter.org, fw@strlen.de,
marc+nf@mbsi.ca, gandalf@netfilter.org, yasuyuki@netfilter.org
Subject: Re: SYNPROXY module with bridge
Date: Sun, 05 Apr 2015 15:52:10 +0300 [thread overview]
Message-ID: <55212FFA.9050204@4vendeta.com> (raw)
In-Reply-To: <20150405114729.GC23433@acer.localdomain>
Hello,
I was check and as you said REJECT target also doesn't work in Bridge.
Where is the problem - in "br.c" or it must add a check in
"ipt_synproxy.c" for is the packet coming from bridged interface?
I find this patch for reject in bridge but doesn't work -
http://markmail.org/message/zkd57gfh7htcbyvc#query:+page:1+mid:spwhgpx2jl6iholn+state:results
Any help would be useful to me...
Thank you!
----------------------------
Kind regards,
Todor Todorov
System Administrator
4 Vendeta LTD
GSM: +359 895 935 835
root@4vendeta.com
----------------------------
На 05.4.2015 г. в 14:47, Patrick McHardy написа:
> On 04.04, Todor Todorov wrote:
>> Hello,
>>
>> From 1 week ago I'm trying to patch synproxy module to work in bridge mode.
>> The problem is that SYNPROXY is not send syn-ack by bridge, its send by
>> default route.
>> I know roughly C language but failed to rewrite and work..
>>
>> This is the topology of the problem:
>>
>> User -----> SYN ------> Firewall - br0 - physdev vlan10
>> Firewall - eth0? -------> SYN-ACK ------> User
>>
>> Should be like:
>>
>> Firewall - br0 - physdev vlan10 -------> SYN-ACK ------> User
>>
>> Please help or some guidance on how to fix this problem.
> You should have a look at the REJECT target, which faces the same problem.
> Also please CC the netfilter-devel list on questions like that, someone
> might jump in to help.
parent reply other threads:[~2015-04-05 12:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150405114729.GC23433@acer.localdomain>]
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=55212FFA.9050204@4vendeta.com \
--to=root@4vendeta.com \
--cc=fw@strlen.de \
--cc=gandalf@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@netfilter.org \
--cc=marc+nf@mbsi.ca \
--cc=netfilter@vger.kernel.org \
--cc=yasuyuki@netfilter.org \
/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