similar to: what wrong about my ipv6 address

Hello I've got two prefixes, one /48 and one /64 let's say these two 2001:db8:0815::/48 2001:db8:4711:cafe::/64 the router has on it's ethernet interface the following to IPv6 addresses: 2001:db8:0815::1/48 2001:db8:4711:cafe::1/64 a windows box has 2001:db8:0815::17/48 and 2001:db8:0815::1 as it's gateway a linux box has 2001:db8:4711:cafe::11/64 and 2001:db8:4711:cafe::1 as

On 10/5/2014 1:56 AM, Bhasker C V wrote: > On 04/10/14 21:13, The Cop wrote: >> On 10/4/2014 8:46 PM, Bhasker C V wrote: >>> On 04/10/14 15:36, The Cop wrote: >>>> Hello, >>>> >>>> I am trying to assign an IPv6 address to one of my guests. I followed the >>>> following guide, unsuccessfully: >>>> >>

> Try > > ping6 -I eth1 2000:8000:12:6:192:168:11:8 Thanks for the response. I tried. However, It did not resolve.... # ping6 -I eth1 2000:8000:12:6:192:168:11:8 PING 2000:8000:12:6:192:168:11:8(2000:8000:12:6:192:168:11:8) from fe80::a00:27ff:fe03:5b8a eth1: 56 data bytes On 2015/11/13 2:22, Paul Heinlein wrote: > On Thu, 12 Nov 2015, ???? wrote: > >> Hello >>

I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024 fe80::/64 dev eth0 proto kernel metric 256 $ ping6 fd80:2015:2105:abcd::1 PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes 64 bytes from fd80:2015:2105:abcd::1:

Hello Because I did not send , and then retransmitted. I am using the CentOS5.7. In a state where the link down, I did a ping to the IPv4 and IPv6. IPv4 succeeds in ping. but, IPv6 is ping fails. Once confirmed by ifconfig, it did not have a Link-Local Address. At link down, Is the Link-Local Address not set? Leave the link down, Is there a way to avoid this? # ethtool eth1 Settings for eth1: ?

I can't get IPv6 routing to configure correctly despite everything I've read saying it should This is my network config on a fully-updated CentOS 5.8 system: # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=my.hostname.com GATEWAY=aaa.bbb.ccc.ddd IPV6_DEFAULTGW=2a02:aaaa.bbbb::1 IPV6_DEFAULTDEV=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0

* sorry for the other schema, it came out a mess. I hope this one is understandable. hi: I have this 2 boxes set up like this: 2020::2/128 2020::254/128 3030::254/128 192.168.0.2/24 192.168.0.254/24 192.168.30.254/24 +-------+ eth0 eth3 +-------+

I'm completely confused here and I'm hoping someone here has a setup they're willing to share, or help me configure things on my end. My connectivity is through Comcast, who unfortunately, does not offer ipv6 in my area. My connection goes like this: Comcast -> Motorola Surfboard Cable Router -> CentOS 6.5 server The CentOS server is multi-homed and manages the internal

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/4/2014 8:46 PM, Bhasker C V wrote: > On 04/10/14 15:36, The Cop wrote: >> Hello, >> >> I am trying to assign an IPv6 address to one of my guests. I followed the >> following guide, unsuccessfully: >> https://www.berrange.com/posts/2011/06/16/providing-ipv6-connectivity-to-virtual-guests-with-libvirt-and-kvm/

Hello, I am having a some problems getting SSHD to run on the Ipv6 interface. Interface/Ipv6 Address: ipv6.open-systems.org [kevin at satan kevin/xp-0.0.15] 536 $ping6 ipv6.open-systems.org PING6(56=40+8+8 bytes) 3ffe:1200:3028:ff01::cab --> 3ffe:1200:3028:ff01::caa 16 bytes from 3ffe:1200:3028:ff01::caa, icmp_seq=0 hlim=64 time=73.96 ms sshd_config: ListenAddress

hello, the topology is like this: centos v0:eth1 <------> centos v0: eth2 fc00:2:3:4::1 fc00:2:3::4 i turned the packet forwarding ping6 -i eth2 fc00:2:3:4::1 the output is PING fc00:2:3:4::1(fc00:2:3:4::1) from fc00:2:3::5 eth2: 56 data bytes >From fc00:2:3::4 icmp_seq=1 Destination unreachable: Administratively prohibited >From fc00:2:3::4 icmp_seq=2

> First off, I assume you can ping your link-local address: > > ping6 -I eth1 fe80::a00:27ff:fe03:5b8a > > Second, you never mentioned how eth1 was assigned its IPv6 address. > Given that you've tried to embed an IPv4 address within an IPv6 address > (which is normally done with a 0:0:0:0:0: prefix), I'd guess you did it > manually. If so, with what tools?

We've been running ipv6 for a year or so now, but some of our newer instances (all on an ESX cluster) are not working. It looks like it's all of our Centos 6 instances. I'm hoping someone can point me in the right direction... tshark indicates that it's neighbor discovery that's failing: <centos666.peak.org> [26] # cat ../network NETWORKING=yes

On 04/10/14 21:13, The Cop wrote: > > On 10/4/2014 8:46 PM, Bhasker C V wrote: >> On 04/10/14 15:36, The Cop wrote: >>> Hello, >>> >>> I am trying to assign an IPv6 address to one of my guests. I followed the >>> following guide, unsuccessfully: >>> >

On Fri, 13 Nov 2015, ???? wrote: >> Try >> >> ping6 -I eth1 2000:8000:12:6:192:168:11:8 > > Thanks for the response. > > I tried. > However, It did not resolve.... > > # ping6 -I eth1 2000:8000:12:6:192:168:11:8 > PING 2000:8000:12:6:192:168:11:8(2000:8000:12:6:192:168:11:8) from > fe80::a00:27ff:fe03:5b8a eth1: 56 data bytes First off, I assume

You have a typo in your routes: fd80:2015:2105:adcd::/6 abcd vs. adcd On 21 May 2015, at 19:35, Martin <martinmoen at gmail.com<mailto:martinmoen at gmail.com>> wrote: I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024

https://bugzilla.mindrot.org/show_bug.cgi?id=3161 Bug ID: 3161 Summary: ssh -J <public IPv6> <LL IPv6%scopeID> doesn't work as expected Product: Portable OpenSSH Version: 8.2p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5

I've been trying out IPv6 networking with tinc and noticed that it will not route smaller segments than /48 If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get network unreachable However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine Is this is a limitation in tinc or the kernel network stack itself? -------------- next part -------------- An HTML

Em 10-09-2018 10:43, Rowland Penny via samba escreveu: > On Mon, 10 Sep 2018 09:56:46 -0400 > spiderslack via samba <samba at lists.samba.org> wrote: > >> Hi, all >> >> >> I trying setting domain samba with bind9-DLZ. I followed the tutorial >> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, >> but not

On Thu, 12 Nov 2015, ???? wrote: > Hello > > Because I did not send , and then retransmitted. > > I am using the CentOS5.7. > In a state where the link down, I did a ping to the IPv4 and IPv6. > IPv4 succeeds in ping. but, IPv6 is ping fails. > Once confirmed by ifconfig, it did not have a Link-Local Address. > At link down, Is the Link-Local Address not set? > Leave