IPFS Cycles Network Printer Power [was Update Brave Nightly Cycles Network Printer Power]

@Mattches, as a test, I downloaded the IPFS Desktop application version 0.17.0 and launched it, and it also resets the printer in macOS and Windows 10. So there’s little doubt it’s IPFS, at least in my mind.

Submitted ticket with IPFS project:

2 Likes

Still occurs on 1.33.57 Mac/Win:

Date: 03 November 2021 03 November 2021
Machine: 2012 13" MacBook Pro Lenovo ideapad FLEX 4-1580, Intel® Core™ i7-7500U CPU @ 2.70GHz, 16 GB RAM
Network Connection: Ethernet Ethernet
Printer Reset? Yes - when enabled IPFS local node Yes - when enabled IPFS local node
Brave: 1.33.57 1.33.57
Chromium: 95.0.4638.69 (Official Build) nightly (x86_64) 95.0.4638.69 (Official Build) nightly (64-bit)
Revision: 6a1600ed572fedecd573b6c2b90a22fe6392a410-refs/branch-heads/4638@{#984} 6a1600ed572fedecd573b6c2b90a22fe6392a410-refs/branch-heads/4638@{#984}
OS: macOS Version 10.14.6 (Build 18G9323) Windows 10 Version 21H1 (Build 19043.1288)
JavaScript: V8 9.5.172.25 V8 9.5.172.25
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/95.0.4638.69 Safari/537.36
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/95.0.4638.69 Safari/537.36

Still occurs with Nightly 1.33.62.

macOS Windows
Date: 04 November 2021 04 November 2021
Machine: 2012 13" MacBook Pro Lenovo ideapad FLEX 4-1580, Intel® Core™ i7-7500U CPU @ 2.70GHz, 16 GB RAM
Network Connection: Ethernet Ethernet
Printer Reset? Yes - when enabled IPFS local node Yes - when enabled IPFS local node
Brave: 1.33.62 Chromium: 96.0.4664.27 (Official Build) nightly (x86_64) 1.33.62 Chromium: 96.0.4664.27 (Official Build) nightly (64-bit)
Revision: 0658dae02ef18b530eda4384920ee23f5e156c55-refs/branch-heads/4664@{#459} 0658dae02ef18b530eda4384920ee23f5e156c55-refs/branch-heads/4664@{#459}
OS: macOS Version 10.14.6 (Build 18G9323) Windows 10 Version 21H1 (Build 19043.1288)
JavaScript: V8 9.6.180.8 V8 9.6.180.8

UPDATE AFTER POSTED THIS COMMENT: The printer was in some weird state where it responded to scan request, but when I went to it and checked it it cycled power and nagged me, and now Nightly and IPFS Desktop reboot the printer when launched with IPFS local node enabled, again.


Well, now I’m a bit baffled. The current channel versions all use go-ipfs 0.10.0 but don’t do the printer thing, now. Only Nightly actually has the local node running - Dev, Beta, and Release all report go-ipfs offline and top in Terminal only lists go-ipfs when Nightly launches it (screenshot below). Because there isn’t a rational explanation, so far, I hesitate to list this as solved. [See note above about printer state - Nightly and IPFS Desktop still reboot it]

IPFS Companion had a notice in each case pointing me to the release notes for v2.19.1, and it does say that version introduced a fix for onboarding when enabling local node is the first interaction, but that was updated in June, so I don’t know why that would have changed anything today. [NOTE PER UPDATE: IT DIDN"T]

So it seems things are working as they’re supposed to with Nightly, and while local node isn’t working with Dev, Beta, or Release, at least they don’t reboot my printer.

Here are screen shots of Terminal and the IPFS local node status page with Nightly running:
image

The bottom line from above is that NIghtly with IPFS set to local node and IPFS Desktop 0.17.0 both still reboot the printer. Also, the command line version of go-ipfs v0.10.0 also reboots the printer.

In the IPFS issue it was determined that the issue is go-ipfs v0.10.0’s mdns implementation in go-libp2p. Apparently, go-ipfs v0.11.0 will use random DNS labels that the devs think should solve this problem.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.