We would really apriciate if you could add option 82 insert / replace at layer 2 as specified in SEC v4 (Secure enduser connection v4) page 10, 4.1.6
4.1.6 Traceability must be added to the DHCP-requests in “L2-mode” as in option 82
for example. The access switch must not be DHCP-relay.
http://www.sakerkundanslutning.se/wp-content/uploads/2010/07/SEC-2010-10-21.pdf
The rest of requirement for SEC v4 seems possible to fulfill with already existing function in Routeros.
Best regards,
Thomas
I haven’t tried, but it seem to me that they fixed this several years ago in the in the 3.3 release
*) fixed bug - DHCP server did not parse Relay-Agent-Info option 82;
Chupaka got it to work together with radius.
http://forum.mikrotik.com/t/dhcp-option-functionality/27258/1
Its not the same, using an SXT as and CPE in an layer2 network where no routing is handled we need support for inserting/replacing option 82 agent.circuit-id to identify the customers at a central dhcp-server. Many of our customers(network infrastrucure owners) dont handle layer3 and this is provided by a third party serviceprovider in “open networks”. End customer can choose from several diffrent serviceproviders from internet, telephony and tv. Theese service providers need to know where the dhcp-req originates and we dont know anything about their ip-addressranges or even what ip-address their dhcp-server is using. That one strong reason for implementing this feature.
For me it look like an pretty simple feature to implement, forward dhcp-request packet to cpu instead of uplink, add/replace option-82 with hostname and ingressport recalculate packet and send it out on intended uplink port. This function would only be imoplemented in bridging of course othervise we could use dhcp-relay functions.
Best regards,
Thomas