[Possible Spam]Re: dhcp with multiple dhcp-relay routers

mjones at mnsi.net mjones at mnsi.net
Thu Oct 30 15:27:11 UTC 2025


Alan

	My apologies.   As it turns out the original information I was given to figure out was flawed so sent me on a wild goose chase.   In future I will attempt to post correctly.

Mark Jones
Operations
Managed Network Systems
Windsor Desk 519-258-2333 x8417
Cell 226-340-1254



-----Original Message-----
From: Freeradius-Users <freeradius-users-bounces+mjones=mnsi.net at lists.freeradius.org> On Behalf Of Alan DeKok via Freeradius-Users
Sent: Wednesday, October 29, 2025 6:49 AM
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
Cc: Alan DeKok <alan.dekok at inkbridge.io>
Subject: Re: [Possible Spam]Re: dhcp with multiple dhcp-relay routers

On Oct 28, 2025, at 4:37 PM, mjones at mnsi.net wrote:
> Just ran a quick debug again so I get my story straight

  Is there any particular reason only posted a tiny portion?

  All of the documentation says to post the FULL DEBUG OUTPUT.  When you join the list, the introductory message tells you to do this.

> The key in dhcp_sqlippool is
> 
>       pool_key = "%{%{DHCP-Client-Identifier}:-%{DHCP-Client-Hardware-Address}}"

  Which is also shown in the full debug output...

> Debug is as follows
> 
> Tue Oct 28 16:32:24 2025 : Debug: (1121)   DHCP-Gateway-IP-Address = 10.180.144.2

  And that has the full dates, which is from "freeradius -Xx", and not "freeradius -X" as the documentation suggests.  That makes it more difficult to read the output.

> Tue Oct 28 16:32:25 2025 : Debug: DHCP: No Pool-Name defined (cid %{DHCP-Client-Identifier} chaddr %{DHCP-Client-Hardware-Address} giaddr %{DHCP-Gateway-IP-Address})

  Maybe this message is useful?

> These are the same request being relayed from the two different routers.

  And running in threaded mode.  Which means that the log messages from one request are mixed with log messages from another request.  Which makes it more difficult to read the output.

 Plus, if you read the output, you'll see that there are 3 different packets, not two.

>   One matches the existing ip the other does not as the query is using the giaddr.

  No, the query is not using the giaddr.

>  Unless I am misunderstanding the debug.

  Yes, you are misunderstanding the debug.

  It is extremely difficult to understand the debug output when you don't follow the documentation.  Using "freeradius -X" means that you don't get every debug line prefixed with a date (which is unnecessary).  It also means that the server runs in single threaded mode, which means that you get the debug output for one request all grouped together.  Then, the debug output for a second request is also grouped together.

  It doesn't matter whether you're using docker, or some other system to get the debug output you posted above.  That method is wrong, and is making it harder for you to see what's going on.

  Use "freeradius -X" to debug the server.  Using anything else is guaranteed to be painful and frustrating.

  As for the specific issue you're running into, perhaps try defining a Pool-Name attribute?  If you read the REST of the debug output, you'll see that the module returns "noop" when there isn't a Pool-Name.  i.e. it doesn't allocate an IP address.

  And the rest of the debug output would also show that it's not doing SQL queries when the Pool-Name isn't defined.

  But I can't show that here, because you've "helpfully" deleted most of the debug output.  And it's difficult to tell that's what's going on, because the server is running in multi-threaded mode, and the log messages for different requests are all mixed up.

  In short, configure the server as documented.  Debug it using the documented method.  Post the FULL debug output to the list.  Don't go out of your way to make it as difficult as possible for people to help you.

  If the tone of this message surprises you, then understand that ALL of this is documented extensively.  It is not particular pleasant to answer questions when the content essentially begins with "Yeah, I'm not going to read the documentation or do what it says".

  Alan DeKok.

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



More information about the Freeradius-Users mailing list