WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2018-Mar-08 07:06:52

gmkim
Member
Registered: 2016-Jul-19
Posts: 27

.

.

Last edited by gmkim (2020-Aug-17 20:03:33)

Offline

 

#2 2018-Mar-08 09:46:28

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: .

The WARPLab ref design uses broadcast packets to send triggers to the WARP nodes. The WL code creates an IP/UDP packet with destination address of 10.0.0.255 (assuming the default 10.0.0.x subnet). Your PC maps this to the broadcast MAC address and sends it to the switch. The switch then forwards this packet to all connected ports. Is your new switch configured to block broadcast packets?

Offline

 

#3 2018-Mar-19 00:27:26

gmkim
Member
Registered: 2016-Jul-19
Posts: 27

Re: .

.

Last edited by gmkim (2020-Aug-17 20:03:45)

Offline

 

#4 2018-Mar-19 09:06:29

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: .

These errors can all be explained by your Ethernet switch dropping packets. Something is causing unreliable communication between the PC and WARP nodes, most likely a fault or configuration error in your new switch. You need to isolate the source of this unreliability before WARPLab will work normally.

Offline

 

Board footer