adel75

it looks like it is a bug in iperf3 with some queuing mechanism. iperf2 doesn't show these packet losses.

yes. that's fully reproductible. every time. with the commands i provided.

that's for the ERL (Edge Router Lite) not the ERX.

EDIT: it looks like it is a bug in iperf3 with some queuing mechanism. iperf2 doesn't show these packet losses. Hi, i am doing some testing on an R1 perf wise. - R1 is plugged to a ERX. - i'm behind a 1Gbit/s FTTH. - NO CONGESTION CONTROL ans TURBO AND SUPERTURBO Configured. when behind R1 testing at 12Mbps UDP: @home:~$ iperf3 -c ping.online.net -u -b 12000000 -p 5202 Connecting to host ping.online.net, port 5202 [ 4] local 192.168.118.200 port 51312 connected to 62.210.18.40 port 5202 [ ID] Interval Transfer Bandwidth Total Datagrams .. .. - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-10.00 sec 14.2 MBytes 11.9 Mbits/sec 1.140 ms 0/1813 (0%) when behind R1 testing at 15Mbps UDP, there is UDP packet loss: @home:~$ iperf3 -c ping.online.net -u -b 15000000 -p 5202 Connecting to host ping.online.net, port 5202 [ 4] local 192.168.118.200 port 59820 connected to 62.210.18.40 port 5202 [ ID] Interval Transfer Bandwidth Total Datagrams ... ... - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-10.00 sec 17.7 MBytes 14.9 Mbits/sec 1.092 ms 185/2265 (8.2%) [ 4] Sent 2265 datagrams when behind ERX directly and even at 30Mbps UDP, there is NO UDP packet loss: iperf3 -c ping.online.net -u -b 30000000 -p 5202 Connecting to host ping.online.net, port 5202 [ 6] local 192.168.1.101 port 56094 connected to 62.210.18.40 port 5202 [ ID] Interval Transfer Bandwidth Total Datagrams [ 6] 0.00-1.01 sec 3.23 MBytes 27.0 Mbits/sec 414 [ 6] 1.01-2.01 sec 3.58 MBytes 30.0 Mbits/sec 458 [ 6] 2.01-3.01 sec 3.59 MBytes 30.1 Mbits/sec 459 [ 6] 3.01-4.01 sec 3.57 MBytes 30.0 Mbits/sec 457 [ 6] 4.01-5.00 sec 3.59 MBytes 30.2 Mbits/sec 459 [ 6] 5.00-6.00 sec 3.57 MBytes 29.9 Mbits/sec 457 [ 6] 6.00-7.00 sec 3.59 MBytes 30.1 Mbits/sec 459 [ 6] 7.00-8.01 sec 3.57 MBytes 29.8 Mbits/sec 457 [ 6] 8.01-9.00 sec 3.59 MBytes 30.1 Mbits/sec 459 [ 6] 9.00-10.01 sec 3.57 MBytes 29.9 Mbits/sec 457 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 6] 0.00-10.01 sec 35.4 MBytes 29.7 Mbits/sec 0.758 ms 0/4535 (0%) UDP is very important for gaming traffic and if there is a 13/14mbps on UDP limitation on R1 then it can explain some weird issues.. So question : can people download iperf3 : https://iperf.fr/iperf-download.php and run this test : - deactivate any Congestion Control and enable turbo and superturbo mode . 10Mbps test : iperf3 -c ping.online.net -u -b 10000000 -p 5202 20Mbps test : iperf3 -c ping.online.net -u -b 20000000 -p 5202 and then do the same directly behind their ISP router. this would confirm/infirm that there is something with R1 regarding UDP.

this starts to look more and more like a scam.. (and yeah before the white knight speak we paid for the product..) i would be pissed at Apple if they left the same iPhone software since i bought it. and the white knight bot answers : Apple have 50000 dev , duma just one.. these threads are useless because people here are either brainwashed, have no clue or don't care.. Netduma as a company is one of my biggest disappointment.

I think game with a good net code doesn't need an anti-jitter mechanism because this is implemented in the game server and client: when a packet with a message "at tick X, my game state/ commands are Y," the server should put that message in some internal input queue for tick X, and when the simulation gets to tick X for everyone, it will execute it in time. so implementing a router level anti-jitter may break what the game anti-jitter is already trying to do.

i was indeed replying to someone about dumaOS anti jitter and telling him that if any it will be local jitter control , not remote one.

