Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 2957 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SG135W (9.510-5) Radius authentication?

tryf

Hello to all network specialists,

in our subsidiary I got an SG135W Firewall with integrate AP (LocalWifi0) and no separate AP . For the WiFi authentication I have my Radius Server (NAP 2012R2) up and running. But I get no response from Radius Server. Does anybody know, if SG135W (9.510-5) basically supports Radius authentication?

hostapd: wifi0: CTRL-EVENT-EAP-STARTED 10:08:b1:62:1f:01

hostapd: wifi0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1

hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.1X: Sending EAP Packet (identifier 103)
hostapd: wifi0: STA 10:08:b1:62:1f:01 WPA: event 2 notification
hostapd: wifi0: STA 10:08:b1:62:1f:01 WPA: event 2 notification
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.11: disassociated
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.11: disassociated
hostapd: wifi0: STA 10:08:b1:62:1f:01 MLME: MLME-DISASSOCIATE.indication(10:08:b1:62:1f:01, 8)
hostapd: wifi0: STA 10:08:b1:62:1f:01 MLME: MLME-DISASSOCIATE.indication(10:08:b1:62:1f:01, 8)
hostapd: wifi0: STA 10:08:b1:62:1f:01 MLME: MLME-DELETEKEYS.request(10:08:b1:62:1f:01)
hostapd: wifi0: STA 10:08:b1:62:1f:01 MLME: MLME-DELETEKEYS.request(10:08:b1:62:1f:01)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
hostapd: wifi0: STA 10:08:b1:62:1f:01 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

Every help is welcomed.
Best regards.


This thread was automatically locked due to age.
Parents
  • 0

    How does your setup on the SG135W look like? I don't use Radius, but Active Directory. Under Definitions & Users, Authentication Services, Server: I have my Domain Controller setup their as an AD auth server. You can define a Radius server there as well. Did you double check on the ports in use?

    Unfortunately, it is long ago that it was setup, so not sure on what exactly is needed. I think in our setup, the SG pulls the users from a specific AD group. And than there is Client-Authentication, which allows the group "internal wifi users" to use the internal wifi network (to connect to AD?). Gosh, this was long ago.

    Hopefully there is a few pointers for you to look into.

Reply
  • 0

    How does your setup on the SG135W look like? I don't use Radius, but Active Directory. Under Definitions & Users, Authentication Services, Server: I have my Domain Controller setup their as an AD auth server. You can define a Radius server there as well. Did you double check on the ports in use?

    Unfortunately, it is long ago that it was setup, so not sure on what exactly is needed. I think in our setup, the SG pulls the users from a specific AD group. And than there is Client-Authentication, which allows the group "internal wifi users" to use the internal wifi network (to connect to AD?). Gosh, this was long ago.

    Hopefully there is a few pointers for you to look into.

Children
No Data
Unfiltered HTML