@someusername said in Aliases and limiters:

Should I enable the rules and kill the states of the IPs affected?

The existing state is going to take precedence over the new rule so yes, kill the state and/or end the transfer when testing changes or any firewall rule.

@daddygo Thanks, I appreciate it.

@steveits said in How does borrowing work in CBQ? Or, does it?:

I found that the Comcast/Xfinity speed test site is testing about 40 Mbps downloading to our office

Finally tracked this part down, and kinda feel dumb, but speedtest.xfinity.com has a gear in the upper right to change protocols. Testing over IPv6 tunneled through Hurricane Electric is throttled to around 40. Testing over IPv4 is the expected speed.

@pzanga

My provider used to source RTP directly from the carrier servers (not their own) but always had their own SIP.. (has since changed)

Depending on what you have on your end.. Server or Clients.. Look to see what your clients are connecting to. If you have a local on site SIP server it will still act as a client to go out to the providers server generally.

Look at connection states to see what things are trying to connect to. Do you have DNS of their stuff? sip.frontier.com?? ect..??

Outbound everything is allowed by default. In some cases the provider does want inbound NAT (I don't usually agree with) and in some cases you will only need firewall rules to allow the traffic to the client.

Maybe the Siproxd package is a good fit for you?

@andyrh

I fixed it!

https://www.youtube.com/watch?v=pk7hONu0b1c

This video explained it all. The other documentation was either unclear or the process was not intuitive.

For example I needed to make the firewall rule on the LAN and use the source IP. I assumed the WAN is needed to be limited to a destination address - and that didn't work. I also needed traffic limiter entries for In and Out.

It worked for the videos. 10Mbps still invoked HDR for Amazon but 6Mbps brightened the picture considerably. I will experiment with other speeds a bit later.

broken again in 2.5.2 release

how do I mark the ticket as closed, I created it and fixed it.

@steveits more or less same result (right side iftop)
fc5f1dae-58d2-464c-aa7b-740262fa9187-image.png

@magikmark that did it! now seems to be working as expected! Thanks! It seems like something was stuck or corrupt which may have caused that issue.