ok, i tried changing the hostname in imgadm.conf to the dns64 ip6 for images.smartos.org, and it still fails

imgadm sources: error (SourcePing): unexpected ping error with "imgapi" image source "64:ff9b::439e:362a": Error: connect ENETUNREACH

however this works

# wget --no-check-certificate [64:ff9b::439e:362a]... (full message at <libera.ems.host/_matrix/media/v3/do…cd0001fe3146f24b31c4c6a9bca3db63e6d>)

how?

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

gonzosysadm[m]: have you tried using /etc/hosts?

yup

no luck

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

that doesn't seem right, it should try to connect. every other application in every other machine will gladly ingest the faked AAAA record

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).

Orion7: if you look at prtconf -dD do you see anything there?

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?

Ah, I did find /qlogic in that output...

And I see it in [cfgadm -al]. Still trying to figure out how to use it...

Despite knowing a bunch, fc is not something I've ever used.

That's fair. I am still poking around without success. Maybe someone can point me in the right direction.

can't seem to save (-w) a tcpdump pcap as root in a zone

any idea? says permission denied

Newer versions of tcpdump drop root after getting the interface, then write dumps as some user specifically for tcpdumps.

If the guest is running linux, you may be fighting with apparmor.

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.

funny story, .cap is in the debian distribution's apparmor file because of me.

this is in a smartos zone though

it drops to _tcpdump, but i tried to -w to a 777'd directory, and even then no dice