|
[You should check your firewall/ip6tables rules. That should just work -- assuming, of course, that the two devices are connected directly] When pinging a link-local ipv6 address, you could also include the link specification via the %-syntax: ping6 fe80::dfef:2fb9:b91c:89a0%l_br0 PING fe80::dfef:2fb9:b91c:89a0%l_br0(fe80::dfef:2fb9:b91c:89a0%l_br0) 56 data bytes 64 bytes from fe80::dfef:2fb9:b91c:89a0%l_br0: icmp_seq=1 ttl=64 time=0.615 ms ...(notice the ...%l_br0; l_br0 is the name of my bridge; you'll have to use ...%enp0s31f6 or ...%eth2 with your addresses). When using netcat, etc you'll have to use the % syntax as they have no way to specify the interface as ping6 has via -I. Example, on a machine listen with: nc -l fe80::dfef:2fb9:b91c:89a0%em0 8888And connect from the other with: nc fe80::dfef:2fb9:b91c:89a0%l_br0 8888(the first machine with the em0 interface is running OpenBSD; the second with the l_br0 interface is running Linux). (责任编辑：) |