So my NAS got ipV6 address, however after 1-2 hours the ipv6 address disapears. Restarting the ndp service restores the ipv6 adress: i.kek.sh/7uN27YLGMC0.png But then it disappears again. What have I missed during the setup, how can I set up the NAS to keep the IPV6 adress? I am using SLAAC here.

root@omnios:~# cat /etc/inet/ndpd.conf

ifdefault StatelessAddrConf on

ifdefault StatefulAddrConf off

ifdefault TmpAddrsEnabled true

ifdefault TmpPreferredLifetime 600

ifdefault TmpValidLifetime 600

Might be rhe tmpaddrsenabled

I had this before I have added the tmpaddr too.

root@omnios:~# cat /etc/hostname6.e1000g0

token ::10/64

I also have this.

I didn't had IPV6 connectivvity during the install, so maybe I missed some important setting / file / service.

nas is omnios?

yes

does ipadm show address objects for v6?

have you see nthe screenshot I posted? Does that contain the info you was asking for?

like: vioif0/v6 addrconf ok fe80::8:20ff:fe4d:a12a%vioif0/10

I have censored it because it is a global ipv6 adress

ok, objects are there.

this is physical host with direct connection or vm?

this is a physical host

essentially, if your setup is using stateless addrconf, then the router is supposed to send periodically out prefix announcements, if those announcements stop, then the prefix will expire and the address is dropped from interface. With dhcpv6, you get stateful config and address (with prefix) is coming from dhcp server and lease lifetime settings apply.

But as I have mentioned, restarting the service makes the ipv6 address show up immediately. So I think the router announces the prefix just fine, just omnios ignores it and lets the address expire.

in case of stateless setup, it is possible your ISP is not sending prefix announcements (then the prefix will expire in your router and it will stop announcements in your lan), or your router is buggy.

you should be able to monitor the announcements with snoop/tcpdump/tshark

I had similar issue with my netgear orbi, and at some point in time it got "fixed", I'm not even sure if the cause was at ISP or in my router...

I understand, but none of the other clients have any issue with the router. So I suspect the issue is in omnios or in its config.

I have created the ndpd.conf and the ipv6 address did not dissapeared in the last 30 min. I will monitor it further and hope it will work now.

oh, rhight, ndpd has option to switch on the debug printout

the ndpd log shows me the following:

Mar 16 13:10:37 /etc/inet/ndpd.conf line 6: TmpDesyncFactor (600) is greater than TmpPreferredLifetime (120)

Mar 16 13:10:37 /etc/inet/ndpd.conf line 7: TmpPreferredLifetime (86400) is greater than TmpValidLifetime (120)

86400 is 24h. I suspect omniOS simply lets the address expire. So i have reordered the entries in the ndpd.conf like this:

ifdefault TmpPreferredLifetime 600

ifdefault TmpValidLifetime 600

since then no warning. MAybe the default 86400 sec alue is simply too long.

but this config options are for the temp addresses, so it should not impact the global ipv6 address.

yep.

no idea then :S

well, you can run in.ndpd -d (or -D XXX where XXX is value you can find from source), this will stop turning into daemon, so you need to disable smf service and start it manually

-d does enable full debug, so it will spam some...

but my symptoms were quite similar -- phones and macos had ipv6, illumos got them expired

I was already suspecting if its related to missing ND_OPT_ROUTE_INFO feature, but then it was "magically" fixed:D

ipv6 adress just disapeared.

Lets try with the -d

strange, but I can1t sem to find the in.ndpd executable, it is not in $PATH

/usr/lib/inet/in.ndpd

yep

I have disabled the tmpddrs to reduce the noise and got his: paste.omnios.org/?259a1b79231d6983#…tM7kmbZkQrdU6aGV7XbZPBt3zRG42hmrrBr

The router is running up-to-date openwrt.

you can trace only prefix with ndpd -D 0x0008, constants are in src.illumos.org/source/xref/illumos…/defs.h?r=176dc728&mo=2271&fi=90#86

It says: "Address removed due to timeout "

whole log: paste.omnios.org/?bda5cff789176b29#…QyMKUYiFhvr5UJVMP5qRyXr5yCBKStCvNYk

I have buped the "IPv6 Valid Prefix Lifetime" and "IPv6 Preferred Prefix Lifetime" to 10 years.

szilard: router should be periodically multicasting a prefix advertisement to ff02::1 ; if ndpd doesn't see the advertisement it will time out the prefix and the address will go away.

And... second time my box has just randomly hung, then self rebooted with no crashdump or other clue as to why. First on 151054ad, this time on 151054am. 'feels' like a storage IO hang as it'll ping but not complete an ssh attempt before it reboots?

Of course it's remote so no idea what was on screen when it tanked.

Sometimes I miss the old hard-copy console.

Yeah.... would be so nice right about now.

Save for the hour drive to get to it...

RS-232 console server with log ....

smartctl looks healthy across the board

nvme slogs show healthy

Ok, illumos.org/issues/8391 matches up pretty well to what I've observed, short of seeing the console output.

→ BUG 8391: mr_sas controller lockup on Dell H330 (New)

illumos.topicbox.com/groups/developer/Td11518c45ba141cc as well

if you can, replace it with a HBA330

Or, toss it given the mandate is no more local anything... blech. This will be a fun chat tomorrow.

Can I convince work to spend $65 to fix it short term so I'm not down storage while migrating to AWS?

i paid something like $25 for my hba330 :)

The trick is convincing for ANY spend on HW is now stupid difficult.

Kurlon: is the hardware otherwise good? convince them to let you take it for $homelab.

R640 with 512GB RAM, I suspect they're going to try and sell it despite it being EOL, but I'm hoping otherwise. :D

EOL doesn't mean it can't be resold... just not for as much $$$.

It's OK for it's age, loud as heck and not exactly skimping on power draw for homelab use.

so.. classic :)

Other than this problem, it's been rock solid for the 7, 8? years we've had them.

Take the HW, find a matching generation bare workstation to transpose the ram / cpu(s) into, add big ol video card... battle station status: Excellent

If the lights in the block don't dim when you hit power, it's not big enough.