Unfortunately Mikrotik Radius Client does not pass some radius attributes to radius server . They described in following documents and supported by Cisco http://cisco.com/en/US/docs/ios/12_4t/1 ... cidtg.html and Juniper http://www.juniper.net/techpubs/en_US/j ... l#id-55548 http://www.juniper.net/techpubs/en_US/j ... l-vsa.html etc.

Here is the RFC http://www.faqs.org/rfcs/rfc4679.html
http://odysseus.ieee.org/cs.html?url=ht ... &n=1&la=en


Also in some Dslams it named "PPPoE Intermediate Agent" , TR-101 (WT-101)

How can i pass "Access-Node-Identifier" , "Agent-Circuit-Id" , "Agent-Remote-Id" to radius server ?

Anyone interested ?
It is very useful . for example with "Agent-Circuit-Id" you can understand which user connected to which port of dslam . in large deployments with centralized RADIUS server it adds more flexibility to network .

Mikrotik stuff ?
I have sent Ticket#2010062166000111 but there is no reply . Please reply here or there .

"Agent-Circuit-Id" and "Agent-Remote-Id" (Option 82) works fine with DHCP+RADIUS, but in case of PPPoE, your router should do insertion, not just resending... so you should wait for support response =)

Isn't a way to do that job manually ? for example a routeros script or something else . maybe a trick ?

Hello,

Thank you for the feature request.
DHCP and PPP implementations are completely different.
We will see what we can do for the requested feature.

Regards,
Sergejs

May this feature available in 4.11 ?
Please do it if possible . i think it is the only way to really prevent bad behaviors like mac spoofing in PPPoE based DSL networks .

Mikrotik staff ?

We are researching the particular option, we will se what we can do.

Will included in next version ?

http://forum.mikrotik.com/viewtopic.php ... 88#p218588

Option specifics are exlained in RFC
http://www.networksorcery.com/enp/rfc/rfc3495.txt
From RFC
+------+--------+----------------+----------------+---+----------------+
| 122 | Length | Sub-option 1 | Sub-option 2 |-----| Sub-option n |
+------+--------+----------------+----------------+---+----------------+

+-------------------+--------+------------------------+
| Sub-option Code | Length | Sub-option information |
+-------------------+--------+------------------------+

You need to write this information as hexadecimal value into dhcp options configuration

Why don't implement a general way like dhcp hexadecimal options ?

Unfortunately this feature does not included in 4.11 . It is very simple to implement and very useful . when it will be supported ?

Are we speaking of PPPoE intermediate Agent ?

See my article

http://www.brisenet.net/www.brisenet.ne ... ESALE.html

F.

Yes . exactly .
Thanks for good article . maybe mikrotik stuff read your article and find why this feature is so important .

is that part of some standard. We really do not like introduce some tags, that are not supported by anything else for something that has strict standard set.

you cal look at http://www.iana.org/assignments/pppoe-parameters to see, if any of these tags, that are not vendor specific would fit for requested functionality.

what about bellow one ?
in my previous there are a lot of useful links about standards .

Hi, is it possible to do these things:
1. MT as dhcp server, use radius=yes
2. freeradius on a FreeBSD
3. mysql (on t5he FreeBSD too)

MT dhcp send to freeradius data from option 82 (switch, port number, vlan)
I need to dhcp option 60 (vendor class id) send from MT dhcp via use radius=yes to FreeBSD freeradius.....
The task is identify MS windows clients (MSFT 5.0) and other clients.....
What I can do to achieve this)

What if we pay for developing this feature ?
We need this PPPoE option 82 . it is a must . we could negotiate about fee and payment .

support@mikrotik.com
or, probably, sales@mikrotik.com =)

I tried your suggestion and mikrotik reply is

Hello,

We do not offer such service.

Probably we will add this function in the future.

Regards,
Sergejs

I am sorry, maybe I am completely wrong, but why the dslam doesn´t act as PPPoE concentrator itself? Why do you need RouterOS as PPPoE concentrator for DSLAM? Or is this any kind of PC-based DSLAM?

few dslams brands can act as pppoe concentrator and their implementations are very simple and buggy . We want routeros for pppoe concentrator because it is routeros

Thanks for explication.

I need this too, I have some dslams and we need to control (put some rules) about where the user can be connected (port for example)

We use freeradius and I have only enabled the pppoe-intermediate-agent from DSLAM but the PPPoE server from Mikrotik does not pass the information to FreeRadius

This option is too important for us, when mikrotiks developers will add it on the RouterOS?

Thanks in advance!

is this feature added to RouterOS/MikroTik ?

no any new news on new year ?

We are researching the particular option, we will se what we can do.

Long researching sergejs

3 Years for researching :-" ...

Most of modern D-Link (even D-Link!) Switches support pppoe circuit-id insertion. And of course most of other vendors.

