All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] imq problem
@ 2003-02-06 17:23 Robert Penz
  2003-02-06 17:42 ` Robert Penz
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: Robert Penz @ 2003-02-06 17:23 UTC (permalink / raw)
  To: lartc

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I've running imq on some servers and it works everywhere except the new
machine I just try to set up.

on that machine I get that

tsunami:/usr/src# iptables -t mangle -A PREROUTING -i eth0 -j IMQ
iptables: No chain/target/match by that name

for testing I've added an 1 and get that

tsunami:/usr/src# iptables -t mangle -A PREROUTING -i eth0 -j IMQ1
iptables v1.2.6a: Couldn't load target `IMQ1':/lib/iptables/libipt_IMQ1.so:
cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.

here what I've done plus an strace, I don't have a clue what I did wrong,
works on an other debian woody machine so it can't a dist. problem.

tsunami:/usr/src# tar xvzf libipt_IMQ-1.2.6a.tar.gz -C /lib/iptables
libip6t_IMQ.so
libipt_IMQ.so
tsunami:/usr/src# strace iptables -t mangle -A PREROUTING -i eth0 -j IMQ
execve("/sbin/iptables", ["iptables", "-t", "mangle", "-A", "PREROUTING",
"-i", "eth0", "-j", "IMQ"], [/* 16 vars */]) = 0
uname({sys="Linux", node="tsunami", ...}) = 0
brk(0)                                  = 0x8056a5c
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_sizes40, ...}) = 0
old_mmap(NULL, 7340, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40014000
close(3)                                = 0
open("/lib/libdl.so.2", O_RDONLY)       = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0T\27\0\000"..., 1024)
= 1024
fstat64(3, {st_mode=S_IFREG|0644, st_size€08, ...}) = 0
old_mmap(NULL, 11004, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40016000
mprotect(0x40018000, 2812, PROT_NONE)   = 0
old_mmap(0x40018000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x1000) = 0x40018000
close(3)                                = 0
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\30\222"..., 1024) 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size\x1153784, ...}) = 0
old_mmap(NULL, 1166560, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40019000
mprotect(0x4012c000, 40160, PROT_NONE)  = 0
old_mmap(0x4012c000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x113000) = 0x4012c000
old_mmap(0x40132000, 15584, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40132000
close(3)                                = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 0x40136000
munmap(0x40014000, 7340)                = 0
brk(0)                                  = 0x8056a5c
brk(0x8056a8c)                          = 0x8056a8c
brk(0x8057000)                          = 0x8057000
open("/lib/iptables/libipt_IMQ.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\4\0\000"..., 1024) 1024
fstat64(3, {st_mode=S_IFREG|0775, st_size815, ...}) = 0
old_mmap(NULL, 6076, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40014000
mprotect(0x40015000, 1980, PROT_NONE)   = 0
old_mmap(0x40015000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0)
= 0x40015000
close(3)                                = 0
socket(PF_INET, SOCK_RAW, IPPROTO_RAW)  = 3
getsockopt(3, SOL_IP, 0x40 /* IP_??? */, [1735287149], [84]) = 0
brk(0x8058000)                          = 0x8058000
getsockopt(3, SOL_IP, 0x41 /* IP_??? */, [1735287149], [2340]) = 0
brk(0x8059000)                          = 0x8059000
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, [1735287149], 2544) = -1 ENOSYS
(Function not implemented)
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, [1735287149], 2544) = -1 ENOSYS
(Function not implemented)
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, [1735287149], 2544) = -1 ENOENT (No
such file or directory)
write(2, "iptables: No chain/target/match "..., 45iptables: No
chain/target/match by that name
) = 45
_exit(1)                                = ?


and the module is loaded

tsunami:/usr/src# lsmod
Module                  Size  Used by    Not tainted
ipt_limit                960   1  (autoclean)
ipt_REJECT              2816   1  (autoclean)
ipt_mac                  672   1  (autoclean)
ipt_LOG                 3168   2  (autoclean)
ipt_state                608   7  (autoclean)
ipt_MARK                 800   2  (autoclean)
iptable_mangle          2208   1  (autoclean)
iptable_nat            13876   0  (autoclean) (unused)
iptable_filter          1728   1  (autoclean)
imq                     1880   1
ip_conntrack_ftp        3776   0  (unused)
ip_conntrack           16652   3  [ipt_state iptable_nat ip_conntrack_ftp]
ip_tables              10400  11  [ipt_limit ipt_REJECT ipt_mac ipt_LOG
ipt_state ipt_MARK iptable_mangle iptable_nat iptable_filter]
cls_fw                  2016   2  (autoclean)
sch_sfq                 3424   4  (autoclean)
sch_htb                18080   2  (autoclean)


system data:  debian woody with an 2.4.20 patched with imq-2.4.18.diff-10 AND 
(= tried both) imq-2.4.18.diff-combo-6 (extracted the source for each patch), 
it doesn't work with any of them



- --
Regards,
Robert
- ----------------
Robert Penz
robert.penz AT outertech.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+QpoK8tTsQqJDUBMRAtpfAJ9HMKFiAtKwoE66rCPKkVBXVGFQPQCdE9po
hP+ea9gB7p5w9AjylBuWxeY=yPa6
-----END PGP SIGNATURE-----

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [LARTC] imq problem
  2003-02-06 17:23 [LARTC] imq problem Robert Penz
@ 2003-02-06 17:42 ` Robert Penz
  2003-09-09  6:29 ` [LARTC] IMQ problem michal
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Robert Penz @ 2003-02-06 17:42 UTC (permalink / raw)
  To: lartc

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 06 February 2003 18:23, Robert Penz wrote:

argh, found my mistake, I've forgotten the "IMQ target support"  

- -- 
Regards,
Robert
- ----------------
Robert Penz
robert.penz AT outertech.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+Qp538tTsQqJDUBMRAplUAKCiMFEZPNyOKvm6SC/R1HDwVxeMhQCeNdPp
GcC6g4BOhV3EDuCsjBXkMbg\bSq
-----END PGP SIGNATURE-----

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [LARTC] IMQ problem
  2003-02-06 17:23 [LARTC] imq problem Robert Penz
  2003-02-06 17:42 ` Robert Penz
@ 2003-09-09  6:29 ` michal
  2003-09-09 15:19 ` Stef Coene
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: michal @ 2003-09-09  6:29 UTC (permalink / raw)
  To: lartc

Hi,
I tried to make IMQ device to work... So I patched the kernel, patched iptables,
made all the stuff, boot to new kernel was ok, module imq was there and it was
ok to load it and 'ip link imq0 up' also worked and imq0 was present in ifconfig
listing. Unitil imq0 was inactive everything was clear and stable.

BUT: Anytime I redirected any traffic to imq0 (with the iptables ... -j IMQ
comand), then the kernel crashed with "Kernal panic!" message.... 

kernel 2.4.21 patched with linux-2.4.21-imq-1.diff
iptables 1.2.8 patched via patch-o-matic-20030107 with pom-20030625.diff

Any tips, hints or whatever?? 

Thanks, Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [LARTC] IMQ problem
  2003-02-06 17:23 [LARTC] imq problem Robert Penz
  2003-02-06 17:42 ` Robert Penz
  2003-09-09  6:29 ` [LARTC] IMQ problem michal
@ 2003-09-09 15:19 ` Stef Coene
  2003-09-10 16:02 ` Toshiro Viera
  2003-09-10 17:38 ` Stef Coene
  4 siblings, 0 replies; 6+ messages in thread
From: Stef Coene @ 2003-09-09 15:19 UTC (permalink / raw)
  To: lartc

On Tuesday 09 September 2003 08:29, michal@jursa.cz wrote:
> Hi,
> I tried to make IMQ device to work... So I patched the kernel, patched
> iptables, made all the stuff, boot to new kernel was ok, module imq was
> there and it was ok to load it and 'ip link imq0 up' also worked and imq0
> was present in ifconfig listing. Unitil imq0 was inactive everything was
> clear and stable.
>
> BUT: Anytime I redirected any traffic to imq0 (with the iptables ... -j IMQ
> comand), then the kernel crashed with "Kernal panic!" message....
>
> kernel 2.4.21 patched with linux-2.4.21-imq-1.diff
> iptables 1.2.8 patched via patch-o-matic-20030107 with pom-20030625.diff
>
> Any tips, hints or whatever??
I don't know if it's the case, but never give the imq device an ip address.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [LARTC] IMQ problem
  2003-02-06 17:23 [LARTC] imq problem Robert Penz
                   ` (2 preceding siblings ...)
  2003-09-09 15:19 ` Stef Coene
@ 2003-09-10 16:02 ` Toshiro Viera
  2003-09-10 17:38 ` Stef Coene
  4 siblings, 0 replies; 6+ messages in thread
From: Toshiro Viera @ 2003-09-10 16:02 UTC (permalink / raw)
  To: lartc

> > I tried to make IMQ device to work... So I patched the kernel, patched
> > iptables, made all the stuff, boot to new kernel was ok, module imq was
> > there and it was ok to load it and 'ip link imq0 up' also worked and imq0
> > was present in ifconfig listing. Unitil imq0 was inactive everything was
> > clear and stable.
> >
> > BUT: Anytime I redirected any traffic to imq0 (with the iptables ... -j IMQ
> > comand), then the kernel crashed with "Kernal panic!" message....
> >
> > kernel 2.4.21 patched with linux-2.4.21-imq-1.diff
> > iptables 1.2.8 patched via patch-o-matic-20030107 with pom-20030625.diff
> >
> > Any tips, hints or whatever??
> I don't know if it's the case, but never give the imq device an ip address.

I've been having the same problems (I've also posted it to this list
with no success). I've noticed that (at least for me) the kernel panics
when I try to shape both incoming and outgoing traffic using the same
imq device, if I shape only incoming traffic, everything's OK.

If you find out something, please let me know.

-- 
Toshiro Viera <tviera@arnaldocastro.com.uy>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [LARTC] IMQ problem
  2003-02-06 17:23 [LARTC] imq problem Robert Penz
                   ` (3 preceding siblings ...)
  2003-09-10 16:02 ` Toshiro Viera
@ 2003-09-10 17:38 ` Stef Coene
  4 siblings, 0 replies; 6+ messages in thread
From: Stef Coene @ 2003-09-10 17:38 UTC (permalink / raw)
  To: lartc

On Wednesday 10 September 2003 18:02, Toshiro Viera wrote:
> > > I tried to make IMQ device to work... So I patched the kernel, patched
> > > iptables, made all the stuff, boot to new kernel was ok, module imq was
> > > there and it was ok to load it and 'ip link imq0 up' also worked and
> > > imq0 was present in ifconfig listing. Unitil imq0 was inactive
> > > everything was clear and stable.
> > >
> > > BUT: Anytime I redirected any traffic to imq0 (with the iptables ... -j
> > > IMQ comand), then the kernel crashed with "Kernal panic!" message....
> > >
> > > kernel 2.4.21 patched with linux-2.4.21-imq-1.diff
> > > iptables 1.2.8 patched via patch-o-matic-20030107 with
> > > pom-20030625.diff
> > >
> > > Any tips, hints or whatever??
> >
> > I don't know if it's the case, but never give the imq device an ip
> > address.
>
> I've been having the same problems (I've also posted it to this list
> with no success). I've noticed that (at least for me) the kernel panics
> when I try to shape both incoming and outgoing traffic using the same
> imq device, if I shape only incoming traffic, everything's OK.
>
> If you find out something, please let me know.
Mhh.  I can remember me a problem with spaping in and outgoing traffic with 
the same imq device.  But I thought it was solved in the latest imq release.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-09-10 17:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-06 17:23 [LARTC] imq problem Robert Penz
2003-02-06 17:42 ` Robert Penz
2003-09-09  6:29 ` [LARTC] IMQ problem michal
2003-09-09 15:19 ` Stef Coene
2003-09-10 16:02 ` Toshiro Viera
2003-09-10 17:38 ` Stef Coene

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.