Cezary Sydlo | 1 Aug 10:45 2003
Picon

[Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz

Hi,

how do i have to apply this patch to the kernel?
I tried and had a lot of errors.
The configure scripts did not work any more after this ...

Greetings
Cezary
Gavin Hamill | 1 Aug 11:13 2003
Picon

Re: [Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz

On Friday 01 August 2003 9:45 am, Cezary Sydlo wrote:
> Hi,
>
> how do i have to apply this patch to the kernel?

Are you using a kernel 2.4.21 source from kernel.org, or perhaps a RedHat or 
SuSE 'tweaked' kernel source?

If it's just a vanilla kernel, then it should just be a matter of doing

$ cd /path/to/patch/directory
$ gunzip ebtables-brnf-2_vs_2.4.21.diff.gz
$ cd /usr/src/your-kernel-source-2.4.21-directory
$ patch -p1 </path/to/patch/directory/ebtables-brnf-2_vs_2.4.21.diff

If that still fails, please paste the output from the 'patch' command! :)

Cheers,
Gavin.
Cezary Sydlo | 1 Aug 13:07 2003
Picon

Re: [Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz

Hi,

tried it ... patch works fine but "make xconfig" does not anymore :-(

i applied it to a 2.4.21 kernel from kernel.org ...
what do i make wrong?

Thanks

> If that still fails, please paste the output from the 'patch' command! :)
> 
> Cheers,
> Gavin.

rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory `/usr/src/linux-2.4.21/scripts'
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
net/ipv4/netfilter/Config.in: 47: can't handle
dep_bool/dep_mbool/dep_tristate condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.21/scripts'
make: *** [xconfig] Error 2

Greetings
Cezary
Gavin Hamill | 1 Aug 13:33 2003
Picon

Re: [Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz

On Friday 01 August 2003 12:07 pm, Cezary Sydlo wrote:
> Hi,
>
> tried it ... patch works fine but "make xconfig" does not anymore :-(
>
> i applied it to a 2.4.21 kernel from kernel.org ...
> what do i make wrong?

Ah, I've never used make xconfig, since I configure for servers, and servers 
obviously don't need X installed... 

Of course, you're probably compiling on another machine - could you try 'make 
menuconfig' instead?  That certainly worked for me.

Cheers,
Gavin.
Brad Morgan | 1 Aug 15:31 2003
Picon
Picon

RE: [Bridge] How to apply the patch ebtables-brnf-2_vs_2.4.21.diff.gz

I had this same problem but if you edit net/ipv4/netfilter/Config.in: 47:
you will see the obvious problem.  It needs one more entry on the line.

Exactly what should be there is unknown, but I copied the last entry from a
similar line nearby and could at least make xconfig without error.

Sorry to be so vague but the machine where I fixed this is down for a few
days as we are moving.

Regards,

Brad

> -----Original Message-----
> From: bridge-bounces <at> math.leidenuniv.nl [mailto:bridge-
> bounces <at> math.leidenuniv.nl] On Behalf Of Cezary Sydlo
> Sent: Friday, August 01, 2003 5:08 AM
> Cc: bridge <at> math.leidenuniv.nl
> Subject: Re: [Bridge] How to apply the patch ebtables-brnf-
> 2_vs_2.4.21.diff.gz
> 
> Hi,
> 
> tried it ... patch works fine but "make xconfig" does not anymore :-(
> 
> i applied it to a 2.4.21 kernel from kernel.org ...
> what do i make wrong?
> 
> Thanks
> 
(Continue reading)

Bart De Schuymer | 1 Aug 20:43 2003
Picon

Re: [Bridge] Using IPChains with the bridging in linux 2.4

On Thursday 31 July 2003 23:51, Shawn Zhou wrote:
> We know ipchains can be used in linux 2.4 if we unload the iptables
> related modules and load the ipchains module.
>
> It can be used in linux 2.2 with the bridging. But I can't find any
> document talking about using that with the linux bridging
>
> Feature in linux 2.4. No kernel patches are found for that.

I don't think there will ever be a patch for this.

cheers,
Bart
Shawn Zhou | 5 Aug 20:14 2003

[Bridge] the "netfilter(firewalling) support" option

Hi all,

I tried to install the firewall bridging in Red Hat 8.0. The linux
2.4.19 kernel is downloaded and extracted. And I did :

Patch -p1<bridge-nf-0.0.7-against-2.4.19.diff

Everything looks fine. No errors. But when I do makemenuconfig, I cannot
find the "netfiler(firewalling) support" option under the Network
Options or under the 

802.1d Ethernet Bridging which is marked.  I have already marked the
Network packet filtering option and also marked any item under the
Netfilter Configuration. Does anybody know what's the reason?

Thanks,

Shawn
Eble, Dan | 7 Aug 22:44 2003

[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 <at> aiinet.com>  _____  .
                           |  _  |/|
Applied Innovation Inc.    | |_| | |            "All Protocols MUST be odd"
http://www.aiinet.com/     |__/|_|_|              -- RFC 1661 (PPP)
Nick Fedchik | 1 Aug 15:29 2003
Picon

Re: [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 <at>  maillist)

Here is the correct piece of net/ipv4/netfilter/Config.in
...
if [ "$CONFIG_BRIDGE" != "n" ]; then
    dep_tristate '  Physdev match support' CONFIG_IP_NF_MATCH_PHYSDEV 
$CONFIG_IP_NF_IPTABLES
  fi
...
Just add $CONFIG_IP_NF_IPTABLES at the end of line 47.

--

-- 
Best regards, Nick Fedchik
http://www.fedchik.org.ua
Bart De Schuymer | 8 Aug 01:14 2003
Picon

[Bridge] [ANNOUNCE] ebtables + bridge-nf patch 3 for 2.4.21

It's available at the usual place.
Change: remove vlan patch from Bassem Armanyous. Kernel oopses were reported 
in kernels that have an unloaded but compiled vlan module.
I currently lack the time to figure out the solution, so for now it's removed.
If you're not getting an oops, there is no need to switch from patch 2 to the 
new patch (3).

cheers,
Bart

Gmane