Hi Everyone,
Is there a notion that auto-configured IPv6 addresses based on
globally unique prefixes are transient compared to manually configured
ones?
I know that we could configure them to have infinite lifetimes & such,
but I am thinking of a large IPv6 deployment where these addresses are
expe
Hi,
Perhaps a naive question, but can somebody mention some practical use
cases for advertising multiple prefixes in a Router Advertisement?
Thanks & Regards
Vijay
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative
mcast address
because I might also be sending
packets with this address as source address)
thanks & regards
Vijay
On Fri, Sep 18, 2009 at 11:24 PM, Suresh Krishnan
wrote:
> Hi Vijay,
>
> On 09-09-18 11:17 AM, Vijayrajan ranganathan wrote:
>>
>> Hi,
>> If I w
Hi,
If I want to use more than 1 loopback IPv4 address, I can
assign one from 127.0.0.0/8 address range.
Does IANA reserve some IPv6 address range for loopback communication?
If not, what is the best address range to use for assigning such an
IPv6 address?
Thanks & Regards
Vijay
-
ul 8, 2009 at 6:23 PM, Tim Chown wrote:
> On Fri, Jul 03, 2009 at 07:28:31AM +0100, David Malone wrote:
>> On Thu, Jul 02, 2009 at 12:40:20PM +0530, Vijayrajan ranganathan wrote:
>> > Is there a standard solution for this kind of problem?
>>
>> On some OSes it is possib
do these come from?
What happens if they need to host a large number of virtual OSes,
do they pre-allocate these, any ideas?
Thanks & Regards
Vijay
On Thu, Jul 2, 2009 at 4:45 PM, Aleksi Suhonen wrote:
> Vijayrajan ranganathan wrote:
>>
>> I did consider using vlans but
> On Thu, Jul 02, 2009 at 12:40:20PM +0530, Vijayrajan ranganathan wrote:
>> Is there a standard solution for this kind of problem?
>
> On some OSes it is possible to control the host part of the
> autoconfigured address by manually configuring a link local address
> before the int
Hi Thomas,
I have an interface that is shared by multiple virtual hosts on the box, each of
which requires autoconf addresses. The one standard address can't be shared
as, in my implementation, the IP address is the one that uniquely identifies
the virtual host for an incoming connection.
These ad
pecific value, don't bother copying
> the mac, hash it then put in your filler.
>
> Tony
>
>> -Original Message-
>> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of
>> Vijayrajan ranganathan
>> Sent: Tuesday, June 23, 2009 10:09
Hi Jeffrey,
Reply inline.
> RFC 4291 states in section 5.1:
>
> "For all unicast addresses, except those that start with the binary value
> 000, Interface IDs are required to be 64 bits long and to be constructed in
> Modified EUI-64 format."
=> I am not sure this is not the only way I can form
Hi Everyone,
I have an ethernet interface for which I am defining the Interface-ID
in a different manner.
For an ethernet interface with MAC "34-56-78-9A-BC-DE", I am defining
the Interface-ID to be "34-56-78-xy-zw-9A-BC-DE" instead of
"36-56-78-FF-FE-9A-BC-DE"
where x,y,z,w are my implementatio
Hi Everyone,
I have an ethernet interface for which I am defining the Interface-ID
in a different manner.
For an ethernet interface with MAC "34-56-78-9A-BC-DE", I am defining
the Interface-ID to be "34-56-78-xy-zw-9A-BC-DE" instead of
"36-56-78-FF-FE-9A-BC-DE"
where x,y,z,w are my implementatio
12 matches
Mail list logo
