Re: [LARTC] IMQ patch for 2.6.3 kernel

2004-03-05 Thread The Codrinus 

I encountered  errors with linux-2.6.2-imq-4.diff even if I marked both 
options as modules or not. But linux-2.6.4-rc2-imq-5.patch seems to be  
quite stable until now.

Codrin.

On Fri, 5 Mar 2004, Andre Correa wrote:

> 
> Sorry, but the patch is not broken. It compiles without errors. You just 
> have to choose the right options in your config:
> 
> CONFIG_IP_NF_TARGET_IMQ=y
> and
> CONFIG_IMQ=y
> 
> and avoid using modules.
> 
> Andre
> 
> 
> Marc-Christian Petersen wrote:
> > On Friday 05 March 2004 00:00, The Codrinus wrote:
> > 
> > Hi Codrin,
> > 
> > 
> >>I downloaded the latest imq patch for 2.6.x kernels from
> >>http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff
> >>I successfully applied the patch but when compiling IMQ I get the
> >>following error messages:
> >>What might be the problem ?
> > 
> > that patch is b0rked. Use attached one.
> > 
> > --
> > ciao, Marc
> > 
> > 
> > 
> > 
> > # 2.6.3-WOLK1.1
> > 
> > # Patch from: http://www.linuximq.net/
> > 
> > # Build fixes: me
> > 
> > diff -urN linux-2.6.orig/drivers/net/Kconfig linux-2.6.new/drivers/net/Kconfig
> > --- linux-2.6.orig/drivers/net/Kconfig  2004-01-21 19:33:36.0 +0100
> > +++ linux-2.6.new/drivers/net/Kconfig   2004-01-25 15:08:20.0 +0100
> > @@ -85,6 +85,20 @@
> >   To compile this driver as a module, choose M here: the module
> >   will be called eql.  If unsure, say N.
> >  
> > +config IMQ
> > +   tristate "IMQ (intermediate queueing device) support"
> > +   depends on NETDEVICES && NETFILTER
> > +   ---help---
> > + The imq device(s) is used as placeholder for QoS queueing disciplines.
> > + Every packet entering/leaving the ip stack can be directed through
> > + the imq device where it's enqueued/dequeued to the attached qdisc.
> > + This allows you to treat network devices as classes and distribute
> > + bandwidth among them. Iptables is used to specify through which imq
> > + device, if any, packets travel.
> > +
> > + To compile this driver as a module, choose M here: the module
> > + will be called imq.  If unsure, say N.
> > +
> >  config TUN
> > tristate "Universal TUN/TAP device driver support"
> > depends on NETDEVICES
> > diff -urN linux-2.6.orig/drivers/net/Makefile linux-2.6.new/drivers/net/Makefile
> > --- linux-2.6.orig/drivers/net/Makefile 2004-01-21 19:33:36.0 +0100
> > +++ linux-2.6.new/drivers/net/Makefile  2004-01-25 15:08:20.0 +0100
> > @@ -110,6 +110,7 @@
> >  endif
> >  
> >  obj-$(CONFIG_DUMMY) += dummy.o
> > +obj-$(CONFIG_IMQ) += imq.o
> >  obj-$(CONFIG_DE600) += de600.o
> >  obj-$(CONFIG_DE620) += de620.o
> >  obj-$(CONFIG_AT1500) += lance.o
> > diff -urN linux-2.6.orig/drivers/net/imq.c linux-2.6.new/drivers/net/imq.c
> > --- linux-2.6.orig/drivers/net/imq.c1970-01-01 01:00:00.0 +0100
> > +++ linux-2.6.new/drivers/net/imq.c 2004-01-25 15:08:51.0 +0100
> > @@ -0,0 +1,323 @@
> > +/*
> > + * Pseudo-driver for the intermediate queue device.
> > + *
> > + * This program is free software; you can redistribute it and/or
> > + * modify it under the terms of the GNU General Public License
> > + * as published by the Free Software Foundation; either version
> > + * 2 of the License, or (at your option) any later version.
> > + *
> > + * Authors:Patrick McHardy, <[EMAIL PROTECTED]>
> > + *
> > + *The first version was written by Martin Devera, <[EMAIL 
> > PROTECTED]>
> > + *
> > + * Credits:Jan Rafaj <[EMAIL PROTECTED]>
> > + *  - Update patch to 2.4.21
> > + * Sebastian Strollo <[EMAIL PROTECTED]>
> > + *  - Fix "Dead-loop on netdevice imq"-issue
> > + * Marcel Sebek <[EMAIL PROTECTED]>
> > + *  - Update to 2.6.2-rc1
> > + */
> > +
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#if defined(CONFIG_IPV6) || defined (CONFIG_IPV6_MODULE)
> > +#include 
> > +#endif
> > +#include 
> > +#include 
> > +
> > +static nf_hookfn imq_nf_hook;
>

