0

On Solaris10 (vm on qemu) I configure ipv6

ipsec and firewall are disabled

svcs -a|gegrep 'ipfilter|ipsec' disabled 1:00:14 svc:/network/ipfilter:default disabled 23:38:28 svc:/network/ipsec/manual-key:default disabled 1:00:18 svc:/network/ipsec/policy:default disabled 1:00:18 svc:/network/ipsec/ike:default 

ipv6 is configured

ifconfig -a6 e1000g1: flags=2104841<UP,RUNNING,MULTICAST,DHCP,ROUTER,IPv6> mtu 1500 index 3 inet6 fe80::5254:ee:fdc7:a479/10 e1000g1:1: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 3 inet6 418:5b17:d32a:8023::2/64 

but cannot ping the "external" switch (is a virbr created from libvirt), can ping only his own address

ping -A inet6 -s 418:5b17:d32a:8023::2 PING 418:5b17:d32a:8023::2: 56 data bytes 64 bytes from 418:5b17:d32a:8023::2: icmp_seq=0. time=0.0300 ms 64 bytes from 418:5b17:d32a:8023::2: icmp_seq=1. time=0.0400 m ping -A inet6 -s 418:5b17:d32a:8023::1 PING 418:5b17:d32a:8023::1: 56 data bytes 

route seems correct

netstat -rn Routing Table: IPv6 Destination/Mask Gateway Flags Ref Use If --------------------------- --------------------------- ----- --- ------- ----- 418:5b17:d32a:8023::/64 418:5b17:d32a:8023::2 U 1 98 e1000g1:1 fe80::/10 fe80::5254:ee:fdc7:a479 U 1 69 e1000g1 

Another machine (Slackware Linux) connected to the same virtual switch can ping without problem

ping -6 fe80::5254:ee:fdc7:a481 PING fe80::5254:ee:fdc7:a481(fe80::5254:ee:fdc7:a481) 56 data bytes 64 bytes from fe80::5254:ee:fdc7:a481%eth0: icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from fe80::5254:ee:fdc7:a481%eth0: icmp_seq=2 ttl=64 time=0.028 ms 64 bytes from fe80::5254:ee:fdc7:a481%eth0: icmp_seq=3 ttl=64 time=0.028 ms 

why Solaris network remain isolated?

Routeadm report

routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing enabled enabled IPv6 routing enabled enabled IPv4 forwarding enabled enabled IPv6 forwarding enabled enabled 

From an external machine I can ping Linux vm but not Solaris vm.

1 Answer 1

0

Solution found: was a buggy driver/configuration. In the previous configuration I had 4 nics (all e1000g0), I have change the driver of the 4th (which was not in use), to rtl8139. I reboot and..

root@solaris10:~# ping 418:5b17:d32a:8023::1 418:5b17:d32a:8023::1 is alive root@solaris10:~# ping 418:5b17:d32a:8023::2 418:5b17:d32a:8023::2 is alive root@solaris10:~# ping 418:5b17:d32a:8023::3 418:5b17:d32a:8023::3 is alive 

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.