The line was missing to begin with. Here is what it looked like before: [10.*.*.*] AccessListMap=N description=WLC #1 gamingVlan=612 registrationVlan=613 guestVlan=612 deauthMethod=RADIUS type=Cisco::WLC_5500 UMHBVlan=611 ForeignVlan=612 isolationVlan=617
and here it is with the radius secret added: [10.*.*.*] radiusSecret=SUPER DUPER SECRET AccessListMap=N description=WLC #1 gamingVlan=612 registrationVlan=613 guestVlan=612 deauthMethod=RADIUS type=Cisco::WLC_5500 UMHBVlan=611 ForeignVlan=612 isolationVlan=617 The radius secret IS present in the default switch which is why I though it would take that value. Regardless, I am very thankful for your assistance. My users were getting a bit restless : ) Jake Sallee Godfather of Bandwidth System Engineer University of Mary Hardin-Baylor WWW.UMHB.EDU 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221 ________________________________________ From: James Rouzier [[email protected]] Sent: Monday, September 15, 2014 11:53 AM To: [email protected] Subject: Re: [PacketFence-users] SOLVED - Switch in switchs.conf but not in radius_nas table Jake it will use values from the default switch. However if you have an empty parameter like this [a.b.c.d] ... radisSecret= It will not use the value from the default switch since the switch has an entry for it. In order for the switch inherit from the default switch remove the line entirely. James Rouzier [email protected] :: +1.514.755.3630 :: http://www.inverse.ca Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence (http://www.packetfence.org) On 2014-09-15 12:28 PM, Sallee, Jake wrote: > Interesting! > > The entries did not have a radius secret, I erroneously thought that if you > omit the field it would pull the value from the default switch like it does > in the GUI. It did not. > > Once I added the secret they did indeed populate correctly. Thank you James! > Inverse to the rescue once again. > > Jake Sallee > Godfather of Bandwidth > System Engineer > University of Mary Hardin-Baylor > WWW.UMHB.EDU > > 900 College St. > Belton, Texas > 76513 > > Fone: 254-295-4658 > Phax: 254-295-4221 > > ________________________________________ > From: James Rouzier [[email protected]] > Sent: Monday, September 15, 2014 10:58 AM > To: [email protected] > Subject: Re: [PacketFence-users] Switch in switchs.conf but not in radius_nas > table > > Jake can you verify if those new switches have the radiusSecret set. > If they do not they will not be added to the radius_nas table. > > James Rouzier > [email protected] :: +1.514.755.3630 :: http://www.inverse.ca > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence > (http://www.packetfence.org) > > On 2014-09-15 11:49 AM, Sallee, Jake wrote: >> Hello all! >> >> Interesting problem, I added several switches to my switches.conf manually >> since it is MUCH quicker than adding them individually in the GUI. However >> they are not showing up in the radius_nas table which is causing FreeRADIUS >> not to respond to the auth requests. >> >> I have restarted the PF services and done a pfcmd configreload and even >> configrelaod hard ... no joy :( >> >> pfcmd checkup returns normal. >> >> I will continue to work on this but any advice you can offer is greatly >> appreciated. >> >> Jake Sallee >> Godfather of Bandwidth >> System Engineer >> University of Mary Hardin-Baylor >> WWW.UMHB.EDU >> >> 900 College St. >> Belton, Texas >> 76513 >> >> Fone: 254-295-4658 >> Phax: 254-295-4221 >> >> ------------------------------------------------------------------------------ >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> _______________________________________________ >> PacketFence-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/packetfence-users > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
