Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi
Last month on my ISP router I moved with queueing from IMQ to IFB (for incoming traffic on eth1 LAN interface). Everything seems to working fine however I noticed that when queueing is enabled on eth1 (LAN) interface which ifb0 is connected to there is a gradually increasing number of TX dropped packets. It looks like below. Is it normal behavior for queueing mechanisms for doing this or this is a problem of too small socket buffers? How to fix that?
Code:
root@access1:~# netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 1596046184 1 1992 0 1048035349 0 0 0 BMRU
eth1 1500 0 1112127683 6 0 0 1610512236 0 0 0 BMRU
eth0.6 1500 0 994109903 0 0 0 1036972784 0 0 0 BMRU
eth0.6:1 1500 0 - no statistics available - BMRU
eth0.6:2 1500 0 - no statistics available - BMRU
eth0.6:3 1500 0 - no statistics available - BMRU
eth0.6:4 1500 0 - no statistics available - BMRU
eth0.6:5 1500 0 - no statistics available - BMRU
eth1.8 1500 0 26630 0 0 0 25235 0 0 0 BMRU
eth1.10 1500 0 100159397 0 0 0 79595979 0 16306 0 BMRU
eth1.10:1 1500 0 - no statistics available - BMRU
eth1.10:2 1500 0 - no statistics available - BMRU
eth1.20 1500 0 97316370 0 0 0 93154573 0 21278 0 BMRU
eth1.20:1 1500 0 - no statistics available - BMRU
eth1.20:2 1500 0 - no statistics available - BMRU
eth1.100 1500 0 354601567 0 2 0 320990005 0 36936 0 BMRU
eth1.100:1 1500 0 - no statistics available - BMRU
eth1.180 1500 0 110145136 0 0 0 125649429 0 46503 0 BMRU
eth1.180:1 1500 0 - no statistics available - BMRU
eth1.190 1500 0 3000576 0 0 0 2994657 0 0 0 BMRU
eth1.200 1500 0 392698570 0 0 0 415288471 0 59740 0 BMRU
eth1.200:1 1500 0 - no statistics available - BMRU
ifb0 1500 0 1054757621 0 0 0 1054757621 0 0 0 BORU
lo 65536 0 2 0 0 0 2 0 0 0 LRU
There is no such thing as burst in hfsc. Moreover it (the problem) doesn't appear while using IMQ instead of IFB so it's not the matter od queueuing mechanism.
No, it't not the matter of hfsc, because it was moved from my previous system intact. I would rather change system buffers, but I like ask someone if it will help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