you always have an upstream (WAN) and a downstream (LAN) interface on a router.. you can apply fq_codel , qdisc on both so you affect all direction. you can even use a netem delay to add artificial latency and control jitter. i doubt that any router will implement an effective remote anti jitter because you can't control the remote side of thing.. (servers, other consoles..) you can only affect your own network and your upstream link saturation. someone could implement some adaptive artificial netem like delay but if someone you are playing with has a 20ms jitter you can't do anything about it unless you add latency to their connection to their worst case (+20ms) which in turn will make your latency looks bad to other players.. it is easy to have no jitter in a local controlled environment.. but that's not what internet is nor what a gaming router is aiming for. what a gaming router is aiming at is to make your connection appear to be a high quality connection so your game matchmaking "internal scoring" match you with similar good connection players (beside geofilter). but what happen in reality is if your connection is too good (superb latency, nat type 1 ) then you are matched with those nat type 3 because they can only connect to a nat type 1 player.... because : - Strict NAT (3) can only match to open NAT (1) people. - Moderate NAT (2) can only match to moderate and open - Open NAT (1) can match to everyone so sometime too good is worst .. networking isn't an easy beast.

fq_codel, codel are exactly dealing with bufferbloat and jitter issue. this is integrated in linux kernel and even some line rate (multiple Gbps) support in NIC with BQL ..we are in 2017.. https://indico.uknof.org.uk/event/27/contribution/3/material/slides/0.pdf

and you are exactly why i think this company is unprofessional.. because it let people like you think a commercial product support forum allows you to have this kind of answer to a PAYING CUSTOMER. this is unseen anywhere else.

seriously don't bother.. i personally gave up.. you have 3 kind of people here : - those waiting for improvement , QoL feature as you can expect from any commercial product - those who are perfectly happy with what they have or are too much in fandom to express any form of constructive criticism netduma related - those who don't care.. the later two are what netduma as a company seems to prefer.. so far they are fed with a bootstrap UI image once every 6 months and are happy with it.. (example:demo) having just a single dev in house is no excuse for what we are seeing from netduma , look at company like console tuner (titan one and two) the dev is alone but there is basically one update every week for new features, minor bug fixes and everything, UI etc.. Netduma is a "commercial" company but i highly doubt that it is the main activity (and priority) of the people involved it (it should for a 180$ commercial product) from here it looks like a hobbyist company. here is what i did : - got a fitPC4 pro (http://www.fit-pc.com/web/products/specifications/fit-pc4-models-specifications/?model%5B%5D=fit-PC4-CG420-WACB-FM4U) - install ubuntu on it - enabled fq_codel as default queuing (sysctl -w net.core.default_qdisc=fq_codel) - use a TC QDISC script for bandwidth reservation/allocation etc.. - installed xtables and geoip iptables modules which allow me to get rule like : -A FORWARD -p udp -m set --match-set WhiteList src -j ACCEPT -A FORWARD -p udp -m set --match-set WhiteList dst -j ACCEPT -A FORWARD -p udp -m set --match-set GeoFiltered dst -m multiport --ports 3074:3080 -m geoip --source-country AP,AF,EG,IR,TR,IQ,SA,YE,SY,AE,TZ,IL,JO,LB -j LOG_DROP - WhiteList is an basic ipset of PSN/AMAZON etc.. or basically what netduma call Cloud partial exemple: root@redir1:# ipset -L WhiteList Name: WhiteList Type: hash:net Revision: 6 Header: family inet hashsize 1024 maxelem 65536 Size in memory: 14456 References: 2 Members: 54.182.164.0/22 199.74.210.0/24 206.138.168.0/21 13.64.0.0/11 131.253.22.0/23 209.201.96.0/22 ... you can even automate the whitelist for Amazon by grabbing this URL : https://ip-ranges.amazonaws.com/ip-ranges.json as amazon is used for a lot of PSN or dedicated servers etc.. - Geofiltered is an ipset containing my PS4 lan IP or not.. to activate geofiltering.. this get me basically 100% of what the net duma is doing right now. yes i don't have a nice UI and all the bells&whistles knobs and that's why i was interested in the netduma. but now at least i'm not waiting 18 months between software updates.

and since you are so inclined to think we are all stupid customers : here is me on linkedin.. read my resume before assuming anything about me. link removed by moderator now show me your beside being a dumb fan boy ? adel

can you build a car from the ground up by yourself ? yes or no ? is you car functional ? does you car manufacturers do 0 update to you In car Entertainment software in 14 months? you can replace car with 'iPhone', 'PS4','xbox', 'netflix' whatever.. once again i doubt you get my point. i'm not on some community based software forum. i'm on a commercial company support forum asking for more detail about firmware update to something i paid for. ps: and oh... yes i can certainly build a router from ground up myself using some linux as a based as i did already. Netduma used openwrt as a base too. now do i need to prove this to you ? no..

you don't understand, you are definitely not worth any time.. get back to your copy paste posts..and oh don't forget to erase your sources as always..

I already did and i am perfectly satisfied with my solution.. it is based on a fitpc4 running ubuntu and all what i listed previously. I just check regularly if my investment get any update, you should be glad i didn't gave up on it or that would be bad because i think i'm exactly market target for stuff like this. Netduma being 1 or 100 employees doesn't change the fact that we pay a premium price (200€) to get a router with game oriented features and those are stall since january 2016. There is other 1 person company like the people at consoletuner.com for the titan one and two stuff, yet they make firmware update almost weekly for both small bug fixes and feature requests.