[RADIATOR] Radiator with Windows Server 2008 DHCP

[Hugh Irvine]

Hello Richard -

Yes correct - Radiator is sending a DHCP request, but the DHCP server is not responding, presumably because it doesn't understand the request.

You will need to check the DHCP server log to find out what it thinks the problem is.

I am guessing, like Alan, that the problem is the PoolHint you are sending is not matching any address pools defined on the DHCP server.

BTW - what exactly are you wanting to do? It is more usual to have your NAS equipment set up to allocate IP addresses directly.

regards

Hugh


On 4 Aug 2010, at 18:32, Richard Fenner wrote:

> Hi Alan,
> 
> Just run a test using Wireshark on the DHCP end and all I get is the
> confirmation of 4 DHCP DISCOVER packets being received by the DHCP
> server and then no response. Presumably this means that Radiator is
> attempting to make a connection 4 times with each one failing for some
> reason?
> 
> Cheers,
> 
> Richard
> 
> -----Original Message-----
> From: radiator-bounces at open.com.au [mailto:radiator-bounces at open.com.au]
> On Behalf Of Richard Fenner
> Sent: 04 August 2010 09:16
> To: Alan Buxey
> Cc: radiator at open.com.au
> Subject: Re: [RADIATOR] Radiator with Windows Server 2008 DHCP
> 
> Hi Alan,
> 
> I don't quite follow what you mean regarding the PoolHint?
> 
> Also, I can confirm that the DISCOVER packets are being received at the
> DHCP server as they appear in the Windows Firewall logs. Will get
> Wireshark out and test where they go from there in a bit.
> 
> Cheers,
> 
> Richard
> 
> -----Original Message-----
> From: Alan Buxey [mailto:A.L.M.Buxey at lboro.ac.uk] 
> Sent: 03 August 2010 18:53
> To: Richard Fenner
> Cc: radiator at open.com.au
> Subject: Re: [RADIATOR] Radiator with Windows Server 2008 DHCP
> 
> Hi,
> 
>>      <AuthBy DYNADDRESS>
>>      AddressAllocator dhcpallocator
>>      PoolHint 255.255.255.240
>>      </AuthBy>
> 
> from the manual:
> 
> Note: the PoolHint supplied in the AuthBy DYNADDRESS clause must be a
> subnet
> definition that is understood by the DHCP server for the purposes of
> address allocation
> 
> 
> goodies/addressallocatordhcp.cfg  has a nice example config to look
> at....  I find
> if you are having issues and make no progress just looking at the
> RADIATOR
> debug logs, then look at the other end - see what your DHCP server is
> bleating
> about and check with eg wireshark, tcpdump or snoop, that traffic is
> going
> between the hosts involved!
> 
> alan
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB: 

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets), 
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.