similar to: [Bridge] [RELEASE] ebtables-brnf vs 2.4.20 try 2

Displaying 20 results from an estimated 10000 matches similar to: "[Bridge] [RELEASE] ebtables-brnf vs 2.4.20 try 2"

2007 Apr 18
1
[Bridge] [RELEASE] ebtables-brnf-3-vs-2.4.22 and ebtables-2-0-6
Hi, At http://sourceforge.net/projects/ebtables/ you can find the following new releases: ebtables-brnf-3-vs-2.4.22 Changes: - let iptables see VLAN tagged IP traffic - bugfix for queued packets that get mangled in userspace - ebt_among module (Grzegorz Borowiak) - ebt_limit module (Tom Marshall) The patch compiles but I've done no further tests, but I probably didn't screw up.
2007 Apr 18
0
[Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz
On Friday 01 August 2003 15:07, Cezary Sydlo wrote: > Hi, > > tried it ... patch works fine but "make xconfig" does not anymore :-( It's know bug. (was described in the ebtables-user@ maillist) Here is the correct piece of net/ipv4/netfilter/Config.in ... if [ "$CONFIG_BRIDGE" != "n" ]; then dep_tristate ' Physdev match support'
2007 Apr 18
4
[Bridge] ebtables target to disable an interface
I would like to set up an ACL for an ethernet port using ebtables rules, and if a security violation occurs, to physically disable the port (i.e. whatever "ifconfig down" does). I did not see such a feature in the ebtables man page. Does this exist anywhere, or do I have to create a new extension for it? -- Dan Eble <dane@aiinet.com> _____ . | _
2007 Apr 18
0
[Bridge] ebtables
Hi Stephen, Thanks for your prompt response. What I wanted to tell was: the following cmd DOES NOT WORK..(here 0x828 is my protocol no. that encapsulates the IP data, like VLAN) ebtables -A INPUT -p 0x828 -j DROP BUT the following does work... ebtables -A INPUT -p 0x800 -j DROP So, ebtables is not seeing the frame before decapsulation. For that as Bart schuymer said I need to register my
2007 Apr 18
0
[Bridge] [EBTABLES][PATCH] fix gcc format warning
Hi Dave, Please apply this compiler warning fix from Randy. Signed-off-by: Bart De Schuymer <bdschuym@telenet.be> Signed-off-by: Randy Dunlap <rddunlap@osdl.org> diff -Naurp ./net/bridge/netfilter/ebt_ulog.c~brnetf_types ./net/bridge/netfilter/ebt_ulog.c --- ./net/bridge/netfilter/ebt_ulog.c~brnetf_types 2005-01-10 10:38:40.531343592 -0800 +++ ./net/bridge/netfilter/ebt_ulog.c
2007 Apr 18
2
[Bridge] Bridge Problem with RedHat and iptables
Hello, I am running into a strange problem here. I wrote you a mail earlier also regarding this. 1. I am trying to run the bridge mode over Redhat 7.3 (kernel 2.4.18). I tried the latest version of brdige mode utility and also I tried version 0.94 as well. But whenever I run the brdige mode on this kernel - the kernel goes panic saying "aiee - killing interrupt handler". Now I am in a
2007 Apr 18
4
[Bridge] [PATCH/RFC] Let {ip, arp}tables "see" bridged VLAN tagged {I, AR}P packets
Hi all, The patch below does four trivial changes and one big change Trivial changes, these are all in br_netfilter.c: - check ar_pln==4 when giving bridged ARP packets to arptables - delete unnecessary if in br_nf_local_in - add more logging for the "Argh" message - add some brag-comments in the file head comment Big change: let {ip,arp}tables see VLAN tagged {I,AR}P packets. This
2007 Apr 18
2
[Bridge] IPv6 + ip6tables packet bridging?
Hiyas, Is there a patch for the 2.4.x series to do ip6tables bridging of IPv6 packets? I was unable to go to 2.6 due to issues with large packets so still living in 2.4 land. If there are no patches, any ideas on what gets patched in IPv4 to allow this bridging? -Scott __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
2007 Apr 18
2
[Bridge] Re: [RESEND][PATCH] ebtables: clean up vmalloc usage in net/bridge/netfilter/ebtables.c
An earlier variant of your patch was applied already, included below. You'll need to submit the newer parts relative to the current tree. diff-tree 7ad4d2f6901437ba4717a26d395a73ea362d25c6 (from b8282dcf0417bbc8a0786c129fdff9cc768f8f3c) Author: Jayachandran C <c.jayachandran@gmail.com> Date: Tue Apr 11 17:25:38 2006 -0700 [BRIDGE] ebtables: fix allocation in
2023 Sep 08
1
[Bridge] [PATCH AUTOSEL 4.14 6/8] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.5 33/45] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.1 20/26] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.4 30/41] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 5.10 11/14] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 5.15 12/15] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2007 Apr 18
0
[Bridge] Re: [Ebtables-user] Trying to do gigabit bridging+firewalling
On Monday 29 September 2003 20:44, DarthPeter wrote: > Hi everyone, Hello, I'm CC-ing the bridge mailing list since there are more people on that one and they might be able to shed more light. > We are trying to build a powerful firewall that could handle > several hundred megabits of traffic and we are running into a problem > with it. We'd like to be able to accomplish
2023 Aug 16
0
[Bridge] [PATCH net-next v4] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to ?__read_overflow2_field? declared with attribute warning: detected read beyond
2023 Aug 16
1
[Bridge] [PATCH net-next v2] netfilter: ebtables: replace zero-length array members
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> As suggested by Kees[1], replace the old-style 0-element array members of multiple structs in ebtables.h with modern C99 flexible array. [1]: https://lore.kernel.org/all/5E8E0F9C-EE3F-4B0D-B827-DC47397E2A4A at kernel.org/ Link: https://github.com/KSPP/linux/issues/21 Signed-off-by: GONG, Ruiqi <gongruiqi1 at huawei.com>
2007 Apr 18
5
[Bridge] Any way of knowing a packet's been defragmented
Hello, Due to a recent change in the bridge code, we now need a way of knowing if a packet has been defragmented. The bridge code now checks on the packet size and drops packets that are too big for the output port. Defragmented packets will get refragmented later, so they shouldn't be dropped. I've been reading the defragmentation code and can't find an easy way of knowing if a
2007 Apr 18
1
[Bridge] ebtables configuration in 2.6.8 kernel
Hi everyone, I am working on packet filtering at mac layer. I want to use ebtables. I am using Fedora core 2. But I am unable use the ebtables eventhough all the modules are enabled at the time of kernel compilation. Plz suggest me how to use ebtables in Fedora core 2 Phani