MOX: how to netboot?

Software SW help
41

Same here.

It is a big progress but still quite far from expected result. No settings are available.

Again, anyone from Turris team willing to help? Otherwise I will create official ticket soon.
MOXes are being delivered and operated and support should react on the issue. Espcially if they seem to be generic and not isolated to single extremely customized configuration.

42

I already created official ticket two days ago - so far no response…

43

Thank you very much! I had the same issue, but your small Tutorial helped. The UI is broken too, but my WLan coverage is now perfect.

1 Like
44

I also got this kind of working for a while with these instructions, but I have never seen that it extends my wifi for real. I have seen the “heart beat” led blinking few days and then it just stopped blinking.

Probably I just wait that Turris team fixes software problems with this, UI at least is half baked and will need some love.

45

My coverage was extended, but suddenly today MOX stopped working :frowning:
(No heartbeat, just solid red LED)
Reboot doesn’t help. Any idea?

46

plus 1 Reset of MOX reconnecting in Firefox helped.

47

I tried it , but I can not bring him back to work again … I started from scratch, but no result.
netboot-manager shows no contend.

48

I didn’t say I’m on 3.11.6 RC4. I wrote to support, to inform them. Pepe wrote to me that they want release the new TOS 4 for MOX today. But I don’t know if 3.11.X pulls TOS 4 for MOX AP? I don’t have time to look for a solution. I just unplugged MOX, revoked paired device (in Firefox). Reset MOX, and repaired again (in Firefox).

49

I have similar issues with the users above. Below is the log what I have done to get network boot working for those new owners that are facing problem.

Important: Please remove the SD Card from Turris Mox for network boot.

  1. Reset to factory setting both Turris Omnia & Turris Mox.
  2. Configure Turris Omnia as per before (I reconfigured everything instead of restoring from backup)
  3. Install Turris Mox network boot package from the Updater tab in Foris. Let Turris perform the installation and reboot the device just to make sure.
  4. Connect Turris Mox to Turris Omnia LAN 4 while device is off
  5. Connect Turris Mox to power and let device boot
  6. The Foris UI for the new Managed Devices section does not work properly so I start configuring through SSH instead. Go to terminal and SSH to your Turris Omnia.
  7. Get the Turris Mox that is connected to your Turris Omnia either via Foris UI in Managed Devices -> Netboot or through SSH and run netboot-manager list. Copy the serial for the next step.
  8. In SSH execute the following command: netboot-manager accept $serial. Replace $serial with the serial you have copied in step 7. Wait for the system to do it’s thing.
  9. Once completed you should be able to see your device in Foris UI under Managed Devices -> Set Up & Managed Devices -> Wi-Fi but you will only see exclamation marks as the Foris UI is still not working as should. Congrats your Turris Mox is booting from network and act as an AP. Make sure your Turris Mox LED is blinking like a heartbeat after it fully boot.
1 Like
51

FWIW, I was encountering many of the issues described here. My two cents:

  • The Turris admin interface seems to support Chrome-based browsers only. In Chrome, netboot correctly shows the MOX device asking to get paired. In Safari and Firefox, the page does not display anything. Simiarly the Setup page - in Chrome, it’s possible to delete a device. In Safari & Firefox, when I click on the delete button, TypeError: undefined is not an object (evaluating 'button[0].localName') is thrown from subordinates-setup:176 (source code).

  • Instructions for performing a factory reset of MOX: Reset modes of Turris MOX

By switching to Chrome and performing a factory reset of my MOX, I was able to successfully restore netboot functionality that did not seem to work after restarting MOX. What’s even better, after I unplug MOX from the power and start it again, it automatically boots from the network.

The only problem that’s still remaining (for me) is the “WI-FI” page that is always waiting for information about devices & channels and never receiving it.

52

hello, for me, i have empy /srv/tft and /srv/turris-netboot/
so i must run at CLI Omnia this command: netboot-setup

That generate certificate, download netboot image etc. After that i have working MOX netboot AP.
It was helping, if this command could be at official documentation.