There is a solution.
Here is a working configuration. MX is not used as BRAS, it terminated Q-in-Q Distribution of IP addresses via DHCP relay.
ge-1/1/0 {
flexible-vlan-tagging;
encapsulation flexible ethernet services;
unit 890 {
proxy-arp restricted;
vlan tags outer 890 inner-range 801-845;
family inet {
mac-validate strict;
address Y.Y.Y.Y;
address X.X.X.X;
}
}
}
dhcp-relay {
forward-snooped-clients configured-interfaces;
server-group {
test {
Z.Z.Z.Z;
}
}
active-server-group test;
group test {
active-server-group test;
overrides {
allow-snooped-clients;
layer2-unicast replies;
trust-option-82;
proxy mode;
}
interfaces ge-1/1/0 .890;
}
}
Junos version 11.4R6.5
22.01.2013, 17:57, "Bjørn Skovlund" <[email protected]>:
> Your question is still a bit ambiguous.
>
> If you have an inner-list and want to bind it to a L3 interface, then you need to make a bridge domain and attach the IRB to that.
>
> Alternatively, depending on what you want, we're doing something along the lines of the below, where we bind the customers together in DHCP groups and relay them to a DHCP server with option-82, so we know which customer gets what IP - again, not sure if it's customers or what that you're trying to stitch together ;-)
>
> Cheers, Bjørn
>
> unit 301 {
> proxy-arp restricted;
> vlan tags outer 1198 inner 42;
> family inet {
> mac-validate strict;
> unnumbered-address lo0.0 preferred-source-address x.x.x.x;
> }
> }
>
> and under forwarding-options the dhcp relay:
> group data {
> active-server-group data;
> overrides {
> always-write-option-82;
> }
> relay-option-82 {
> circuit-id {
> use-interface-description logical;
> }
> }
> interface ge-0/0/0 .301;
> ......
> }
>
> On Mon, Jan 21, 2013 at 11:23 PM [email protected] <[email protected]> wrote:
>> Thanks for the reply.
>> I need to terminate Q-in-Q with multiple internal tags.
>> inner-list
>> Junos 11.4R1.14
>> Allows you to create only if the interface will be family bridge,
>> I need a L3 interface.
>>
>> 21.01.2013, 18:55, "[email protected]" <[email protected]>:
>>
>>>> Does MX ambiguous vlan?
>>> Please rephrase the question.
>>>
>>> If you're asking whether the MX80 supports dual port Ethernet
>>> traffic, the answer is yes. E.g.
>>>
>>> ge-1/0/0 {
>>> flexible-vlan-tagging;
>>> encapsulation flexible ethernet services;
>>> unit 11 {
>>> vlan tags outer 1063 inner 900;
>>> family inet {
>>> address 10.9.130.1/30;
>>> }
>>> }
>>> }
>>>
>>> Steinar Haug, Nethelp consulting, [email protected]
>>
>> -------- End forwarded message --------
>> _______________________________________________
>> juniper-nsp mailing list [email protected]
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
