On Sun, Apr 26, 2015 at 10:10:36AM +0100, Roy Marples wrote:
>
> It sounds like accept_ra is disabled in the kernel (sysctl
> net.inet6.ip6.accept_rtadv, or on the interface (ndp -i jme0 | grep
> accept_rtadv).
> You can either enable them (ip6mode=autohost in rc.conf) or let dhcpcd
> manage th
On 27/04/2015 12:16, Ted Lemon wrote:
> On Apr 24, 2015, at 9:55 AM, Christos Zoulas
> wrote:
>> One of my ISProviders is TWC. If you don't use DHCPv6, what you end
>> up is the link-local address for each interface (which you get
>> anyway), and a default route to the link-local address of the T
On Apr 27, 7:16am, mel...@fugue.com (Ted Lemon) wrote:
-- Subject: Re: default ipv6 route?
| On Apr 24, 2015, at 9:55 AM, Christos Zoulas wrote:
| > One of my ISProviders is TWC. If you don't use DHCPv6, what you
| > end up is the link-local address for each interface (which you get
On Apr 24, 2015, at 9:55 AM, Christos Zoulas wrote:
> One of my ISProviders is TWC. If you don't use DHCPv6, what you
> end up is the link-local address for each interface (which you get
> anyway), and a default route to the link-local address of the TWC
> router (through RA's), which is not usefu
In article ,
Matt Thomas wrote:
>
>> On Apr 23, 2015, at 8:40 PM, Brett Lymn wrote:
>>
>> inet6 fe80::76d0:2bff:fe2b:89bc%wm0 prefixlen 64 scopeid 0x1
>
>That is a link local address is only good for communicating with other
>machines accesible from that interface.
>
>If you had ârealâ
In article <20150425215148.ga1...@internode.on.net>,
Brett Lymn wrote:
>On Fri, Apr 24, 2015 at 09:06:08AM +0100, Roy Marples wrote:
>>
>> DHCPv6 does not specify any default route or prefix.
>> On NetBSD, DHCPv6 is only started when a RA is received with either the
>> O or M flags set and even
On 2015-04-25 22:51, Brett Lymn wrote:
On Fri, Apr 24, 2015 at 09:06:08AM +0100, Roy Marples wrote:
DHCPv6 does not specify any default route or prefix.
On NetBSD, DHCPv6 is only started when a RA is received with either
the
O or M flags set and even then you need to use dhcpcd(8) to get this
On Fri, Apr 24, 2015 at 09:06:08AM +0100, Roy Marples wrote:
>
> DHCPv6 does not specify any default route or prefix.
> On NetBSD, DHCPv6 is only started when a RA is received with either the
> O or M flags set and even then you need to use dhcpcd(8) to get this
> working.
>
> Did your host recei
> On Apr 23, 2015, at 8:40 PM, Brett Lymn wrote:
>
> inet6 fe80::76d0:2bff:fe2b:89bc%wm0 prefixlen 64 scopeid 0x1
That is a link local address is only good for communicating with other
machines accesible from that interface.
If you had “real” IPv6 you’d see something other than fe80::
Am Freitag, 24. April 2015, 13:10:24 schrieben Sie:
> inet6 fe80::76d0:2bff:fe2b:89bc%wm0 prefixlen 64 scopeid 0x1
If you mean this "IPv6 address" - this is (by IPv6 spec) a "link local"
address - auto generated by "your operating system" byself (from the network
hardware / MAC). This mea
Hi Brett
On 24/04/2015 04:40, Brett Lymn wrote:
> I am clearly doing something wrong here. I have a machine with a wired
> ethernet connection that I have manually configured the ipv4 address
> for, it appears to have an ipv6 address:
>
> wm0: flags=8843 mtu 1500
> capabilities=7ff80
>
Folks,
I am clearly doing something wrong here. I have a machine with a wired
ethernet connection that I have manually configured the ipv4 address
for, it appears to have an ipv6 address:
wm0: flags=8843 mtu 1500
capabilities=7ff80
capabilities=7ff80
capabilities=7ff80
12 matches
Mail list logo
