Thursday, 2014-08-14

*** nowen (~nowen@50-194-249-125-static.hfc.comcastbusiness.net) has joined #wikid12:51
*** coolacid (~CoolAcid@unaffiliated/coolacid) has joined #wikid17:49
*** nowen has quit (Remote host closed the connection)18:18
*** nowen (~nowen@50-194-249-125-static.hfc.comcastbusiness.net) has joined #wikid18:18
nowenhello18:25
*** Angel__ (8ad220aa@gateway/web/freenode/ip.138.210.32.170) has joined #wikid18:31
Angel__Hey Nick, you there?18:32
nowenyep18:32
nowenglad you made it18:32
Angel__How are ya?18:32
nowengood.  you?18:32
Angel__Ok this week we are moving buildings arg. I don't know if you ever received my email with a support question.18:33
nowenyes, I responded asking if there was more than one network client using radius18:33
nowenwe're moving next week.  not a lot of fun18:34
Angel__Sorry I missed that email. At the moment I have several configured but only one actually being used.18:35
nowendue to limitations of radius, you can only have one network client per domain.18:36
nowenwe're looking for a fix, but I'm not sure when or even if it will work18:36
Angel__We do have a second domain configured and wanted the second network client to use it.18:37
nowenwell, that should work fine18:37
Angel__So yes we are trying the configuration of one network client per domain.18:37
nowenhmm18:37
Angel__IF you notice the image in the email showing our Domains there should be two18:38
nowenojk18:40
nowenok18:40
nowenuser is enabled?18:41
Angel__On the Notice where my user account is showing enabled.18:41
nowenthe .55 IP address is the 2nd network client?18:44
Angel__.5318:44
nowenthe log is showing the request coming from .55, so it's checking against the domain associated with that network client18:45
Angel__ignore18:45
Angel__So what you were saying is that I would need to have another network client with a separate IP18:46
nowenyes18:46
Angel__The network client would not be able to use the same IP is that correct.18:46
nowencorrect18:46
nowenradius uses the NAS IP to analyze the packets18:47
Angel__Ok I will configure our Netscaler with a second IP on the same subnet then.18:48
nowenthat should work18:52
Angel__Can you take a look at the email I just sent Nick? Thanks.19:01
nowenlooks ok - did you create a second one for the netscaler?19:03
nowenand restart the wikid service afterward?19:04
Angel__the one that says cl-ns-2 should be the second one. I have not put that ip on the Netscaler yet. I am doing a TCPDUMP from the WiKID server and noticed that the RADIUS traffic is flowing through the .5519:06
Angel__The problem is that yesterday I changed that to domain External219:06
Angel__But seemingly users associated with -External seem to be passing through to the .5519:07
Angel__Am I missing something?19:07
Angel__Is it because I did not restart the WiKID services?19:08
nowenI'm confused - you haven't up the cl-ns-2 ip address on the netscaler yet?19:08
Angel__No19:08
nowenthen traffic can't be coming from it, right?19:09
Angel__Because I have been trying to figure out what path WiKID is sending RADIUS inquiries to so I know which IP is actually being used.19:09
Angel__I'm just further confused by the fact that it's using .55 which I originally did have on -External domain and for testing changed it to the -External2 domain19:10
Angel__Unless the services require a restart when changing the Network client configurations. Is that true?19:11
nowenthat is true19:11
nowenbut19:11
nowenradius uses whatever IP the traffic is coming19:11
nowenfrom19:11
nowenso, if tcpdump shows it coming from .55, it will use the network client mapping it finds first19:11
nowenso, I think you need to add the IP to the netscaler and restart wikid, Angel__20:12
*** nowen has quit (Quit: Leaving.)21:25

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!