[f-nsp] MLX with "route-only" port is forwarding VLAN1 BPDUs?

[Clement Cavadore]

Yes thats it ;)

Le 24 juin 2016 23:30:02 GMT+02:00, Gerald <gerald at ax.tc> a écrit :
>Oops, need sleep ;-)
>
>!
>int eth 1/2
> enable
> route-only
> ip addres 10.0.0.1/24
>!
>vlan 666 name dummy-layer3-vlan
> untag eth 1/2
>!
>
>Am 24.06.2016 um 23:27 schrieb Gerald:
>> Thx Clement for this advice, did you mean something like this:
>> 
>> !
>> int eth 1/2
>>  enable
>>  route-only
>>  ip addres 10.0.0.1/14
>> !
>> vlan 666 name dummy-layer3-vlan
>>  untag eth 2/12
>> !
>> 
>> 
>> Gerald
>> 
>> Am 24.06.2016 um 21:59 schrieb Clement Cavadore:
>>> You should create some "dummy" vlans on route-only ports, to avoid
>that. 
>>> No problem having untagged vlan on any port with IP/routing
>configuration. You even ca do this without any disturbance.
>>>
>>> Le 24 juin 2016 21:53:08 GMT+02:00, Gerald <gerald at ax.tc> a écrit :
>>>> The MLX got a reboot some weeks ago, this seems not to help. I'am
>>>> afraid
>>>> of your (1) note... :-(.
>>>>
>>>> Gerald
>>>>
>>>> Am 24.06.2016 um 21:27 schrieb Steven Raymond:
>>>>>
>>>>>> On Jun 24, 2016, at 1:19 PM, Gerald <gerald at ax.tc> wrote:
>>>>>>
>>>>>> Is there a way to stop this? I would have my "route-only" ports
>>>> Layer2
>>>>>> free and not disturb other Layer2 systems behind.
>>>>>
>>>>> Old old notes I found said basically 1) “bpdus are sent even with
>>>> route-only”, and 2) "you should reboot after applying route-only". 
>
>>>>>
>>>>> Both of which may not helpful to you.
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> foundry-nsp mailing list
>>>> foundry-nsp at puck.nether.net
>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>>

-- 
Sent from my phone.
Please excuse any typos or mistakes.
But not both !