Monday, July 23, 2012

Re: [Discuss-gnuradio] MTU Size

On 07/23/2012 09:40 AM, Alexander Olihovik wrote:
> More specifically, I've tried changing the device address with:
> device_addr="addr0=10.1.1.105, recv_frame_size=4096, send_frame_size=4096"
> but when running the program, both the recv_frame_size and send_frame_size
> are still 1472 bytes.
> I've also configured my network to be able to handle frames of size 4096,
> and have had this working with C++ code. However, the Python code doesn't
> work as I would expect. It seems not to make a difference whether I specify
> the frame size or not.
>

Its the same device args, so python/c++ it shouldnt make a difference.

The driver is however testing if it can handle that MTU by sending test
packets. Perhaps its still a network configuration issue?

Also, you should be able to

uhd_usrp_probe --args="addr0=10.1.1.105, recv_frame_size=4096,
send_frame_size=4096"

and still see the same issue.

-josh

> On Mon, Jul 23, 2012 at 11:56 AM, Alexander Olihovik <ano9cn@virginia.edu>wrote:
>
>> Hi all,
>> I'm currently getting overflow errors that I believe could be remedied by
>> increasing the MTU size.
>> Is there a way to change the recv_frame_size and send_frame_size in Python?
>>
>> I've read the Transport Application Notes and some old emails to this
>> list, but I still can't figure out how to pass these parameters to the USRP
>> objects. Any help is greatly appreciated!
>>
>> -Alex
>>
>
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

No comments:

Post a Comment