[Xorp-users] xorp VLAN create/delete usage question
Joe Coco
JoeCoco at mecnet.net
Wed Oct 5 05:03:51 PDT 2011
Hello,
I kind of like the idea of either an ENV or a startup option. Leaning more towards the startup option.
We're (considering) using Xorp in the following scenarios:
A. Gui creates interfaces/vlans, and XORP just performs dynamic routing
B. XORP does everything
C. Initial interface configuration created at startup, XORP has control later on.
I like the idea that based on a flag or switch, XORP would allow the adding, deleting, or modifying of any existing interface, or based on a different flag or switch XORP
would either leave any interfaces configured alone on exit, or cleanup on exit and discard them.
As to your initial concern, I don't completely understand why you would want to delete an interface from XORP's configuration but not have that interface modified in the OS.
Could you explain that a little?
-- Joe
-----Original Message-----
From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Ben Greear
Sent: Tuesday, October 04, 2011 7:07 PM
To: Eric S. Johnson
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] xorp VLAN create/delete usage question
On 10/04/2011 11:53 AM, Ben Greear wrote:
> On 10/04/2011 11:47 AM, Eric S. Johnson wrote:
>>
>> greearb at candelatech.com said:
>>> I just noticed that the vlan delete logic is messing up one of my
>>> own xorp configurations. Basically, I want to delete a vlan from
>>> the xorp config, but I don't want it deleted from the OS.
>>
>>> I can easily enough add some hack like an environment variable to
>>> disable all vlan deletes, but I was wondering instead if I should be
>>> more clever and maybe have xorp only delete vlans that it created?
>>
>> If you delete an interface that was previously created outside xotp
>> it deletes it.
>
> It does now...question is whether it should? Xorp has no concept of
> delete interface v/s remove xorp configuration for interface.
>
> I was thinking that if xorp didn't create the VLAN itself, it should
> not delete the VLAN from the OS when removing xorp configuration for
> that interface.
I just committed code that will cause xorp to only delete from the OS VLANs that it created earlier.
If anyone wants an env-variable to either force the VLANS to always be deleted, or never, I'll be happy to add it.
Adding a new flag to the configuration to allow users per-interface control of vlan deletion is more effort than I feel like putting in, but patches are welcome.
Thanks,
Ben
>
>>
>> So I would think vlan behavior should follow that paradigm, by default.
>> So I would vote for a env variable based behavior change.
>
> That's easily enough done, but might not be flexible enough for all
> users...
>
> Perhaps a better way would be an explicit per-interface flag that
> users could set..but that is a lot code...
>
> Thanks,
> Ben
>
>
>>
>> E
>
>
--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Xorp-users mailing list
Xorp-users at xorp.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
More information about the Xorp-users
mailing list