Poll of opinions for new keyword

Arran Cudbard-Bell a.cudbardb at freeradius.org
Fri Sep 8 04:16:29 CEST 2017

> On 7 Sep 2017, at 23:47, Alan DeKok <aland at deployingradius.com> wrote:
> On Sep 7, 2017, at 9:36 AM, Winfield, Alister <Alister.Winfield at sky.uk> wrote:
>>   recv Access-Request {
>>   subrequest dhcp {
>  Hmm... putting the protocol there is a reasonable choice.
>  But... the issue is we also need to run the DHCP state machine:
> 	recv foo  {
> 	}
> 	send foo {
> 	}
>  etc.  The idea is that *all* DHCP packets undergo the same processing.  Which avoids the weird issues we have in v3 with inner-tunnel sometimes not being the same as the default server.

The DHCP and RADIUS state machines deal with doing the correct thing across system boundaries.

They're concerned with take a request off the wire, converting it to our internal, generic representation of a request, processing it through a bunch of different sections, and converting our generic representation of a response back into wire format.

There's great variance between the protocols as to what those state machines are required to do.

The subrequest sections would be largely protocol agnostic, there's no different behaviour required when conjuring a DHCP packet, or a RADIUS packet or any other kind of packet. They'd be more like the wire format side of the system boundary, so a generic state machine could be used for all subrequests.

>>   update request {
>>   Request-Packet-Type := Discover
>>   }
>>   dhcp
>  That's better done via Matthew's suggestion:
> 	call server.Packet

dhcp in this case would by the dhcp client module, there's not a whole lot of point going through another virtual server in that case?

Not sure "call" is the best name, but not sure "proxy" or "forward" is any better.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20170908/3a704f66/attachment.sig>

More information about the Freeradius-Users mailing list