ndt-users list created

[Jakub Sławiński <>]

Hi,

can you try using the '-i' option on the server side?


Regards,
  Jakub.

On 12/10/2013 12:38 PM, Prabu Gj wrote:
> Hi,
> 
>         If my answer is wrong then, i am testing in same network which is (
> client and server connected to same switch and its connected to firewall
> for routing to external).
> 
> Regards
> Prabu
> 
> 
> 
> 
> On Tue, Dec 10, 2013 at 3:34 PM, Prabu Gj 
> <>
>  wrote:
> 
>> HI,
>>
>>           I have bonding br0 with eth0 port and other then loopback.
>>
>> br0       Link encap:Ethernet  HWaddr E0:69:95:73:1C:D3
>>           inet addr:192.168.5.209  Bcast:192.168.5.255  Mask:255.255.255.0
>>           inet6 addr: fe80::e269:95ff:fe73:1cd3/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:7628959 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:836082 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:5109976379 (4.7 GiB)  TX bytes:321323316 (306.4 MiB)
>>
>> eth0      Link encap:Ethernet  HWaddr E0:69:95:73:1C:D3
>>           inet6 addr: fe80::e269:95ff:fe73:1cd3/64 Scope:Link
>>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>>           RX packets:19821791 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1419032 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:11836874717 (11.0 GiB)  TX bytes:530072300 (505.5 MiB)
>>           Memory:fe400000-fe420000
>>
>> lo        Link encap:Local Loopback
>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>           inet6 addr: ::1/128 Scope:Host
>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>           RX packets:4 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:1872 (1.8 KiB)  TX bytes:1872 (1.8 KiB)
>>
>> Regards
>> Prabu
>>
>>
>> On Tue, Dec 10, 2013 at 3:26 PM, Jakub Sławiński 
>> <
>>> wrote:
>>
>>>
>>> Hi,
>>>
>>> how many network devices do you have on your ndt server? Which one would
>>> you expect to be used during the test?
>>>
>>>
>>> Regards,
>>>   Jakub.
>>>
>>> On 12/10/2013 10:41 AM, Prabu Gj wrote:
>>>> Hi,
>>>>
>>>>     After increasing debug level out put is below.
>>>>
>>>> # web100clt -ll -ddd -n 192.168.5.209
>>>> Testing network path for configuration and performance problems  --
>>>  Using
>>>> IPv4 address
>>>> * New Client, implements queuing feedback
>>>> Requesting test suite:
>>>>  > Middlebox test
>>>>  > Simple firewall test
>>>>  > C2S throughput test
>>>>  > S2C throughput test
>>>>  > META test
>>>>  <-- Middlebox test -->
>>>>   -- port: 3003
>>>> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
>>>>  <-------------------->
>>>>  <-- Simple firewall test -->
>>>> checking for firewalls . . . . . . . . . . . . . . . . . . .
>>>>   -- port: 32773
>>>>   -- time: 1
>>>>   -- oport: 48942
>>>> Done
>>>>  <-------------------------->
>>>>  <-- C2S throughput test -->
>>>>   -- port: 3002
>>>> running 10s outbound test (client to server) . . . . . Protocol error -
>>>> missed text message!
>>>> C2S throughput test FAILED!
>>>>  <-- S2C throughput test -->
>>>> Protocol error - missed prepare message!
>>>> S2C throughput test FAILED!
>>>>  <-- META test -->
>>>> Protocol error - missed prepare message!
>>>> META test FAILED!
>>>> Protocol error - expected results!  got '', msgtype=2
>>>>
>>>> Regards
>>>> Prabu
>>>>
>>>>
>>>> On Tue, Dec 10, 2013 at 2:23 PM, Jakub Sławiński
>>>> <>wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> can you increase the debug level in your client?
>>>>>
>>>>>
>>>>> Regards,
>>>>>   Jakub.
>>>>>
>>>>> On 12/10/2013 09:47 AM, Prabu Gj wrote:
>>>>>> Hi,
>>>>>>
>>>>>>    Thanks for your reply, I am facing the problem in command line
>>> also.
>>>>>>
>>>>>> # web100clt -ll -n 192.168.5.209
>>>>>> Testing network path for configuration and performance problems  --
>>>>>  Using
>>>>>> IPv4 address
>>>>>> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
>>>>>> checking for firewalls . . . . . . . . . . . . . . . . . . .  Done
>>>>>> running 10s outbound test (client to server) . . . . .
>>>>>> Protocol error - missed text message!
>>>>>> C2S throughput test FAILED!
>>>>>> Protocol error - missed prepare message!
>>>>>> S2C throughput test FAILED!
>>>>>> Protocol error - missed prepare message!
>>>>>> META test FAILED!
>>>>>> Protocol error - expected results!  got '', msgtype=2
>>>>>>
>>>>>> Regards
>>>>>> Prabu
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Dec 10, 2013 at 1:28 PM, Jakub Sławiński
>>>>>> <>wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> are you able to perform tests successfully with the command line
>>> client?
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>   Jakub.
>>>>>>>
>>>>>>> On 12/10/2013 08:46 AM, prabu.gj wrote:
>>>>>>>> Hi Team,
>>>>>>>>
>>>>>>>>        Anybody help me on this issue please.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Prabu
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>