And I can't figure out how to get the external interface to be pingable. It's either the IP that gets auto-discovered by these tools is somehow wrong, or the router is configured not to respond to ping (most likely), or maybe even ICMP is blocked higher up the chain (I know salt uses carrier grade NAT). But seems like it should be possible given that the router GUI lets you configure port forwarding, DMZ, all the usual stuff..
By the way, the default router user/pass is admin/admin.
Things I tried:
1. Under "Network > Intrusion Detection," uncheck "Discard Ping To WAN Interface" and save settings.
2. Under "Network > Firewall," set "Firewall features" to "Off," save settings.
3. (1) and (2) simultaneously.
Not sure what else to try.
Actually if you go to "Administration > Network Tools" and run a traceroute to anywhere, and take the first non-local IP, this turns out to be pingable. But I confirmed this is not my end device by powering off my router and seeing that the IP still responded to pings from my mobile phone on cellular data connection.
Works fine for me. Firewall set to "Low", both boxes in "Intrusion Detection" are unchecked (discard ping from WAN and another one).
Are you perhaps using a web proxy? Do you have a public (routable) IPv4 address assigned to the box (there was talk about Salt switching to private / non-routable IPv4)?
Ah, that's it. This is pretty clear from the router GUI because it is showing a 10.*.*.* address for IPv4, but somehow I thought maybe we still had our own external IPv4 that it wasn't showing for some reason. But yeah, looks like you don't get it by default and have to pay extra:
IPv6 is no problem but I can't find a line monitor test like on dslreports that works with IPv6.
I sometimes get very long "Resolving host..." or "Waiting for response from..." times with this connection. Maybe seems more common at periods of high internet usage (evenings etc). This on the salt DNS as well as after switching to google or opendns. So I don't know what's up. I just thought I'd run a bunch of tests and see if anything was revealed. Kinda wishing at this point that I had just gone with init7.
Would be nice if I could check firmware version but I don't see anything this detailed... I guess for firmware updates salt just manages it completely on their own, pushing an overall update to the "salt box" at some point, which may include firmware upgrades for individual components?
Interesting - looks like I have a different box (hardware version is a R01A). Out of curiosity, if you try to backup your settings (Expert mode - Administration - Restore/Save/Upload Setting - click on Backup fiber box), what is the resulting file name (the one you get prompted to download)? Mine is ArcadyanV1_backup.cfg and I know at least on the initial release (such as mine), the internals were made by Arcadyan (see also the 'Conformity' section on https://fiber.salt.ch/sites/default/...anual-en-1.pdf )
You can find out the assigned IP address if you go to the Overview tab and then click on "Detail" under Internet.
The error you are referring to could be a temporary DNS failure or misconfiguration on your PC (e.g. if the first configured DNS server is slow or down, it will take some time for the request to time out until it gets to the next one). Try configuring 1.1.1.1 as your only DNS server (on the PC) and see if it works.
The updates are indeed pushed to the box and are activated on a reboot. I am hesitating to update mine, as I don't want to be stuck with IPv6.
I think I was just making an assumption that this online test detected the hardware somehow; on second thought that doesn't make sense. I also get "arcadyanV1_backup.cfg" (lowercase but otherwise the same as what you wrote). And in the user manual Jpeg that is stored directly on the device (in the router GUI under Administration > User Manual), it has the same 'Conformity' section.
I popped open the cfg in a hex editor to look for human readable version strings but I see nothing. It almost looks like base64 encoded, but I can't quite figure it out.
These brave souls disassembled a salt box and found Arcadyan also. The page is down at the moment but maybe will come back:
Problem is it has been pretty intermittent, and possibly correlated to high-traffic times, but it hasn't been long enough to where I can say confidently.
I didn't know about 1.1.1.1, I will give them a try. In fact this made me realize something else-- I changed my IPv4 DNS to google/openDNS, but didn't even think to change the configuration for IPv6. I've now set all primary/secondary for IPv4/6 to the ones they specify at https://1.1.1.1/dns/ so we'll see how it goes. I've also installed this chrome extension https://github.com/pmarks-net/ipvfoo so I can get a feel for 4 vs 6... It could be that what I thought was "intermittent" was actually the Salt DNS being down or in a bad state, which was only manifesting on sites where IPv6 was happening. I could probably find a way to test this hypothesis thoroughly but I think I will just see how things go for a while.
I assumed they grandfathered you in. But knowing Salt I guess they wouldn't do that (their market mostly seems to be people who would have no clue of the change). If this goes well I'll be fine with Salt at least for the duration of my contract, but still would think of switching to Init7 just to get something that feels more like a proper setup.
Thanks, I'll try using only IPv6 for a few days and see if it makes a difference. Haven't looked into replacing the box yet, I didn't suspect that to be the culprit.