Re: [LARTC] IMQ patch for 2.6.3 kernel

2004-03-05 Thread The Codrinus 

Marc,
I've just upgraded my kernel to 2.6.3 with the IMQ patch and it seems to 
be fine until now.

Thanks alot,
Codrin.

On Fri, 5 Mar 2004, Marc-Christian Petersen wrote:

> On Friday 05 March 2004 00:00, The Codrinus wrote:
> 
> Hi Codrin,
> 
> > I downloaded the latest imq patch for 2.6.x kernels from
> > http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff
> > I successfully applied the patch but when compiling IMQ I get the
> > following error messages:
> > What might be the problem ?
> that patch is b0rked. Use attached one.
> 
> --
> ciao, Marc
> 
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] IMQ patch for 2.6.3 kernel

2004-03-04 Thread The Codrinus 

Hi,
I downloaded the latest imq patch for 2.6.x kernels from 
http://www.linuximq.net/patchs/linux-2.6.2-imq-4.diff
I successfully applied the patch but when compiling IMQ I get the 
following error messages:

  CC  net/ipv4/netfilter/ipt_IMQ.o
net/ipv4/netfilter/ipt_IMQ.c: In function `imq_target':
net/ipv4/netfilter/ipt_IMQ.c:19: error: structure has no member named 
`imq_flags'
make[3]: *** [net/ipv4/netfilter/ipt_IMQ.o] Error 1
make[2]: *** [net/ipv4/netfilter] Error 2
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2

  CC [M]  drivers/net/imq.o
