@Leon71,

first, an EAP115 has only a Fast Ethernet (100 Mbps) interface, so max. throughput can't raise over 100 Mbps full-duplex .

Secondly, the 300 Mbps is the maximum WiFi rate of an EAP115 over a shared, half-duplex medium. It's neither the actual wireless throughput a certain client can achieve nor is it the Ethernet full-duplex goodput on the EAP's Fast Ethernet interface.

For example, under ideal conditions the max. WiFi goodput for 300 Mbps WiFi rate in 802.11n mode is 70% of the WiFi throughput, this yields 300 Mbps - 30% = 210 Mbps half duplex.

210 Mbps wireless goodput is enough to support an Ethernet throughput of 100 Mbps full-duplex (which is 100 Mbps in each direction simultaneously, thus corresponding to 200 Mbps half-duplex).

Remember, this is under ideal conditions (no interferences, no other APs/clients around, 40 MHz channel width, 802.11n-only mode, low distance and free line of sight between the client and the EAP).

But real-world wireless throughput depends on many more influences beside WiFi mode, channel width and the WiFi rate negotiated between client and EAP, such as the client's WiFi card, interferences, signal reflections, available AirTime, number of nearby APs and even other non-WLAN RF devices operating in the same band (DECT, Bluetooth, Zigbee, video/audio transmitters, remote controls, baby phones, microwave ovens) etc. etc.

Thus, in my opinion 80 Mbps is a pretty good Ethernet goodput for a 2.4 GHz N300 device. The more you can ensure ideal conditions as lised above, the better is the change to increase this goodput up to 98 Mbps, which is pretty much the maximum goodput over Fast Ethernet.