Inside and Outside interfaces cannot be the same.



  • I wanted to test the QoS setup over the lan to make sure it is working properly. Sure, I could run tests on the wan using sites like speedtest.net but I wanted to accurately run some ack tests. Not only that but this is what my ping looks like from comp 1 to comp 2 on the lan when comp 3 is maxing out the wifi:
    64 bytes from 192.168.1.3: icmp_seq=529 ttl=64 time=265.828 ms
    64 bytes from 192.168.1.3: icmp_seq=530 ttl=64 time=20.954 ms
    64 bytes from 192.168.1.3: icmp_seq=531 ttl=64 time=243.703 ms
    64 bytes from 192.168.1.3: icmp_seq=532 ttl=64 time=228.313 ms
    64 bytes from 192.168.1.3: icmp_seq=533 ttl=64 time=233.493 ms
    64 bytes from 192.168.1.3: icmp_seq=534 ttl=64 time=235.306 ms
    64 bytes from 192.168.1.3: icmp_seq=535 ttl=64 time=102.201 ms
    64 bytes from 192.168.1.3: icmp_seq=536 ttl=64 time=104.237 ms
    64 bytes from 192.168.1.3: icmp_seq=537 ttl=64 time=195.841 ms
    64 bytes from 192.168.1.3: icmp_seq=538 ttl=64 time=234.064 ms
    It would be nice to be able to setup QoS so the ping doesn't spike up on an FPS when time machine starts running. I believe setting up aprox 30% ack on the lan end would be appropriate in a worse case senario. On the wan end it varies a bit more…freaking bit torrent.

    Is there an easy way to QoS the same subnet? Is this option aval in 2.0?



  • I'm confused.  If the two computers are on the same subnet, the pfsense should not even be involved.  Can you describe your network topology more clearly?


Log in to reply