Feature Request: PPPoE option 82

RouterOS General
1

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/12_4t4/htecidtg.html and Juniper http://www.juniper.net/techpubs/en_US/junose9.3/information-products/topic-collections/broadband-access/dsl-forum-vsas-in-aaa-access-and-accounting-messages.html#id-55548 http://www.juniper.net/techpubs/en_US/junose9.3/information-products/topic-collections/broadband-access/radius-dsl-vsa.html etc.

Here is the RFC http://www.faqs.org/rfcs/rfc4679.html
http://odysseus.ieee.org/cs.html?url=http%3A%2F%2Fwww.ieee802.org%2F1%2Ffiles%2Fpublic%2Fdocs2006%2Fliaison-dslf-tr-101-1006.pdf&charset=iso-8859-1&qt=tr-101&col=stds&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 ?

2

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 .

3

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

4

“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 =)

5

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

6

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 .

7

Mikrotik staff ?

8

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

9

Will included in next version ?

http://forum.mikrotik.com/t/dhcp-server-option-122/39296/3

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

10

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

11

Are we speaking of PPPoE intermediate Agent ?

See my article

http://www.brisenet.net/www.brisenet.net/Telecom_philanthropy_blog/Entries/2009/1/2_E-9-1-1_VoIP_over_DSL_WHOLESALE.html

F.

12

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

13

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.

14

what about bellow one ?

261 (0x0105)  Vendor-Specific        See the reference        [RFC2516]

in my previous there are a lot of useful links about standards .

15

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)

16

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 .

17

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

18

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

19

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?

20

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 :slight_smile: