16 Replies
      Latest reply: Jan 12, 2017 2:35 AM by eskimo RSS
      jarheadii Level 1 Level 1 (0 points)

        I just upgraded to macOS Sierra last week and realized that Network Link Conditioner doesn't work anymore.

        Any solutions for fix it? Or if someone know a similar network traffic limiter app.

         

        Thanks in advance.

        • Re: Network Link conditioner doesn't work on macOS Sierra
          eskimo Apple Staff Apple Staff (6,310 points)

          Network Link Conditioner is quite tightly bound to the kernel architecture and, as such, has to be updated with each major OS release.  Did you install the Xcode 8 version?  If not, you should.

          You can find this by:

          1. launching Xcode 8

          2. choosing Xcode > Open Developer Tool > More Developer Tools

          3. finding, downloading and installing Additional Tools for Xcode 8

          Share and Enjoy

          Quinn “The Eskimo!”
          Apple Developer Relations, Developer Technical Support, Core OS/Hardware
          let myEmail = "eskimo" + "1" + "@apple.com"

            • Re: Network Link conditioner doesn't work on macOS Sierra
              jarheadii Level 1 Level 1 (0 points)

              yes Xcode 8 it's already on my computer, but when I launch Network link conditioner, I switch on but it has no effect on my network connectivity, even when set to 100% loss.

                • Re: Network Link conditioner doesn't work on macOS Sierra
                  eskimo Apple Staff Apple Staff (6,310 points)

                  It’s working for me.  Here’s what I did:

                  1. On 10.12, I downloaded the Additional Tools for Xcode 8 disk image.

                  2. I mounted it and double clicked Network Link Conditioner.prefPane.

                  3. That brought me to System Preferences, where I clicked Install to install preferences pane.

                  4. In the preferences pane, I created a new profile called latency, where each of the Delay fields is see to 300 milliseconds.

                  5. In Terminal, I started pinging a local device; the ping time was a few milliseconds.

                  6. Back in the preferences pane, I activated my profile; looking at Terminal, I saw the ping time jump to over 300 milliseconds.

                  &. I then deactivate my profile; the ping time returned to normal.

                  Here’s a transcript of what I saw in Terminal:

                  $ ping fluffy.local.
                  PING fluffy.local (192.168.1.39): 56 data bytes
                  64 bytes from 192.168.1.39: icmp_seq=0 ttl=64 time=2.722 ms
                  64 bytes from 192.168.1.39: icmp_seq=1 ttl=64 time=2.187 ms
                  64 bytes from 192.168.1.39: icmp_seq=2 ttl=64 time=2.092 ms
                  64 bytes from 192.168.1.39: icmp_seq=3 ttl=64 time=2.408 ms
                  64 bytes from 192.168.1.39: icmp_seq=4 ttl=64 time=2.536 ms
                  64 bytes from 192.168.1.39: icmp_seq=5 ttl=64 time=303.466 ms
                  64 bytes from 192.168.1.39: icmp_seq=6 ttl=64 time=302.965 ms
                  64 bytes from 192.168.1.39: icmp_seq=7 ttl=64 time=302.052 ms
                  64 bytes from 192.168.1.39: icmp_seq=8 ttl=64 time=302.970 ms
                  64 bytes from 192.168.1.39: icmp_seq=9 ttl=64 time=302.708 ms
                  …
                  64 bytes from 192.168.1.39: icmp_seq=185 ttl=64 time=302.126 ms
                  64 bytes from 192.168.1.39: icmp_seq=186 ttl=64 time=302.047 ms
                  64 bytes from 192.168.1.39: icmp_seq=187 ttl=64 time=303.105 ms
                  64 bytes from 192.168.1.39: icmp_seq=188 ttl=64 time=302.251 ms
                  64 bytes from 192.168.1.39: icmp_seq=189 ttl=64 time=302.295 ms
                  64 bytes from 192.168.1.39: icmp_seq=190 ttl=64 time=2.401 ms
                  64 bytes from 192.168.1.39: icmp_seq=191 ttl=64 time=2.208 ms
                  64 bytes from 192.168.1.39: icmp_seq=192 ttl=64 time=2.412 ms
                  64 bytes from 192.168.1.39: icmp_seq=193 ttl=64 time=2.422 ms
                  64 bytes from 192.168.1.39: icmp_seq=194 ttl=64 time=2.495 ms
                  …
                  

                  Please try this out and let me know what you see.

                  Share and Enjoy

                  Quinn “The Eskimo!”
                  Apple Developer Relations, Developer Technical Support, Core OS/Hardware
                  let myEmail = "eskimo" + "1" + "@apple.com"

              • Re: Network Link conditioner doesn't work on macOS Sierra
                jlstmac Level 1 Level 1 (0 points)

                Mac OS 10.12 + Xcode8 + Additional tools for Xcode8。Only "High Latency DNS" works for me!

                • Re: Network Link conditioner doesn't work on macOS Sierra
                  eskimo Apple Staff Apple Staff (6,310 points)

                  Folks, it would help if you were more precise about what you tried, what worked, and what didn’t.  I was hoping for something along the lines of I repeated the steps from your Oct 24 post and it worked as you described, but if I change step A to do X and change step B to Y then I see symptoms Z.

                  Share and Enjoy

                  Quinn “The Eskimo!”
                  Apple Developer Relations, Developer Technical Support, Core OS/Hardware
                  let myEmail = "eskimo" + "1" + "@apple.com"

                  • Re: Network Link conditioner doesn't work on macOS Sierra
                    jlstmac Level 1 Level 1 (0 points)

                    Only “DNS Delay” working.