Re: [RADIATOR] strip attributes from access-reject

2014-12-15 Thread Mueller, Jason C
ms based on the Client Identifier. > > Robert Fisher > Systems Administrator > Sitestar Internet Services > > On 12/15/2014 9:47 AM, Mueller, Jason C wrote: >> Is there a way to not include radius attributes, when sending a RADIUS >> access-reject? >> >> I h

[RADIATOR] strip attributes from access-reject

2014-12-15 Thread Mueller, Jason C
Is there a way to not include radius attributes, when sending a RADIUS access-reject? I have AddToReply attributes in the client stanza. I need to send different attributes based on the device type that is being authenticated against, which is why the AddToReply config is in the client stanza.

Re: [RADIATOR] on Windows Server ?

2013-11-11 Thread Mueller, Jason C
It looks like upgrading Perl is our fix. Now on to upgrading everything. :-( It could be worse, so I will be happy that a Perl upgrade seems to have fixed the issue. -Jason On Nov 8, 2013, at 9:15 AM, Heikki Vatiainen wrote: > On 11/05/2013 09:22 PM, Mueller, Jason C wrote: > >>

Re: [RADIATOR] on Windows Server ?

2013-11-05 Thread Mueller, Jason C
Heikki, On Nov 4, 2013, at 3:34 PM, Heikki Vatiainen wrote: > On 11/01/2013 08:58 PM, Mueller, Jason C wrote: > >> I created a Perl script independent of Radiator that called Sys::Syslog and >> sent a message to the remote host. That worked using UDP. > > That's

Re: [RADIATOR] on Windows Server ?

2013-11-01 Thread Mueller, Jason C
Heikki, I created a Perl script independent of Radiator that called Sys::Syslog and sent a message to the remote host. That worked using UDP. Here are the stanzas I created in the Radiator config file: Identifier syslog LogSock udp LogHost IP_ADDRESS_OF_REMOTE_HOST

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-30 Thread Mueller, Jason C
Heikki, On Jun 28, 2013, at 1:58 PM, Heikki Vatiainen wrote: > On 06/28/2013 07:56 PM, Mueller, Jason C wrote: > >> I have currently relented to specifying every individual IP address >> that needs to listen for RADIUS across the set of systems running >> Radiator (bot

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-30 Thread Mueller, Jason C
Heikki, On Jun 28, 2013, at 1:58 PM, Heikki Vatiainen wrote: > On 06/28/2013 07:56 PM, Mueller, Jason C wrote: > >> I have currently relented to specifying every individual IP address >> that needs to listen for RADIUS across the set of systems running >> Radiator (bot

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Mueller, Jason C
CIDR notation for IPv6 is critical. That is the industry standard way of notating IPv6. Is there any plan for IPv6 CIDR support in the future? If so, what timeframe? Thanks for your help. -Jason On Jun 28, 2013, at 9:38 AM, Heikki Vatiainen wrote: > On 06/28/2013 03:17 PM, Mueller, Jason

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-28 Thread Mueller, Jason C
Heikki, > When BindAddress is set to ipv6::: and request comes in from an IPv4 > address 172.20.3.170 you'll get this in the logs: > > DEBUG: client_addr: > <0><0><0><0><0><0><0><0><0><0><255><255><172><20><3><170> > > When BindAddress is commented out and defaults to IPv4 0.0.0.0 you'll > get t

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-27 Thread Mueller, Jason C
Alan, > Hi, > >> Quick summary again, when using ipv6::: and bindv6only set to 0: >> * Both IPv4 and IPv6 traffic gets to Radiator >> * IPv6 works with everything I have tried >> * IPv4 clients will not match on the proper client stanza, only the DEFAULT >> client stanza > > I have the followin

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-27 Thread Mueller, Jason C
s with everything I have tried * IPv4 clients will not match on the proper client stanza, only the DEFAULT client stanza Let me know if you have any more questions. I hope that helps to clarify the issue. I would appreciate any help in resolving it. Thanks. -Jason On Jun 27, 2013, at 8:07

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-27 Thread Mueller, Jason C
Christian, >>> According to section 5.5 in the Radiator 4.11 reference manual >>> ("doc/ref.pdf") you need to specify both ipv6 and ipv4 like this: >>> >>> >>> BindAddress ipv6:::, 0.0.0.0 >> >> That syntax doesn't work on my system. The issue is not with the binding >> statement. I am able

Re: [RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-27 Thread Mueller, Jason C
Hugh, > According to section 5.5 in the Radiator 4.11 reference manual > ("doc/ref.pdf") you need to specify both ipv6 and ipv4 like this: > > > BindAddress ipv6:::, 0.0.0.0 That syntax doesn't work on my system. The issue is not with the binding statement. I am able to receive both IPv4 an

[RADIATOR] ipv6::: bind results in no match on IPv4 client

2013-06-26 Thread Mueller, Jason C
Hello, I am using Radiator 4.11. I will show relevant portions of my config and then comment on them (IP addresses changed and Secret ***'d out to protect the guilty): -- BindAddress ipv6::: AuthPort1812 AcctPort1813 # ipv6 client Secret *** DupInterval

Re: [RADIATOR] IPv6 equivalent to 0.0.0.0

2013-06-21 Thread Mueller, Jason C
Heikki, That works. Thanks for the info, as I did not find it in the reference manual. I just looked, and my reference manual is a PDF from 2008. I will update ASAP. Thanks again. -Jason On Jun 21, 2013, at 10:49 AM, Heikki Vatiainen wrote: > On 06/21/2013 04:06 PM, Mueller, Jason C wr

[RADIATOR] IPv6 equivalent to 0.0.0.0

2013-06-21 Thread Mueller, Jason C
I am trying to enable IPv6 on Radiator 4.11. When using the BindAddress configuration parameter, I have to specify an IPv6 address. When I specify an address that is in use by the local system, Radiator successfully binds to the IPv6 address. For example, I have a line like this in my radius.cf