drivers/net/imq.c: In function `imq_skb_destructor':
drivers/net/imq.c:88: error: structure has no member named `nf_info'
drivers/net/imq.c: In function `imq_dev_xmit':
drivers/net/imq.c:106: error: structure has no member named `imq_flags'
drivers/net/imq.c:110: error: structure has no member named `nf_info'
drivers/net/imq.c: In function `imq_nf_queue':
drivers/net/imq.c:121: error: structure has no member named `imq_flags'
drivers/net/imq.c:129: error: structure has no member named `imq_flags'
drivers/net/imq.c:141: error: structure has no member named `nf_info'
drivers/net/imq.c: In function `imq_nf_hook':
drivers/net/imq.c:174: error: structure has no member named `imq_flags'
make[2]: *** [drivers/net/imq.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2

What might be the problem ?

Thank you,
Codrin.
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] IMQ patch for iptables-1.2.9 and kernel 2.6.2 final !

2004-02-19 Thread The Codrinus 

Roy,
 "But this stability is probably not because my code is better but  because 
 I don't use egress shaping so the crash reasons still unknown."

I need both ingress and egress traffic shaping, that's why I used the 
classic IMQ version.

> You can try my imq version, which dows not require paching anything
> 
> http://pupa.da.ru/imq
> and I think it should be more stable.
> >
> >
> > Hi,
> > I have successfully applied the IMQ patch for kernel-2.6.2 (final
> > release) from http://www.linuximq.net, and now I have support for 4 IMQ
> > devices loaded in kernel. But I don't know how to patch the iptables-1.2.9
> > to support the -j IMQ target. I tried the patch-o-matic for 2.4.x kernels,
> > but it doesn't work for 2.6.x kernels. I also tried the patch-o-matic-ng
> > for 2.6.x kernels, but when I give the batch script commands it says it's
> > not implemented yet. I don't know how to manually apply the IMQ patches.
> >
> > ./runme --batch userspace/IMQ.patch
> >
> > Could anyone help me how to do this final step and append IMQ support to
> > iptables?
> >
> > --
> -
> >
> > Hi again.
> > I manually patched in the iptables-1.2.9/extensions directory, the files:
> > .IMQ-test
> > .IMQ-test6
> > libip6t-IMQ.c
> > libipt-IMQ.c
> > from the pom-20030625.diff file, and it passed. Now I have the imq devices
> > up and running with kernel-2.6.2, but there is another problem: when I use
> > iptables . -j IMQ I got Segmentation fault, and dmesg says:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 0001
> >  printing eip:
> > c0372908
> > *pde = 18ddc067
> > Oops:  [#1]
> > CPU:0
> > EIP:0060:[]Not tainted
> > EFLAGS: 00010202
> > EIP is at imq_target+0x8/0x30
> > eax: 0001   ebx: c045f820   ecx: d8db7c04   edx: c045f820
> > esi: e08170f0   edi: e0817080   ebp: 0001   esp: d8db7b64
> > ds: 007b   es: 007b   ss: 0068
> > Process iptables (pid: 1648, threadinfo=d8db6000 task=d9e69900)
> > Stack: c03695ee d8db7c04 e0817080 e0817110 0004 0001 e0817080
> > d8db7ba8
> >d8db6000 deff9420 deff9480 0070   
> > 0163
> >      
> > 
> > Call Trace:
> >  [] translate_table+0x4be/0x760
> >  [] do_replace+0x193/0x6e0
> >  [] vfree+0x27/0x40
> >  [] do_ipt_set_ctl+0x6d/0x70
> >  [] nf_sockopt+0x12f/0x140
> >  [] nf_setsockopt+0x37/0x40
> >  [] ip_setsockopt+0x4a7/0xd90
> >  [] nf_sockopt+0xb4/0x140
> >  [] nf_getsockopt+0x37/0x40
> >  [] ip_getsockopt+0x681/0x7c0
> >  [] journal_stop+0x201/0x360
> >  [] ext3_mark_iloc_dirty+0x28/0x40
> >  [] ext3_mark_inode_dirty+0x50/0x60
> >  [] __ext3_journal_stop+0x24/0x50
> >  [] ext3_dirty_inode+0x69/0xd0
> >  [] __mark_inode_dirty+0xde/0xf0
> >  [] buffered_rmqueue+0xd1/0x170
> >  [] buffered_rmqueue+0xd1/0x170
> >  [] __alloc_pages+0x9f/0x330
> >  [] __alloc_pages+0x9f/0x330
> >  [] find_get_page+0x2c/0x60
> >  [] do_anonymous_page+0x17a/0x260
> >  [] do_no_page+0x65/0x3a0
> >  [] pte_alloc_map+0x9b/0xc0
> >  [] handle_mm_fault+0xd4/0x180
> >  [] do_page_fault+0x2fc/0x4dc
> >  [] inet_setsockopt+0x36/0x40
> >  [] sys_setsockopt+0x82/0xd0
> >  [] sys_socketcall+0x220/0x2a0
> >  [] sysenter_past_esp+0x52/0x71
> >
> > Code: 0f b6 00 8b 11 83 c8 80 88 82 94 00 00 00 8b 01 81 88 84 00
> >
> >
> > Does anybody know why it crashes and how can I handle this mess ?
>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] IMQ patch for iptables-1.2.9 and kernel 2.6.2 final !

2004-02-19 Thread The Codrinus 

> On Thursday 19 February 2004 17:19, The Codrinus wrote:
> > Hi,
> > I have successfully applied the IMQ patch for kernel-2.6.2 (final
> > release) from http://www.linuximq.net, and now I have support for 4 IMQ
> > devices loaded in kernel. But I don't know how to patch the iptables-1.2.9
> > to support the -j IMQ target. I tried the patch-o-matic for 2.4.x kernels,
> > but it doesn't work for 2.6.x kernels. I also tried the patch-o-matic-ng
> > for 2.6.x kernels, but when I give the batch script commands it says it's
> > not implemented yet. I don't know how to manually apply the IMQ patches.
> >
> > ./runme --batch userspace/IMQ.patch  
> >
> > Could anyone help me how to do this final step and append IMQ support to
> > iptables?
> I'm not sure, but I think you don't need iptables for the latest imq.  All
> traffic is also flowing thru the imq devices.  But I'm not sure.
>
> Stef
>

Well, iptables need in the extensions dir the following IMQ patch files:
".IMQ-test"
".IMQ-test6"
"libipt_IMQ.c" and 
"libip6t_IMQ.c"  
in order to support the -j IMQ --todev  option.

I manually added these files because the patch-o-matic-ng doesn't know how 
to apply --batch option. (not implemented yet)
The problem is after all, when I try to give an iptables command like:

iptables  -j IMQ --todev eth0 when running the patched kernel-2.6.2

i get segmentation fault and dmesg says the following coredump error:


Unable to handle kernel NULL pointer dereference at virtual address 
0001
 printing eip:
c0372908
*pde = 18ddc067
Oops:  [#1]
CPU:0
EIP:0060:[]Not tainted
EFLAGS: 00010202
EIP is at imq_target+0x8/0x30
eax: 0001   ebx: c045f820   ecx: d8db7c04   edx: c045f820
esi: e08170f0   edi: e0817080   ebp: 0001   esp: d8db7b64
ds: 007b   es: 007b   ss: 0068
Process iptables (pid: 1648, threadinfo=d8db6000 task=d9e69900)
Stack: c03695ee d8db7c04 e0817080 e0817110 0004 0001 e0817080
d8db7ba8
   d8db6000 deff9420 deff9480 0070   
0163
         

Call Trace:
 [] translate_table+0x4be/0x760
 [] do_replace+0x193/0x6e0
 [] vfree+0x27/0x40
 [] do_ipt_set_ctl+0x6d/0x70
 [] nf_sockopt+0x12f/0x140
 [] nf_setsockopt+0x37/0x40
 [] ip_setsockopt+0x4a7/0xd90
 [] nf_sockopt+0xb4/0x140
 [] nf_getsockopt+0x37/0x40
 [] ip_getsockopt+0x681/0x7c0
 [] journal_stop+0x201/0x360
 [] ext3_mark_iloc_dirty+0x28/0x40
 [] ext3_mark_inode_dirty+0x50/0x60
 [] __ext3_journal_stop+0x24/0x50
 [] ext3_dirty_inode+0x69/0xd0
 [] __mark_inode_dirty+0xde/0xf0
 [] buffered_rmqueue+0xd1/0x170
 [] buffered_rmqueue+0xd1/0x170
 [] __alloc_pages+0x9f/0x330
 [] __alloc_pages+0x9f/0x330
 [] find_get_page+0x2c/0x60
 [] do_anonymous_page+0x17a/0x260
 [] do_no_page+0x65/0x3a0
 [] pte_alloc_map+0x9b/0xc0
 [] handle_mm_fault+0xd4/0x180
 [] do_page_fault+0x2fc/0x4dc
 [] inet_setsockopt+0x36/0x40
 [] sys_setsockopt+0x82/0xd0
 [] sys_socketcall+0x220/0x2a0
 [] sysenter_past_esp+0x52/0x71

Code: 0f b6 00 8b 11 83 c8 80 88 82 94 00 00 00 8b 01 81 88 84 00


I really don't know why it crashes and how can I handle this mess,
Codrin.
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] IMQ patch for iptables-1.2.9 and kernel 2.6.2 final !

2004-02-19 Thread The Codrinus 


Hi,
I have successfully applied the IMQ patch for kernel-2.6.2 (final
release) from http://www.linuximq.net, and now I have support for 4 IMQ
devices loaded in kernel. But I don't know how to patch the iptables-1.2.9
to support the -j IMQ target. I tried the patch-o-matic for 2.4.x kernels,
but it doesn't work for 2.6.x kernels. I also tried the patch-o-matic-ng
for 2.6.x kernels, but when I give the batch script commands it says it's
not implemented yet. I don't know how to manually apply the IMQ patches.

./runme --batch userspace/IMQ.patch

Could anyone help me how to do this final step and append IMQ support to
iptables?

---

Hi again.
I manually patched in the iptables-1.2.9/extensions directory, the files:
.IMQ-test
.IMQ-test6
libip6t-IMQ.c
libipt-IMQ.c
from the pom-20030625.diff file, and it passed. Now I have the imq devices
up and running with kernel-2.6.2, but there is another problem: when I use
iptables . -j IMQ I got Segmentation fault, and dmesg says:

Unable to handle kernel NULL pointer dereference at virtual address 
0001
 printing eip:
c0372908
*pde = 18ddc067
Oops:  [#1]
CPU:0
EIP:0060:[]Not tainted
EFLAGS: 00010202
EIP is at imq_target+0x8/0x30
eax: 0001   ebx: c045f820   ecx: d8db7c04   edx: c045f820
esi: e08170f0   edi: e0817080   ebp: 0001   esp: d8db7b64
ds: 007b   es: 007b   ss: 0068
Process iptables (pid: 1648, threadinfo=d8db6000 task=d9e69900)
Stack: c03695ee d8db7c04 e0817080 e0817110 0004 0001 e0817080 
d8db7ba8
   d8db6000 deff9420 deff9480 0070    
0163
          

Call Trace:
 [] translate_table+0x4be/0x760
 [] do_replace+0x193/0x6e0
 [] vfree+0x27/0x40
 [] do_ipt_set_ctl+0x6d/0x70
 [] nf_sockopt+0x12f/0x140
 [] nf_setsockopt+0x37/0x40
 [] ip_setsockopt+0x4a7/0xd90
 [] nf_sockopt+0xb4/0x140
 [] nf_getsockopt+0x37/0x40
 [] ip_getsockopt+0x681/0x7c0
 [] journal_stop+0x201/0x360
 [] ext3_mark_iloc_dirty+0x28/0x40
 [] ext3_mark_inode_dirty+0x50/0x60
 [] __ext3_journal_stop+0x24/0x50
 [] ext3_dirty_inode+0x69/0xd0
 [] __mark_inode_dirty+0xde/0xf0
 [] buffered_rmqueue+0xd1/0x170
 [] buffered_rmqueue+0xd1/0x170
 [] __alloc_pages+0x9f/0x330
 [] __alloc_pages+0x9f/0x330
 [] find_get_page+0x2c/0x60
 [] do_anonymous_page+0x17a/0x260
 [] do_no_page+0x65/0x3a0
 [] pte_alloc_map+0x9b/0xc0
 [] handle_mm_fault+0xd4/0x180
 [] do_page_fault+0x2fc/0x4dc
 [] inet_setsockopt+0x36/0x40
 [] sys_setsockopt+0x82/0xd0
 [] sys_socketcall+0x220/0x2a0
 [] sysenter_past_esp+0x52/0x71

Code: 0f b6 00 8b 11 83 c8 80 88 82 94 00 00 00 8b 01 81 88 84 00


Does anybody know why it crashes and how can I handle this mess ?

thank you,
Codrin.
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] test

2004-02-19 Thread The Codrinus 
test

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] Question about iptables and maximum file size

2003-10-31 Thread The Codrinus 

Hi,
I would like to know if there is any possibility to select from iptables  the 
files with maximum size of 300 kbytes and send them to a proxy server.
As I know until now you can only mark files with maximum size of 64 kbytes.

thank you in advance,
Codrin.

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] IMQ technical question

2003-09-11 Thread The Codrinus 

How many IMQ queueing devices you may have ? I've patched the 2.4.21 
kernel and I have by default 2 devices: imq0 and imq1 !

regards,
Codrin.

___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[LARTC] IMQ and kernel-2.4.22

2003-09-01 Thread The Codrinus 

Hi,
does anyone know if IMQ can be installed on linux kernel-2.4.22 ?
The latest version until now it seems to be IMQ patch against linux 2.4.21
and when I tried to apply the patch to 2.4.22 I've got some errors.

regards,
Codrin.


___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/