search for: ping6

> 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 wr...

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: icmp_seq=1 ttl=64 time=0.020 ms $ ping6 fd80:2015:2105:abcd::2 connect: Network is unreachable -- nodeB(fd80:2015:2105:abcd::2): $ ip -6 route fd80:2015:2105:abcd::2 dev...

Hi, I have a kvm host and I try to install a centos 6 guest with a static ip address. When I do a manual install I eventually get to the network configuration and if I enter IP, gateway and DNS Server I can ping6 the guest from the host and I can ping6 the guest from outside. I do not want to do manual installation, so I have to specify a url to a kickstart file, but to download it the network must be configured. I try some kernel options noipv4 ipv6=... gateway=... dns=... ks=http? This gets me so far t...

...ing netlink to configued interface in linux. For IPv4 addresses i do not see any issue with this assignment. When i try to assign an IPv6 address, the address gets assigned successfully to the interface, but the Neighbour Solication request received for that address is not responded with and hence ping6 from a different machine doesn't work. When i take the same netlink code and run it in a sample program the address gets assigned and the Neighbour solicitation is responded with a advertisement and hence ping6 works. IP assigned by the program : 7000::15/32 IP on client machine from where pi...

...collisions:0 txqueuelen:1000 RX bytes:81093 (79.1 KiB) TX bytes:46507 (45.4 KiB) # ping 192.168.11.8 PING 192.168.11.8 (192.168.11.8) 56(84) bytes of data. 64 bytes from 192.168.11.8: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.11.8: icmp_seq=2 ttl=64 time=0.019 ms ? # ping6 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) 56 data bytes Thanks! -- ??????????????????????? ??????????? ????????? ?? ?? TEL: (052)709-7121 FAX: (052)709-7122 e-mail: komeyama at designet.co.jp URL: http://www.designet.co.jp ????????...

...so the hardware can take it. I've got an ipv6 tunnel through Hurricane Electric and at a shell prompt have done the following: ifconfig sit0 up ifconfig sit0 inet6 tunnel ::IPV4 Address ifconfig sit1 up ifconfig sit1 inet6 add IPV6 Address route -A inet6 add ::/0 dev sit1 Testing that with a ping6 works fine. I then want it to persist across reboots. So I added the following to /etc/sysconfig/network: NETWORKING_IPV6=yes IPV6_DEFAULTDEV=sit1 and I made /etc/sysconfig/network-scripts/ifcfg-sit1 DEVICE=sit1 BOOTPROTO=none ONBOOT=yes IPV6INIT=yes...

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 b...

...ontain `ifconfig $INTERFACE [...]` for both IPv4 and IPv6. > Hm, what if you use Device = /dev/tun0 instead? > > If this still doesn't work, then try to find out what happens with the > packets you are sending. Run tinc in the foreground (use the options > -d5 -D), and then run ping6 fd16:dcc0:f4cc:0:0:2:0:1 in another > terminal. Does tinc see the packets? Does it send them to B? If so, > the problem might be on B. If it doesn't get the packets, try tcpdump > on all the interfaces to see where those packets are going. Although I had checked my configuration by ru...

...tinmoen 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 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: icmp_seq=1 ttl=64 time=0.020 ms $ ping6 fd80:2015:2105:abcd::2 connect: Network is unreachable -- nodeB(fd80:2015:2105:abcd::2): $ ip -6 route fd80:2015:2105:abcd::2 dev...

> 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,...

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

...t;>> ip -6 nei >> I am using two different IPv6 addresses for the two different machines. >> I am unable to ping outside from the VM or connect otherwise via IPv6 >> from the VM. I am also unable to ping the link-local addresses of the >> eth1 interface on the VM (via `ping6 fe80::5054:aaff:fe00:f057/64`). >> ip -6 nei on the VM gives me: >> `fe80::5054:ff:fe1d:a4bb dev eth1 lladdr 52:54:00:1d:a4:bb router STALE` >> >> > Hi, > > Your setup shows > virbr2 and br0 both on the same network 2607:5300:60:1156::2/64 which > will cause...

