It seems to just hang there. The RGB LED is stuck in fast blinking green at this point - so far it doesn't change anywhere in the process.
I just reset the Argon wifi again (long press on mode till blue flashing), and set up the network fresh:
0000006306 [ncp.at] TRACE: > AT
0000006307 [ncp.at] TRACE: < OK
0000007308 [hal] TRACE: NCP ready to accept AT commands
0000007309 [ncp.at] TRACE: > AT+CMUX=0
0000007311 [ncp.at] TRACE: < OK
0000007312 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000007313 [gsm0710muxer] INFO: Openning mux channel 0
0000007313 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000007365 [gsm0710muxer] INFO: Resuming channel 0
0000007367 [gsm0710muxer] INFO: Openning mux channel 1
0000007467 [gsm0710muxer] INFO: Resuming channel 1
0000007468 [gsm0710muxer] INFO: Resuming channel 1
0000007471 [ncp.at] TRACE: > AT
0000007521 [ncp.at] TRACE: < OK
0000007522 [ncp.at] TRACE: > AT+CWDHCP=0,3
0000007571 [ncp.at] TRACE: < OK
0000007572 [hal] TRACE: NCP state changed: 1
0000007574 [net.esp32ncp] TRACE: NCP event 1
0000007576 [ncp.at] TRACE: > AT+CWLAP
0000010130 [ncp.at] TRACE: < +CWLAP:(3,"APName",-54,"APMAC",6)
SSID=APName security=wpa2 channel=6 rssi=-54
//other APs
0000010170 [ncp.at] TRACE: < OK
connecting to WiFi
0000010179 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000010183 [net.ifapi] INFO: Netif wl3 state UP
0000010185 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000010192 [gsm0710muxer] INFO: Openning mux channel 2
0000010275 [gsm0710muxer] INFO: Resuming channel 2
0000010277 [hal] TRACE: Connecting to "APName"
0000012177 [ncp.at] TRACE: < WIFI CONNECTED
0000013127 [ncp.at] TRACE: < OK
0000013128 [hal] TRACE: NCP connection state changed: 2
0000013128 [net.esp32ncp] TRACE: NCP event 2
0000013129 [net.esp32ncp] TRACE: State changed event: 2
0000013131 [net.ifapi] INFO: Netif wl3 link UP
0000013132 [system.nm] INFO: State changed: IFACE_UP -> IFACE_LINK_UP
0000013134 [ncp.at] TRACE: > AT+CWJAP?
0000013178 [ncp.at] TRACE: < +CWJAP:"APName","APMAC",6,-52
0000013179 [ncp.at] TRACE: < OK
0000013210 [ncp.mgr] TRACE: Updated file: /sys/wifi_config.bin
Outside of the extra AT+CWJAP and the config file, it doesn't get any further.
From looking at other people's logs, it seems like IP assignment would typically come next. Something like:
[system.nm] INFO: State changed: IFACE_LINK_UP -> IP_CONFIGURED
Our IT department is asking if I can disable IPv6, or force an IPv4 address on my end, though I'm not sure if that's something I can do. I know that the Argon has successfully leased an IPv4 address in the past on this network, but it may not be doing so now.
I've seen that this thread back in November showed logs failing at the same spot, and @ScruffR commented that:
That’s what I get when my DHCP server tries to assign an IPv6 to the Argon (or merely checks whether IPv6 is supported on the device?).
Currently my workaround is to add an intermediate WiFi router where I can disable IPv6 support entirely.
Hopefully 0.8.0-rc.26 will address this issue.
That thread ends with an announcement that v080-rc.26 was supposed to take care of some of the IPv6 issues. I'm running v1.2.1, so I'm not sure if there are remaining issues with IPv6. Our IT department has told me that the network is "dual stack IPv4/IPv6", so I don't think I have the option to disable IPv6 on their end.
Has anyone run into this recently? Any strategies for getting past it that don't involve adding a new router in the middle? Thanks for your help!