Smoothwall + Ruckus

[TechMonkey]

Ok, I'm feeling particularly stupid at the moment.

I have Smoothwall all setup so I can use the new simple BYOD features. I have followed the new documentation and as far as I can see it is fill in the details for both Smoothwall and Ruckus. But when I go to test from Ruckus I always get failed. In Smoothwall I get:

 

09:21:01 Authentication service RADIUS authentication failed; username: TechMonkey, access point: 192.168.151.239

 

Smoothwall is using AD Auth for users, everything else is working.

Any tips? There must be something I am missing as all the details are very straightforward and the new Smoothwall BYOD system doesn't have all the requirements it had before, so it looks like it should just work!

 

ARGGGHHH.

[TechMonkey]

Anyone?

[truebluesteve]

Ok, I'm feeling particularly stupid at the moment.

I have Smoothwall all setup so I can use the new simple BYOD features. I have followed the new documentation and as far as I can see it is fill in the details for both Smoothwall and Ruckus. But when I go to test from Ruckus I always get failed. In Smoothwall I get:

 

09:21:01 Authentication service RADIUS authentication failed; username: TechMonkey, access point: 192.168.151.239

 

Smoothwall is using AD Auth for users, everything else is working.

Any tips? There must be something I am missing as all the details are very straightforward and the new Smoothwall BYOD system doesn't have all the requirements it had before, so it looks like it should just work!

 

ARGGGHHH.

 

Are these the new features in the latest updates for Smoothwall (haven't got round to doing mine yet - might be a job for today!)?

 

I have got the same setup - albeit via VLANs and it all works fine so I'm a bit puzzled. I guess because you are getting entries in the Smoothwall logs, then the password between the Smoothwall and Ruckus is OK. Have you tried another user - a test account for example?

[AliG]

I think I read there is a bug that support can apply a temp workaround for until it's fixed in the next update I keep meaning to call them myself.

[FN-GM]

I think I read there is a bug that support can apply a temp workaround for until it's fixed in the next update I keep meaning to call them myself.

 

I got update 83 a few days ago. These are the fixes

 

•Ref 8218. Security updates to NTP services

•Ref 8201. Resolves an issue in which Access Points reporting the same connection in different cases are now handled as the same AP

•Ref 8143. Improved TLS negotiation for sites that do not support TLS 1.2

•Ref 8097. Removed support for legacy adapter causing Hyper-V connectivity issues

[TechMonkey]

Thanks, I gave them a call on Friday and funnily enough all L2 staff were unavailable as they were in training.... On the new BYOD section The L1 guy was as bemused as me though, so I felt better that I wasn't missing something obvious.

Should be phoning me back today.

 

I tried different users, with domain, without domain, using either slash.

 

I'll report back if I get it solved.

[rob_coles]

Hello,

 

I have my ruckus working with Smoothwall. The test username/password feature doesn't work. Never has, However ruckus does pass the logon to smoothwall which does work.

 

try connecting from a client device.

[rob_coles]

Only other problem we had was making sure the shared secret between sw & ruckus doesn't have any special characters in

[TechMonkey]

Thanks Rob, Shared secret couldn't really be any simpler, with no special anything in it. Fails with the same error in the logs from a device, so completely baffled.

[TechMonkey]

Well had an L2 tech remote in and says the settings are right but I have to turn on Frame IP Address enabled on our DHCP server. The only place I can find any mention of this is either in RADIUS server documentation or in documentation for NPS server role for 2008/2012.

 

Any one shed any light on this attribute and where I can find it on a DHCP server?

[Nick_Parker]

Hey @TechMonkey, did you ever resolve this issue? Our Ruckus equipment arrived today and I'm having the same issue as you

[ass17]

Ever thought of dropping the radius server? We don't use one and our AD - SW - Ruckus works just fine. We use the accounting server option in ruckus to auth all users devices. Staff pass through smoothwall and pupils are forced to login to apply specific web filter policies.

[TechMonkey]

Hey @TechMonkey, did you ever resolve this issue? Our Ruckus equipment arrived today and I'm having the same issue as you

 

I did for about a week and then it stopped working. Smoothwall said that there end was all working and our Ruckus reseller couldn't find anything wrong. I abandoned all hope in the end as we are doing lots of work currently for a network refresh over the summer so I will look again after then.

 

So yes it worked and was brilliant. Then it didn't and was daft.

[Nick_Parker]

I did for about a week and then it stopped working. Smoothwall said that there end was all working and our Ruckus reseller couldn't find anything wrong. I abandoned all hope in the end as we are doing lots of work currently for a network refresh over the summer so I will look again after then.

 

So yes it worked and was brilliant. Then it didn't and was daft.

 

@TechMonkey, Well that sucks...

Do you know what you changed to get it working for that week?

[howartp]

Neither myself or @timbo have got this working either despite several attempts including Smoothwall and Ruckus.

[TechMonkey]

@TechMonkey, Well that sucks...

Do you know what you changed to get it working for that week?

 

I'm afraid not. Smoothwall were working on it and then it started working. A teacher randomly commented how great it was then the wireless worked but its a shame it doesn't any more, so I don't even have an exact date for when it broke.

 

After the summer (or during if I'm sitting twiddling my thumbs HA HA HA HA HA HA!!) I'm going to start again. Remove all Smoothwall BYOD settings, all Ruckus BYOD settings and methodically go through it documenting everything. Hopefully I will either have an idea what is broken or know exactly what made it work.

[AndyB4rks]

Did anyone get to the bottom of this, were having this exact same fault