We want mikrotik only to retranslate circuit-id options to radius server.

What about implementation this feature in RouterOS v6?

See following post
http://forum.mikrotik.com/viewtopic.php ... 33#p364765

Does this feature request implemented in this version ?
PPPoE option 82 or ticket number Ticket#2010062166000111

No, currently option 82 support is added to DHCP Relay only.

It's sadly ((

Believe it will be implemented in ROS 7

I hope so. This is a must have feature!

ROS 6.0 realesed but still Deep researching ... .
this is one of feature that will force us to use the cisco devices.

Not yet ?? ROS 6.1 and 6.2 Released ...

I think it is good time to ask for this feature http://forum.mikrotik.com/viewtopic.php?f=2&t=79166

BUMP

Very, very much needed support pppoe circuit-id. For transmission to the Radius.
I beg do, please.

BUMP

Question to the developers MikroTik.
How to buy licenses Level 6 that adds support pppoe circuit-id ?

5 years researching ...
no any news !!?

Напрашивается несколкьо выводов.
1. Уволился разработчик pppoe модуля - на нового бютжет по зарплате не расчитан.
2. Кто-то дал много денег компании Mikrotik, чтобы не лезли на рынок, к большим игрокам, т.к. данная функция повышает интерес у провайдеров к данному продукту.
3. Большие игроки пока по хорошему "попросили" некоторые функции не реализовывать.
4. Но скорей всего Микротик - разрабатывает те функции которые спрашивают чаще всего.
Посчитали, что функция "pppoe circuit-id" привлечет максимум - до 100 провайдеров, те купят по 3-6 лицензий - сумма не большая против того, что можно заработать на Roadboard.

Да к стати есть проэкт accel-pppd (http://sourceforge.net/projects/accel-ppp/) разрабатывается одним человеком. Там данныя фукция реализовання одной из первых.
И когда микротик дал понять что PPPoE option 82 можно не ждать - вдолгих поисках нашелся accel-pppd.
Как PPPoE и IPoE - лучнее решение на сейчас - и главное бесплатно!!!.
Для мелких провадйров - супер.
А для круптых - так себе.
Вот к примеру нам нужен был 3й сервер PPPoE. ОС планировался mikrotik - выделили деньги, но тут подвернулся accel-pppd. После изучения, настройки и испытаний - деньги что планировали на лицензию mikrotik - ушли на отдых, пиво.....

5 years researching ...
no any news !!?

its like vlan id for radius on user manager, we have to use freeradius

5 years researching ...
no any news !!?

its like vlan id for radius on user manager, we have to use freeradius

can't be use that , refer to first posts of this topic .

Напрашивается несколкьо выводов.
1. Уволился разработчик pppoe модуля - на нового бютжет по зарплате не расчитан.
2. Кто-то дал много денег компании Mikrotik, чтобы не лезли на рынок, к большим игрокам, т.к. данная функция повышает интерес у провайдеров к данному продукту.
3. Большие игроки пока по хорошему "попросили" некоторые функции не реализовывать.
4. Но скорей всего Микротик - разрабатывает те функции которые спрашивают чаще всего.
Посчитали, что функция "pppoe circuit-id" привлечет максимум - до 100 провайдеров, те купят по 3-6 лицензий - сумма не большая против того, что можно заработать на Roadboard.

Adding a feature like this not so hard , if they think may be conflict with another parts of RouterOS , can add it like a option of PPPoE Server if enable it enable this feature on that PPPOE server , Easily !

@Maksel , translate Russian to English via google translate is bad .

http://forum.mikrotik.com/viewtopic.php?f=21&t=101948
*) ppp - added new option under "ppp aaa" - "use-circuit-id-in-nas-port-id";

this option added , but because of Dynamic Queues cant be changed after 6.32 my radius can't use dynamic rate , I must use 6.31 without new PPP option

this option added , but because of Dynamic Queues cant be changed after 6.32

You should use CoA instead; starting from 6.33 it should now be supported as well:

*) ppp - added CoA support to PPPoE, PPTP & L2TP (Mikrotik-Recv-Limit, Mikrotik-Xmit-Limit, Mikrotik-Rate-Limit, Ascend-Data-Rate, Ascend-XMit-Rate, Session-Timeout);

Does any one tested 6.35rc19

It should support option 82

*) pppoe - added rfc4679 support;

In version 6.33 Now i have version 6.33.3 and use-circuit-id-in-nas-port-id works fine . I did not test newer versions and other parts of rfc4679

Now i have version 6.33.3 and use-circuit-id-in-nas-port-id works fine .

Where does RouterOS get this data?

I see the data from RouterOS directly. For exapmle NAS-Port-Id = "vlan21". Is it possible to get data from the switch where the clients are connected? A switch has "pppoe intermediate-agent" option.