I was in a similar position to you not that long ago. I got my LAN all dual
stack and was a happy camper. I wanted 100% IPv6 and never to see another
RFC 1918 address on my network again. Unfortunately it's just not practical.
My ReadyNAS doesn't talk v6. My mac doesn't appear to like v6 for the fi
What are your problems with using radvd? I have used it quite a bit on
FreeBSD (6.1) without any hassle. It's even written quite nicely in my
experience so working on patches for it should be quite do-able if there
are features missing.
He's saying that the router announcements don't contain a
I'm working on a piece of software that, among other things, allows an
administrator to easily configure IPv6 interfaces on a FreeBSD host. I've
run into a problem where whenever I reconfigure an interface with an IPv6
address FreeBSD marks the new address as being a duplicate.
The problem is that
On 5/6/09 7:27 AM, "Bruce Simpson" wrote:
>> The problem is that I'm following RFC 2461 [1] in that I send an unsolicited
>> neighbor advertisement to ff02::1 immediately after configuring the
>> interface.
>>
>
> How are you doing this? Do you do this from the kernel or from your own
> userl
On 5/6/09 3:06 PM, "JINMEI Tatuya / 神明達哉" wrote:
> I'm afraid we need clarification first...what do you mean by
> "reconfigure an interface with an IPv6 address"? Do you mean adding a
> new IPv6 address to an interface? If so, I'm not sure why you
> referred to the following part of RFC2461 (btw
that would
be a different thread.
I guess that changes my question quite a bit. If you randomly fire off an
unsolicited NA right after configuring an interface should that cause a DAD
failure?
-Bob
On 5/6/09 4:55 PM, "JINMEI Tatuya / 神明達哉" wrote:
> At Wed, 06 May 2009 15:49:45
ut
and clearing this up for me.
-Bob
On 5/6/09 10:47 PM, "JINMEI Tatuya / 神明達哉"
wrote:
> At Wed, 06 May 2009 17:17:52 -0700,
> Bob Van Zant wrote:
>
>> I guess that changes my question quite a bit. If you randomly fire off an
>> unsolicited NA right after configur
I'm experimenting with netgraph to try to implement an IPv6 -> IPv4 gateway,
as specified here:
http://tools.ietf.org/html/draft-xli-behave-ivi-02
This is my first time ever working with netgraph and I admit to being a bit
lost. I have a netgraph node that gets wired up with an ng_ether node. My
I have 2 FreeBSD machines each with 3 ethernet interfaces each with an IPv6
address.
Here's a table showing how the two machines are connected. To try to blame
the switch or its configuration I have tried directly connecting the
machines. The results were the same.
6.34948
rev=0x05
hdr=0x00
e...@pci7:8:0:class=0x02 card=0x016d1028 chip=0x10768086 rev=0x05
hdr=0x00
e...@pci9:4:0:class=0x02 card=0x10028086 chip=0x10268086 rev=0x04
hdr=0x00
em2 was the only device functioning properly on 6.2.
-Bob
On 7/23/09 9:32 PM, "Julian Elischer"
The following reply was made to PR kern/116837; it has been noted by GNATS.
From: Bob Van Zant <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/116837: ifconfig tunX destroy: panic
Date: Sun, 6 Jan 2008 22:46:09 +0530
My FreeBSD 7.0-PRERELEASE box has been running int
The following reply was made to PR kern/116837; it has been noted by GNATS.
From: Bob Van Zant <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc:
Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic
Date: Thu, 24 Jan 2008 12:40:19 +0530
I applied the patch
The following reply was made to PR kern/116837; it has been noted by GNATS.
From: Bob Van Zant <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc:
Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic
Date: Tue, 05 Feb 2008 10:04:08 +0530
I've been runni
13 matches
Mail list logo
