Would be nice if the routerOS dhcp-server allow logging with radius accounting.
We use dhcp-server from mikrotik and we need have a log of each IP we offer to each client and when, through radius.

Would be nice if the routerOS dhcp-server allow logging with radius accounting.
We use dhcp-server from mikrotik and we need have a log of each IP we offer to each client and when, through radius.

But... ALREADY you can do that...

Really?
In which version?

Sorry if already can do this

Really?
In which version?

Sorry if already can do this

I see that option (but i do not use this) on RouterOS 6.7+

I have a routerboards with 6.1v and 6.5v and not see that option.
Mikrotik manual http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server does not say anything about it, maybe it is not updated?

I have a routerboards with 6.1v and 6.5v and not see that option.
Mikrotik manual http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server does not say anything about it, maybe it is not updated?

When evaluate something, use near last version...

but I can see on the wiki the "use-radius" option.... you not?

It is also possible to hand out leases for DHCP clients using the RADIUS server, here are listed the parameters for used in RADIUS server.

About how it work, I do not know, I never try.

But that option doesn't make accounting, it just make authorization.
We need accounting.

Let me to give you an example:

1- device ask for IP to routerboard
2- routerboard ask for IP a radius server (autorization)
3- freeradius replies to routerboard with an IP address for the client
4- routerboard offer an IP to device

...this is what does the routerboard currently.

Even though, if it also does the accounting

1- device ask for IP to routerboard
2- routerboard ask for IP a radius server (autorization)
3- freeradius replies to routerboard with an IP address for the client
4- routerboard offer an IP to device
5- the router reports to server that provided the IP xxx to customer Y (accounting)

This allows to use a DHCP server and pool of IPs in the routerboard and only use the radius server for accounting of IPs offered:

1- device ask for IP to routerboard
2- routerboard offer a IP from own pool to a device
3- the routerboard reports to server that provided the IP xxx to customer Y (accounting)

Currently can not keep track of the IPs that the routerboard delivers to customers.

3- freeradius replies to routerboard with an IP address for the client
4- routerboard offer an IP to device
5- the router reports to server that provided the IP xxx to customer Y (accounting)

But this three passages can be done by user-manager...

I must verify that, but about FreeRADIUS, i do not use it.
I can try only on RouterOS user-manager.

3- freeradius replies to routerboard with an IP address for the client
4- routerboard offer an IP to device
5- the router reports to server that provided the IP xxx to customer Y (accounting)

But this three passages can be done by user-manager...

I must verify that, but about FreeRADIUS, i do not use it.
I can try only on RouterOS user-manager.

But... from user-manager manual:

Note, first local router database is consulted, then User Manager database. User will be unable to obtain DHCP lease, if DHCP router and User Manager server will not contain any information about user's data.

We not have any information from user data, is just a DHCP dynamic server.

But you want ANYONE connect, or only authenticated users?

Anyone.

Anyone.

>>>the dhcp-server allow logging with radius accounting
But accounting from one not existend account?
One account to be acconuted must be create first...

>>>we need have a log of each IP we offer to each client and when, through radius.
I think what you need is HotSpot to track on radius the IP offered...


what do you mean?

Feature request: DHCP accounting through Radius
description:
anyone connect to dhcp-server must be converted to radius user and be logged on radius for that user the ip offered to client and when

Just checked and on future 6.14 version are added this:
*) dhcp server - added option use-framed-as-classless and added support for DHCP-Classless-Static-Route RADIUS attribute;

Sorry, it is perhaps difficult to understand me because I'm not good with english.

>>>the dhcp-server allow logging with radius accounting
But accounting from one not existend account?

One account to be acconuted must be create first...

No. Is only account, not auth. Can be done, because are two different things:
Authentication and authorization allow or deny services.
Account keeps track of resources used.
...and can work together or independently.

For example:
PPPoE user dials but is not registered. His login fail because his account is not registered (auth), however his attempt is logged (account).
In the same way you can keep a log or "accounting" of things that are not registered.
Registration is not required for accounting.

...
Now I remember, this was already asked. Inclusive I voted for this!

http://forum.mikrotik.com/viewtopic.php?f=1&t=76840

The only difference is add the option of accounting also in the case that the allocation of IP is from a pool of the same routerboard (instead of assigning an IP from a remote radius server).

Use radius works but no accounting is sent for dhcp clients.


MIKROTIK PLEASE CONFIRM THIS IS GETTING ADDED\FIXED IN 6 OR 7!!!!!!?!???!?

+1 to implementation of DHCP accounting requests

+ 1

+1

I am amazed this is NOT already there.

Hi!
Any news about support of radius accounting from DHCP?

+1 for accounting

dhcp with accounting - please...

Related: http://forum.mikrotik.com/viewtopic.php?t=61770

also add support for MT-Rate-Limit attribute when using DHCP+RADIUS as already promised (Ticket#2016110222000039)

[*]

also add support for MT-Rate-Limit attribute when using DHCP+RADIUS as already promised (Ticket#2016110222000039)

This already exists! Use the Mikrotik-Rate-Limit VSA

[*]

also add support for MT-Rate-Limit attribute when using DHCP+RADIUS as already promised (Ticket#2016110222000039)

This already exists! Use the Mikrotik-Rate-Limit VSA

sorry, it's in the ticket I referenced, and wasn't entirely clear in this post. what I meant was full support, which means also setting parent queue property.

Below is the request from the referenced ticket which explains in more detail.

> I have a requirement where I must be able to set the parent
> queue on the dynamic queues created when authenticating a DHCP user via RADIUS and assigning
> the MT-Rate-Limit attribute. The queue is being created properly and works, but
> I am unable to figure out a way to assign the parent queue. The result
> is when oversubscribing the connection, the queues do not properly
> function since they do not have any parent defining the total amount of bandwidth available to the users.
>
> I would imagine that an optional setting added to the DHCP Server or
> the Network would be the appropriate place to add the parent queue
> value just like we have on the PPP profile.
>
> Any way that works is acceptable, however assigning the parent queue
> via RADIUS in such a way that also applies to PPP connections without
> needing to set it via the profile would be even better (but faster implementation is even more important).

Would be nice if the routerOS dhcp-server allow logging with radius accounting.
We use dhcp-server from mikrotik and we need have a log of each IP we offer to each client and when, through radius.

Seems that implemented on 4.41!
Now to test!