Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-27 Thread Marcus D Leech via USRP-users
Try adjusting the MTU as well to 1500 Sent from my iPhone > On Jul 26, 2019, at 9:36 PM, 汤 飞 wrote: > > FYI > > ifconfig > enp2s0: flags=4163 mtu 8000 > inet 192.168.10.1 netmask 255.255.255.0 broadcast 192.168.10.255 > inet6 fe80::96c6:91ff:febd:e8bb prefixlen 64 scopeid

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-26 Thread 汤 飞 via USRP-users
FYI ifconfig enp2s0: flags=4163 mtu 8000 inet 192.168.10.1 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::96c6:91ff:febd:e8bb prefixlen 64 scopeid 0x20 ether 94:c6:91:bd:e8:bb txqueuelen 1000 (Ethernet) RX packets 3352 bytes 2274650 (2.2 MB)

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-26 Thread Sam Reiter via USRP-users
Can you post the output of *ifconfig* on your system? Sam Reiter SDR Support Engineer Ettus Research On Thu, Jul 25, 2019 at 7:40 PM 汤 飞 wrote: > Thanks! > > I am learning to use RFNOC to integrate a baseband. So I used PyBOMBS to > create the environment. The automatically installed UHD vers

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-25 Thread 汤 飞 via USRP-users
Thanks! I am learning to use RFNOC to integrate a baseband. So I used PyBOMBS to create the environment. The automatically installed UHD version is as follows uhd_find_devices [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_3.15.0.git-19-g7e1b567d -

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-25 Thread Sam Reiter via USRP-users
Found the offending commit and reported the issue. It also looks like adding *recv_frame_size=1476* explicitly to the device arguments cleared things up on my N310 running 3.14.1.0. Let me know if this does / doesn't work for anyone. Sam Reiter SDR Support Engineer Ettus Research On Thu, Jul 25,

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-25 Thread Marcus D. Leech via USRP-users
On 07/25/2019 03:56 PM, Sam Reiter wrote: Follow up on this thread. I ran my N310 with a 1GbE link and was able to reproduce the "Bad CHDR or packet fragment issue". It seems specific to N3xx RX over a 1GbE link on 3.14.1.0. I didn't spend a ton of time trying to find a workaround on 3.14.1.0,

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-25 Thread Sam Reiter via USRP-users
Follow up on this thread. I ran my N310 with a 1GbE link and was able to reproduce the "Bad CHDR or packet fragment issue". It seems specific to N3xx RX over a 1GbE link on 3.14.1.0. I didn't spend a ton of time trying to find a workaround on 3.14.1.0, but rolling back to 3.14.0.0 cleared the issue

Re: [USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-23 Thread Marcus D Leech via USRP-users
Normally Intel controllers have better performance but even a RealTek chip should have no problem at those data rates. Sent from my iPhone > On Jul 23, 2019, at 10:01 PM, 汤 飞 wrote: > > Actually my pc’s Ethernet card chip is from Realtek. > I’ve tried all possible MTU sizes of auto, 1000, 1

[USRP-users] 答复: 答复: N310 "Bad CHDR or packet fragment" Problem

2019-07-23 Thread 汤 飞 via USRP-users
Actually my pc’s Ethernet card chip is from Realtek. I’ve tried all possible MTU sizes of auto, 1000, 1500, 2000, and up to 9000. Always the same errors. Is it the inherent problem with the Realtek chip? If that, is there any workaround? eg. Changing the default Linux driver, or the last solution,