Hello, May I suggest using your gateway as your primary resolver, works for me.
Good luck On Mon, Mar 24, 2014 at 7:00 AM, Evan Rowley <[email protected]> wrote: > The global zone networking seems fine. It was able to download the > Joyent-published image without a problem. I also have no issues relating to > it. > > 8.8.8.8 pings OK from the global zone, but it is still inaccessible from > the KVM guest. The same goes for my ISP's gateway. > > I have a HP NC360T, which is definitely a supported NIC, as the global > zone's standard admin interface. There is also a quad port Intel I354 NIC > on the same host, but there is no driver yet for SmartOS. The thing just > straight up isn't even visible on dladm show-phys. But that I354 shouldn't > have anything to do with thus current networking issue. > > Once I get to my office desk I'll try the nictagadm. Hopefully it has some > clues as to what is misconfigured. > > Thanks everyone for helping me so far. > On Mar 23, 2014 10:57 PM, "Ian Collins" <[email protected]> wrote: > >> Evan Rowley wrote: >> >>> root@ubuntuguest:~# ifconfig eth0 >>> eth0 Link encap:Ethernet HWaddr f2:62:bb:ac:0d:9b >>> inet addr: XXX.XXX.137.205 Bcast: XXX.XXX.143.255 >>> Mask: 255.255.248.0 >>> inet6 addr: fe80:f062:bbff:feac:db9/64 Scope: Link >>> UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1 >>> RX packets:43590 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:2128 errors:0 dropped:0 overruns:0 carrier:0 >>> collision: 0 txqueuelen:1000 >>> RX bytes:5312194 (5.3 MB) TX bytes: 176399 (176.3 KB) >>> >> >> So it is picking up the networking information you configured in your >> JSON payload. >> >> UPDATE:: I am able to ping the global zone's admin IP address: >>> XXX.XXX.136.64. - I still cannot reach websites on the internet or >>> even the ISP's gateway.The correct gateway IP does still show up in >>> the KVM guest's routing table produced by netstat -r. >>> >> >> Does networking work as expected from the global zone? >> >> I wonder if there is a packet forwarding sysctl, like there is in >>> FreeBSD/OpenBSD, that needs to be set on the SmartOS global zone. I'm >>> not very knowledgeable when it comes to Solaris, so sysctls might be a >>> completely foreign concept in this arena. >>> >> >> You shouldn't have to do anything - just double check with "nictagadm >> list" that your admin nictag is assigned to the correct physical NIC. >> >> -- >> Ian. >> >> >> >> ------------------------------------------- >> smartos-discuss >> Archives: https://www.listbox.com/member/archive/184463/=now >> RSS Feed: https://www.listbox.com/member/archive/rss/184463/ >> 24484565-d47e1b4e >> Modify Your Subscription: https://www.listbox.com/member/?&id_ >> secret=24484565-431e4e0b <https://www.listbox.com/member/?&;> >> >> Powered by Listbox: http://www.listbox.com >> > *smartos-discuss* | > Archives<https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/24697919-04ed9bf0> | > Modify<https://www.listbox.com/member/?&;>Your Subscription > <http://www.listbox.com> > > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
