07:41:47 ok, i tried changing the hostname in imgadm.conf to the dns64 ip6 for images.smartos.org, and it still fails 07:41:50 imgadm sources: error (SourcePing): unexpected ping error with "imgapi" image source "https://64:ff9b::439e:362a": Error: connect ENETUNREACH 07:42:10 however this works 07:42:13 # wget --no-check-certificate https://[64:ff9b::439e:362a]... (full message at ) 07:42:13 how? 07:43:47 it's like something in imgadm really wants to do ipv4 only. for no good reason. i looked a bit in the code but couldn't find anything obvious 08:11:51 gonzosysadm[m]: have you tried using /etc/hosts? 08:12:21 yup 08:12:22 no luck 08:15:45 if I point it to 127.0.0.1 I get ECONNREFUSED. makes sense. if I use the dns64 ip6 (see above), not only does it never try to connect at all (i'm snoop'ing the vlan interface), it fails immediately (with imgadm -v i can see the attempts) with ENETUNREACH 08:16:28 that doesn't seem right, it should try to connect. every other application in every other machine will gladly ingest the faked AAAA record 13:48:07 I have a Dell R710 and just added a QLogic QLE2562. It doesn't show in [sysinfo] or [smbios] so how can I confirm the OS sees it and how do I interact with it? My plan is to use it for networking with a Ubiquiti switch 24 (non-POE). 16:18:05 Orion7: if you look at prtconf -dD do you see anything there? 16:29:34 I looked but do not know what I'm looking for (/2562 /qle /fc). I did find output from [fcinfo hba-port]. Yay! I still don't know how to use it for networking... What web page has a how-to for that? 16:31:16 Ah, I did find /qlogic in that output... 16:35:42 And I see it in [cfgadm -al]. Still trying to figure out how to use it... 16:36:25 Despite knowing a bunch, fc is not something I've ever used. 17:00:59 That's fair. I am still poking around without success. Maybe someone can point me in the right direction. 19:08:25 can't seem to save (-w) a tcpdump pcap as root in a zone 19:08:33 any idea? says permission denied 19:26:42 Newer versions of tcpdump drop root after getting the interface, then write dumps as some user specifically for tcpdumps. 19:29:45 If the guest is running linux, you may be fighting with apparmor. 19:31:19 If you're naming the file something other than *.cap or *.pcap (possibly with a numeric appendage), you can run afoul of common apparmor rules. 19:32:11 funny story, .cap is in the debian distribution's apparmor file because of me. 19:41:51 this is in a smartos zone though 19:42:12 it drops to _tcpdump, but i tried to -w to a 777'd directory, and even then no dice