Thanks. TCP/IP and UDP has been directed to the hardware processor as well? The easiest way to test TCP/IP and UDP would be to have a server connected to the same CMTS, configured for the correct responses. With that type of test configuration, any latency would be due to the modems at the test client and test server end plus a minimal amount due to the CMTS. If you can configure the CMTS to respond to TCP/IP and UDP pings, and just use the CMTS for a test target for all protocols, all the better.