I have included a patch that adds Cisco ISL support to the ethernet bridge
code. When I first debugged it I had to make changes to ip_output.c and
netfilter_bridge.h to leave room for the ISL header. The changes to
ip_output.c I got from looking at the 2.6 changes and tweeking them a bit.
On Fri, 22 Jul 2005 15:13:33 + (UTC)
Joy Leima <[EMAIL PROTECTED]> wrote:
> Lukasz,
>
> I think I have a fix for you. Verify for me that it is the same
> problem. Send a large UDP packet through the bridge. I believe the
> problem is the ip_fragment code is not taking into account the
On Fri, 22 Jul 2005 15:13:33 + (UTC)
Joy Leima [EMAIL PROTECTED] wrote:
Lukasz,
I think I have a fix for you. Verify for me that it is the same
problem. Send a large UDP packet through the bridge. I believe the
problem is the ip_fragment code is not taking into account the VLAN
I have included a patch that adds Cisco ISL support to the ethernet bridge
code. When I first debugged it I had to make changes to ip_output.c and
netfilter_bridge.h to leave room for the ISL header. The changes to
ip_output.c I got from looking at the 2.6 changes and tweeking them a bit.
Lukasz Spaleniak wroc.zigzag.pl> writes:
>
> On Wednesday, July 20, 2005, 9:44:57 PM, Willy Tarreau wrote:
> changed. At least it should have been oopsing from day one.
> It is strange to me too. There is no dependency when it happens.
> Sometimes traffic is small, sometimes it's normal.
Lukasz Spaleniak lspaleniak at wroc.zigzag.pl writes:
On Wednesday, July 20, 2005, 9:44:57 PM, Willy Tarreau wrote:
changed. At least it should have been oopsing from day one.
It is strange to me too. There is no dependency when it happens.
Sometimes traffic is small, sometimes it's
On Wednesday, July 20, 2005, 9:44:57 PM, Willy Tarreau wrote:
> Hello,
Hello Willy,
> just some basic questions :
> - did your configuration change before the oopses started ? (eg: new
> matches, etc...)
One new machine appears but it generates small traffic rate (by now
it's almost
Hello,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
- did the traffic change recently (protocols, data rate) ? eg: new
applications on the network, etc...
- is it possible that it's being targetted by an attack
Hello,
I have bridge firewall (linux box) with three fast ethernet cards (one
rtl8139 for management and two e100 for bridge). It is running 2.4.31
kernel and iptables v1.2.11. It works ok about one month. Few weeks
ago It started ooopsing. First thought was hardware, but it was
replaced with a
Hello,
I have bridge firewall (linux box) with three fast ethernet cards (one
rtl8139 for management and two e100 for bridge). It is running 2.4.31
kernel and iptables v1.2.11. It works ok about one month. Few weeks
ago It started ooopsing. First thought was hardware, but it was
replaced with a
Hello,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
- did the traffic change recently (protocols, data rate) ? eg: new
applications on the network, etc...
- is it possible that it's being targetted by an attack
On Wednesday, July 20, 2005, 9:44:57 PM, Willy Tarreau wrote:
Hello,
Hello Willy,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
One new machine appears but it generates small traffic rate (by now
it's almost unused).
12 matches
Mail list logo
