Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. [Netdot - Feature #1711] Allow containers/subnets in bigger
subnets ([email protected])
2. [Netdot - Feature #1711] Allow containers/subnets in bigger
subnets ([email protected])
3. [Netdot - Feature #1711] Allow containers/subnets in bigger
subnets ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Wed, 28 Nov 2012 11:27:38 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1711] Allow
containers/subnets in bigger subnets
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1711 has been updated by Wim Vandersmissen.
I could, but am I not losing features of 'subnets' then?
The 10.120.0.0/21 is the actually routed subnet, and has been autodetected,
with correct vlan info.
If I change this to a container the vlan info is gone (and maybe some other
subnet features that I'm not aware of?)
If there is no further impact in the system for changing from subnet to
container, this would be a good solution. But I don't have enough knowledge
about this yet :)
----------------------------------------
Feature #1711: Allow containers/subnets in bigger subnets
https://osl.uoregon.edu/redmine/issues/1711#change-3022
Author: Wim Vandersmissen
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
E.g. we have a 10.120.0.0/21 subnet routed, that we internally split up in 8 x
/24's.
We would like to delegate DNS for each /24 to another entity.
When trying to create a container or subnet (management zone) for 10.120.0.0/24
this fails
"Block allocations only allowed under Container blocks: 10.120.0.0/24 within
10.120.0.0/21"
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Wed, 28 Nov 2012 11:39:34 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1711] Allow
containers/subnets in bigger subnets
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1711 has been updated by Carlos Vicente.
Wim Vandersmissen wrote:
> I could, but am I not losing features of 'subnets' then?
>
> The 10.120.0.0/21 is the actually routed subnet, and has been autodetected,
> with correct vlan info.
> If I change this to a container the vlan info is gone (and maybe some other
> subnet features that I'm not aware of?)
>
> If there is no further impact in the system for changing from subnet to
> container, this would be a good solution. But I don't have enough knowledge
> about this yet :)
I see. So it's a real subnet.
This is basically the same as #802. It's doable, but not trivial because it
affects a lot of other stuff.
----------------------------------------
Feature #1711: Allow containers/subnets in bigger subnets
https://osl.uoregon.edu/redmine/issues/1711#change-3023
Author: Wim Vandersmissen
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
E.g. we have a 10.120.0.0/21 subnet routed, that we internally split up in 8 x
/24's.
We would like to delegate DNS for each /24 to another entity.
When trying to create a container or subnet (management zone) for 10.120.0.0/24
this fails
"Block allocations only allowed under Container blocks: 10.120.0.0/24 within
10.120.0.0/21"
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 3
Date: Wed, 28 Nov 2012 11:47:01 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1711] Allow
containers/subnets in bigger subnets
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1711 has been updated by Wim Vandersmissen.
Yes, a real subnet and it's indeed the same feature.
If I would use a container as you suggest, could you tell me what the impact is
? What are the gotcha's?
----------------------------------------
Feature #1711: Allow containers/subnets in bigger subnets
https://osl.uoregon.edu/redmine/issues/1711#change-3024
Author: Wim Vandersmissen
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
E.g. we have a 10.120.0.0/21 subnet routed, that we internally split up in 8 x
/24's.
We would like to delegate DNS for each /24 to another entity.
When trying to create a container or subnet (management zone) for 10.120.0.0/24
this fails
"Block allocations only allowed under Container blocks: 10.120.0.0/24 within
10.120.0.0/21"
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 68, Issue 10
********************************************
