Hi,
When I use the module, I find a issue.

1. This is (premierwave_en) module status.
>show
Product Information:
Product Type : Lantronix PremierWave EN (premierwave_en)
FW Version / Date : 7.9.0.1R8 / Jan 14 14:45:06 PST 2015
Radio FW Version : 3.2.12.0/1.1.6.71/6.134
Current Date/Time : Thu Jan 1 00:03:24 UTC 1970
Serial Number : 0080A39AA664
Uptime : 0 days 00:03:25
Perm. Config : saved
Region : United States

Alerts:
<None>

Network Status:
Primary DNS : <None>
Secondary DNS : <None>

Interface : eth0 (via br0) [br0]
Link : Auto 10/100 Mbps Auto Half/Full (100 Mbps Full)
MAC Address : 00:80:a3:9a:a6:64
Hostname : <None> [<DHCP>]
Domain : <None> [<DHCP>]
IP Address : 169.254.8.33/16 [<DHCP>]
Network Mask : 255.255.0.0 [<DHCP>]
Default Gateway : <None> [<DHCP>]
MTU : 1500

Interface : wlan0 (via br0) [br0]
Link : ESTABLISHED
MAC Address : 3c:97:0e:07:77:30
Hostname : <None> [<None>]
Domain : <None> [<None>]
IP Address : 169.254.3.149/16 [<AutoIP>]
Network Mask : 255.255.0.0 [<AutoIP>]
Default Gateway : <None> [<None>]
MTU : 1500


VPN Status:
Status : Disabled
IP Address : <None>

2. The module Bridge state is enabled.
(config-bridge:br0)#show
Bridge br0 Configuration:
State : Enabled
Bridging MAC Address:
WARNING: Interface eth0 is enabled but is being overridden by br0.


3. Use PING command to test.(Third time PING command, the module reboot)

C:\Users\wind>ping 172.16.1.207

Ping 172.16.1.207.32 :
172.16.1.207 : =32 =2ms TTL=128
172.16.1.207 : =32 =2ms TTL=128
172.16.1.207 : =32 =3ms TTL=128
172.16.1.207 : =32 =2ms TTL=128

(0% loss)

C:\Users\wind>ping 172.16.1.207 -l 1000

Ping 172.16.1.207 1000 :
172.16.1.207 : =1000 =5ms TTL=128
172.16.1.207 : =1000 =4ms TTL=128
172.16.1.207 : =1000 =6ms TTL=128
172.16.1.207 : =1000 =3ms TTL=128
(0% loss)

C:\Users\wind>ping 172.16.1.207 -l 2000

Ping 172.16.1.207 2000 :

172.16.0.32 :
172.16.0.32 :
172.16.0.32 :
(all loss and module reboot)


4. The test equipment:
1. Two PC (WIN10,MTU is the default value)
2. PremierWave Development Kit and a Module
3. A CISCO AP 2602E


I think that issue is due to improper processing of fragmented packets.
I want to make sure this is a configuration issue or a firmware BUG


Thanks in advance