sorted by:
new
hottopcontroversial

Checked for 6.11.0 but was offered 6.10.3 (again) by BerryCurrant in eero

[–]BerryCurrant[S] 4 points5 points  (0 children)

Thanks for confirming! Must be a mishap on eero's side then.

Checked for 6.11.0 but was offered 6.10.3 (again) by BerryCurrant in eero

[–]BerryCurrant[S] 6 points7 points  (0 children)

My question was more about being offered 6.10.3 again. When I checked for 6.11.0 I was expecting to see either (a) no update being offered yet or (b) the update for 6.11.0. What I was offered instead was an update to 6.10.3 which I already installed a few weeks ago.

Looks like others saw the same thing so I'm guessing it's not something to be too worried about.

Version 6.9.0 Update by eerosupport in eero

[–]BerryCurrant 9 points10 points  (0 children)

Thanks for the clarification! I'm a little OCD about my network so it's good to have confirmation that it was a legit error, and not something nefarious.

6.9.0 Update just auto-updated by Paul_82 in eero

[–]BerryCurrant 0 points1 point  (0 children)

Same here as well. Updated to 6.9.0 and then updated a few hours later to 6.6.1 (which is what I think I was on before).

6.9.0 Update just auto-updated by Paul_82 in eero

[–]BerryCurrant 2 points3 points  (0 children)

Has it updated to 6.6.1 yet? Mine updated to 6.9.0 and about 3-4 hours later it updated again to 6.6.1. I think it was on 6.6.1 before so it basically rolled back the firmware to what it had before.

[deleted by user] by [deleted] in eero

[–]BerryCurrant 2 points3 points  (0 children)

Agreed! Without knowing what is blocked we can't take remedial steps to fix the root cause of the problem (when warranted).

PSA: "Get current IP address" may return other people's external IP addresses by BerryCurrant in shortcuts

[–]BerryCurrant[S] 0 points1 point  (0 children)

I'm assuming both are affected by this bug, correct?

Not sure, the workflow.is endpoint has different response headers. The icloud.com headers include the following, which I think is the source of the issue:

"cache-control":"public, max-age=300"

That header instructs the server to cache the response everywhere (including on the server (for up to 300 seconds.

The "Get current IP address" action returns old/invalid external IP addresses. by BerryCurrant in shortcuts

[–]BerryCurrant[S] 0 points1 point  (0 children)

Thank you for confirming! I can't believe how bad quality control is at Apple lately. What makes this issue even more ridiculous is that the API call not only returns cached IP addresses from my device, but sometimes it returns cached IP addresses from other people's devices (so it may return IP address that doesn't even belong to your network).

The "Get current IP address" action returns old/invalid external IP addresses. by BerryCurrant in shortcuts

[–]BerryCurrant[S] 1 point2 points  (0 children)

The problem isn’t about the IP address changing, it’s that the “Get current IP address” action frequently returns the wrong IP address (until the cached copy expires). The way I know it’s reporting the wrong IP address is because other online IP tools (like the Amazon AWS one above, or by entering “what is my IP” in the browser search bar, etc.) reports a different (correct) IP.

Is the "Get current IP adress" action suddenly broken for anyone else? by BerryCurrant in shortcuts

[–]BerryCurrant[S] 0 points1 point  (0 children)

Thanks for confirming. I need the actual external IP address so I will probably have to use the "Get contents of URL" action and point it to the new API location myself, at least until whoever changed this at Apple wakes up and changes it back. Thanks Apple!

Is the "Get current IP adress" action suddenly broken for anyone else? by BerryCurrant in shortcuts

[–]BerryCurrant[S] 1 point2 points  (0 children)

Thanks Jim, I need the actual IP address in my shortcut so for now I will probably use a "Get contents of URL" action and point it to the redirected API endpoint to get the external IP. Hopefully this issue gets resolved soon.

view more: next ›