The ISP will only route packets to the dom0 mac address; they are fully automated and will not accept custom requests. They don't even support solaris, I had to do the install using vmware to have solaris in native on this dedicated hosting.
DOM0_IP is a public IP and ipv4 forwarding is enabled. DOMU_IP is a public IP on the DOM0 side in my /etc/default/inetinit I have: route add -host DOMU_IP -iface DOM0_IP on the DOMU side I have route add -host DOM0_IP -iface DOMU_IP route add default DOM0_IP This works fine as a cheesy workaround but I don't like that the packets are sent twice to the same interface: DOMU_IP -> py-in-f99.google.com ICMP Echo request (ID: 8497 Sequence number: 3) DOMU_IP -> py-in-f99.google.com ICMP Echo request (ID: 8497 Sequence number: 3) py-in-f99.google.com -> DOMU_IP ICMP Echo reply (ID: 8497 Sequence number: 3) py-in-f99.google.com -> DOMU_IP ICMP Echo reply (ID: 8497 Sequence number: 3) Is there a way to tell DOM0 to route the packets to the vnic interface instead of pushing the packet back on the public interface? I am using Xen Drop b66 from July. I read somewhere that some more changes have been imported from the crossbow project in the xen putback to b75 which should be released today. This message posted from opensolaris.org