...py of BIND in a local view and zone (tld is htt). Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back. But if I try to use the IPv6 address of the system I get a time out. Both from nslookup and from ping6. I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server). I have turned off both ip6tables and iptables so it is not a firewall issue. Even 'nslookup - <ipv6...

...hat does this command output look like ? > ip -6 nei I am using two different IPv6 addresses for the two different machines. I am unable to ping outside from the VM or connect otherwise via IPv6 from the VM. I am also unable to ping the link-local addresses of the eth1 interface on the VM (via `ping6 fe80::5054:aaff:fe00:f057/64`). ip -6 nei on the VM gives me: `fe80::5054:ff:fe1d:a4bb dev eth1 lladdr 52:54:00:1d:a4:bb router STALE` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (MingW32) iQIcBAEBAgAGBQJUMFUEAAoJEEhc1G8ZKSOxaigQAKAQ7oJ3kBtxjOGHoOb5K+1K Y09DL8RjiR20F752a9SNEVOXo+GaAAGXk...

...tkey.sh start Starting VPN tunnel encryption..Ok mohan# ******************* *******at Host2******* ram# /usr/local/etc/rc.d/setkey.sh start Starting VPN tunnel encryption..Ok ram# ******************* (File setkey.sh is also attached with the email below for ur reference) After that I executed 'ping6' and 'tcpdump' commands to test the ipsec connection(on my system i.e.,host1-mohan), but it seems, it is not working properly... ########### ping6 command output at host1############ mohan# ping6 -I xl0 fe80::2b0:d0ff:fe48:7ce7 PING6(56=40+8+8 bytes) fe80::2b0:d0ff:fe6f:dfa0%xl0 -->...

...tkey.sh start Starting VPN tunnel encryption..Ok mohan# ******************* *******at Host2******* ram# /usr/local/etc/rc.d/setkey.sh start Starting VPN tunnel encryption..Ok ram# ******************* (File setkey.sh is also attached with the email below for ur reference) After that I executed 'ping6' and 'tcpdump' commands to test the connection(on my system i.e.,host1-mohan), but, it seems is not working properly... ########### ping6 command output at host1 ############ mohan# ping6 -I xl0 fe80::2b0:d0ff:fe48:7ce7 PING6(56=40+8+8 bytes) fe80::2b0:d0ff:fe6f:dfa0%xl0 --> fe80::2...

...FAULTDEV=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0 ONBOOT=yes DEVICE=eth0 BOOTPROTO=static HWADDR=52:54:00:68:42:1E IPADDR=000.111.222.333 NETMASK=255.255.255.128 IPV6INIT=yes IPV6ADDR=2a02:aaaa.bbbb:178:209:50:230:0/112 Attempts to use the IPv6 address fail. For example: # ping6 -c 2 2a00:1450:4016:800::1013 connect: Network is unreachable However it works if I manually enter these 2 lines: # route -A inet6 add ::/0 dev eth0 # ip -6 route add 2000::/3 via 2a02:aaaa.bbbb::1 metric 1 # ping6 -c 2 2a00:1450:4016:800::1013 PING 2a00:1450:4016:800::1013(2a00:1450:4016:8...

...39;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 it's gateway why can only the router do ping6 2001:db8:0815::17 and not the linux box? is there a missing IPv6 route? Thanks, Walter

...ric:1 RX packets:1862 errors:0 dropped:0 overruns:0 frame:0 TX packets:266 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:136703 (133.4 KiB) TX bytes:33944 (33.1 KiB) ipv6 is working locally: <centos666.peak.org> [29] # ping6 2607:f678::16:66 PING 2607:f678::16:66(2607:f678::16:66) 56 data bytes 64 bytes from 2607:f678::16:66: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 2607:f678::16:66: icmp_seq=2 ttl=64 time=0.038 ms ^C --- 2607:f678::16:66 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time...

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 [3ffe:1200:3028:ff01::caa] ListenAddress [3ffe:1200:3028:8655::1] [Note: I also tried using t...