From: "Sumit Pandya" <sumit@elitecore.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] HTB/IMQ with GRE bug
Date: Wed, 30 Oct 2002 09:17:00 +0000 [thread overview]
Message-ID: <marc-lartc-103596887712082@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103589548430225@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Hi All,
Mails from Patrick's account is bouncing back. Does anyone knows his
alternative mail address?
-- Sumit
> -----Original Message-----
> From: devik [mailto:devik@cdi.cz]
>
>
> > [root@linux /root]# dmesg
> > ... ... ...
> > NET: XXX messages suppressed.
> > Dead loop on virtual device gre1, fix it urgently!
>
> Hmm. I heard about these. They are IMQ related - you have
> to bother Patrick.
>
> > class htb 1:35 parent 1:2 leaf 35: prio 0 rate 1Kbit ceil
> 64Kbit burst 1600b
> > cburst 1680b
> > becouse of that I get following message on console
> > ... ... ...
> > Oct 29 17:30:12 1035892812 kernel: HTB: quantum of class 10057 is small.
> > Consider r2q change.
> > Oct 29 17:31:08 1035892868 kernel: NET: 17 messages suppressed.
>
> 1kbit is WAY to small and it is hard to find correct quantum for it.
> Specify "quantum 500" on the line to get rid of the message.
>
> devik
>
[-- Attachment #2: Type: message/rfc822, Size: 4497 bytes --]
From: "Sumit Pandya" <sumit@elitecore.com>
To: <lartc@mailman.ds9a.nl>
Cc: <devik@cdi.cz>, "Patrick McHardy" <kaber@trash.net>
Subject: HTB/IMQ with GRE bug
Date: Tue, 29 Oct 2002 18:11:53 +0530
Message-ID: <NDBBKOCLFLKJBBJIHCODCELLCDAA.sumit@elitecore.com>
Hi Devik/Patrik,
In setting up IMQ/HTB with a GRE Tunnel I'm constantly getting kernel
errors:
[root@linux /root]# dmesg
... ... ...
NET: XXX messages suppressed.
Dead loop on virtual device gre1, fix it urgently!
... ... ...
This I get only if I'm going to start cross device b/w control. If I remove
iptables rule
iptables -t mangle -D POSTROUTING -j IMQ
then no such warning messages :O.
An information to this is in my all class I'm using very low rate and rely
on ceil parameter of htb... example of one such class is
class htb 1:35 parent 1:2 leaf 35: prio 0 rate 1Kbit ceil 64Kbit burst 1600b
cburst 1680b
becouse of that I get following message on console
... ... ...
Oct 29 17:30:12 1035892812 kernel: HTB: quantum of class 10057 is small.
Consider r2q change.
Oct 29 17:31:08 1035892868 kernel: NET: 17 messages suppressed.
... ... ...
This I didnot think a serious matter as in your code you yourself concern
and at run time adjust that parameter and also this works with ethernet
without any problem but while using gre I get dangerous(seems to be)
warnings flooding up.
Any Idea about this? I'm using RedHat release kernel-2.4.18-3 with your
patches
imq-2.4.18.diff-10.txt and htb3.6_2.4.17.diff
In case if you need my detail network setup configuration...
My Tunnel configurations are following
LOCAL-IP=202.LLL.IP.148
REMOTE-IP=202.RRR.IP.4
TUNNEL-IP=202.TUN.IP.254
[root@linux /root]# route -n
202.LLL.IP.148 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
202.INT.IP.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
202.RRR.IP.0 202.LLL.IP.147 255.255.255.248 UG 0 0 0 eth1
202.LLL.IP.144 0.0.0.0 255.255.255.248 U 0 0 0 eth1
202.INT.IP.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 202.TUN.IP.254 0.0.0.0 UG 0 0 0 gre1
[root@linux /root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:4B:50:04:7B
inet addr:202.INT.IP.1 Bcast:202.INT.IP.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1116522 errors:0 dropped:0 overruns:0 frame:0
TX packets:853832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10
eth1 Link encap:Ethernet HWaddr 00:00:4B:50:05:73
inet addr:202.LLL.IP.148 Bcast:202.LLL.IP.151 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1182092 errors:0 dropped:0 overruns:0 frame:2
TX packets:984484 errors:0 dropped:0 overruns:0 carrier:1106
collisions:10090 txqueuelen:100
Interrupt:12 Base address:0x2000
gre0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:1476 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
gre1 Link encap:UNSPEC HWaddr
CA-B7-46-94-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:202.TUN.IP.254 P-t-P:202.TUN.IP.254 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:1476 Metric:1
RX packets:78208 errors:0 dropped:0 overruns:0 frame:0
TX packets:105391 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
imq0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:2914477 errors:0 dropped:0 overruns:0 frame:0
TX packets:2914470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:30
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:32921 errors:0 dropped:0 overruns:0 frame:0
TX packets:32921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Thanks for your time.
-- Sumit
next prev parent reply other threads:[~2002-10-30 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 12:53 [LARTC] HTB/IMQ with GRE bug Sumit Pandya
2002-10-29 15:23 ` devik
2002-10-30 9:17 ` Sumit Pandya [this message]
2002-10-30 9:52 ` devik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103596887712082@msgid-missing \
--to=sumit@elitecore.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.