Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm trying to find out if Iptables supports creating jitter, like it does for packet loss. I'm using 'iptables -A INPUT -m statistic --mode random --probability 0.02 -j DROP' to simulate packet loss, but can I do something similar to create jitter? I think TC will do it, but our firmware does not support it. If there is an alternate solution, any advice would be greatly appreciated.
I've already proposed that, but since these devices have 3 logical zones, each having it's own IP Address, sharing/crossing an internal switch on the MB, going out one shared interface, and our firmware does not support TC, we cannot test between each zone's IP Address, unless we come up with another solution, like iptables doing delay/jitter, like it simulates packet loss. The only thing I've found, is somehow writing a script that that will support using iptables to simulate delay/jitter. I've tried to explain to my Boss, that it doesn't matter testing from zone to zone, and an inline device simulating packet loss & jitter between the devices interfaces will be fine. I'm sure he just wants to be extra sure. Can you see any reason why it would be necessary to test from IP to IP, when it's all one shared interface? Thanks for you help!
You may have explained why it doesn't matter testing from zone to zone to your boss but not to us. So until you do, and preferably in a detailed way outlining components that could pose problems (or not) and therefore should be tested (or not), there is no need for me to come up with any reasons why it would be necessary to test from IP to IP (or not). Or am I mistaken about how things usually work?
I don't (well, not w/o using NFQUEUE). If you must ensure there isn't a way then do search the Netfilter framework source code and mailing list archives and ask on the iptables users / developer mailing list.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.