Thank you Dave. Yes with regular port I can see radius packets at the the radius sever and between the client and hostapd I see EAPOL packets. Can you suggest what value needs to write in the fwd_mask for this to work for bridge interface ? Regards Simon On Tuesday, April 22, 2025, Dave Funk <dbfunk@engineering.uiowa.edu> wrote:
On Mon, 21 Apr 2025, SIMON BABY wrote:
Hello Team,
Do we have to enable anything in the bridge interface in Linux for processing EAPOL packets ? Currently the bridge in my setup cannot detect EAPOL packets. However the DSA lan ports are able to detect. The bridge interface contains the lan ports.
Regards Simon
Technically you should not see any EAPOL packets at your radius server.
You should see the rad-request/rad-account UDP 1812 & 1813 (and possibly tcp 1812 & 1813) packets at your radius server so you will need to be sure those packets make it in thru what ever network config is implemented on the system hosting your radius server.
EAPOL is the network protocol that your WPA supplicants (wireless devices & laptops) use to communicate to your wireless access-points and they use UDP 1812/1813 to send the request to your radius server.
-- Dave Funk University of Iowa <dbfunk (at) engineering.uiowa.edu> College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center, 10 <https://www.google.com/maps/search/amans+Center,+10?entry=gmail&source=g>3 S Capitol St. Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include <std_disclaimer.h> Better is not better, 'standard' is better. B{ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list /users.html