soccerjean17 Posted July 23, 2018 Posted July 23, 2018 I'm having some issues with Traffic Prioritization specially on port 80. It causes my upload buffer bloat to go extremely high. any suggestions?
Administrators Netduma Fraser Posted July 23, 2018 Administrators Posted July 23, 2018 You shouldn't prioritize that port as downloads will use that port. Traffic Prioritization is only meant for low latency/bandwidth applications such as games otherwise it can cause it to become unstable.
soccerjean17 Posted July 23, 2018 Author Posted July 23, 2018 You shouldn't prioritize that port as downloads will use that port. Traffic Prioritization is only meant for low latency/bandwidth applications such as games otherwise it can cause it to become unstable. I thought maybe if I prioritize these ports on the ps4 it would help a little. The link is down below. https://portforward.com/networking/static-ip-ps4/
Administrators Netduma Fraser Posted July 23, 2018 Administrators Posted July 23, 2018 Leave DumaOS Classified Games enabled and that will prioritize the ports necessary for your games/console
soccerjean17 Posted July 23, 2018 Author Posted July 23, 2018 Leave DumaOS Classified Games enabled and that will prioritize the ports necessary for your games/console alright I'll try that thanks a lot for your help.
DFAN Posted September 22, 2018 Posted September 22, 2018 i cannot get the advanced qos port entry system to work? i just get this large error RPC error 'ERROR_UNKNOWN': bad argument #1 to 'len' (string expected, got nil) -> stack traceback: ?: in function <?:73> [C]: in function 'len' ?: in function '?' ?: in function 'decode' ?: in function <?:50> (tail call): ? ?: in function <?:324> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:290> [C]: in function 'run' ?: in function <?:345> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:261> (tail call): ? /dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> [C]: in function 'xpcall' /dumaos/api/cli.lua:59: in main chunk [C]: ?
Administrators Netduma Fraser Posted September 23, 2018 Administrators Posted September 23, 2018 We're aware of that issue and is fixed in the next firmware. Not sure how this error slipped through.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.