MOX: how to netboot?

On RC3, the MOX boots up (heartbeat LED) only for the first time after pairing. All subsequent reboots of MOX result in constantly lit LED light. Nothing ever appears on Managed Devices->Set up.

1 Like

Now I found the Tab “Managed Devices”
There are 3 Listpoint: SET UP, WLAN and NETBOOT

In Tab NETBOOT there is found a Device with Serial 0000000D30006BBE
but nothing happend if I “Accept”
The Tab SET UP is empty.

I now see the same tab, and my Mox (which I paired using netboot-manager), is listed under Netboot.
I don’t see anything under “Setup” or “Wi-Fi”. How do I get a token referred to under “Setup”?

Ok, now with RC5 MOX can boot up every time and I even see it broadcasting the SSID. But the Set Up and Wifi tabs in Managed devices is still empty.

Also, my Omnia uses channel 7 on 2.4 GHz band. Once MOX chose channel 4, but second time it chose 6, which is kind of nonsense given that both routers are in the same room for testing. Is the wifi channel a truly random choice, or does the router scan the air in order to choose the best option? So far, my evidence would suggest the former.

Currently selection of channels is random but can be enforced by modifying a config file. See
https://doc.turris.cz/doc/en/howto/mox_network_boot#under_the_hood

1 Like

Exact same behavior as peci1here. I have the same questions. I can SSH to thr MOX but I have no password.

Anybody managed to get the MOX-AP netboot from the Omnia?
I got thus far that the MOX AP seems to download its boot-file and boots off that file, But then it seems to be stuck and I am not able to manage it through the Foris web-console. It shows up under “Managed-Devices - WiFi”, but with an exclamation mark and spinning circles…
It also shows up under “Managed-Devices - Set up / Device List” - but pressing on the pencil to edit / setup the device nothing happens…
Any help is greatly appreciated!

Same problem here

Which browsee do you use?
With firefox I can edit in the SET-UP Tab

In the TAB WLAN i´ve got spinning circles
In the TAB NETBOOT i´ve got paired

Yep, same here. I have my MOX paired, in the setup tab I could click the edit icon and name it. But… it’s state is listed as ! and in the WiFi tab its state is again ! and devices and channels just show spinning circles.

So far I’m disappointed here - starting to think I bought an expensive door-stop :frowning:

Same problem here.

Still useless… tested a weak ago and after unpairing, deleting boot image a reseting mox I was able to test working wifi. Not possible to configure or see status in Forris, but detected signal. Today I tried to test it again and there is no wifi signal at all.

It seems no one from turris team care about they sold devices not working. Sad… for that price it should be plug-in and work, not debug for hours.

For me, it worked relatively straight forward. Yes, the Forris plugin seems to be buggy still (exclamation mark, devices and channel also not available) but by using netboot-manager on the cli I could accept the pairing request and Mox seems to work nicely since then.

Is there some better guide how to diagnose what is happening? I already spent 10 hours trying to get it work with no success - same story as above but let me repeat:

  • bought Turris MOX “AP option” (just CPU module A)
  • plugged it via Ethernet cable to my Turris Omnia, connected power cable …and nothing happened (LED diod went on and is permanently on) and nothing in Forris
  • followed guide here: doc.turris.cz/doc/en/howto/mox_network_boot (cannot put links as new user)
  • installed Turris MOX network boot package list from the Updater tab
  • plugged it via Ethernet cable to my Turris Omnia, re-connected power cable …and nothing happened (LED diod went on and is permanently on) and nothing in Forris
  • run “Rescue Mode 3: Factory reset” as described here: doc.turris.cz/doc/en/howto/mox_rescue_modes (cannot put links as new user) (this should be YouTube video)
  • plugged it via Ethernet cable to my Turris Omnia, re-connected power cable …and nothing happened (LED diod went on and is permanently on) and nothing in Forris
  • started to figure out how to open (seriously guys you should make YouTube video how to open as this is non-trivial) - luckily I did not damage the plastic covers
  • I tried to put in my own microSSD card to test if the router is totally broken or whether it works
  • configured microSSD: doc.turris.cz/doc/en/howto/mox_microsd_card (cannot put links as new user)
  • run “Rescue Mode 4: USB flashing” as described here: doc.turris.cz/doc/en/howto (cannot put links as new user)
  • I was able to boot as normal Router - so it seems the router works… spent couple of hours trying to configure manually with no success
  • I removed the microSSD card
  • run “Rescue Mode 3: Factory reset” as described here: doc.turris.cz/doc/en/howto/mox_rescue_modes (cannot put links as new user)
  • plugged it via Ethernet cable to my Turris Omnia, re-connected power cable …and nothing happened (LED diod went on and is permanently on) and nothing in Forris
  • I tried to follow the manual part logging to OS version and running netboot-manager list command (as root) - no router displayed anywhere on list
  • I tried netboot-manager regen and netboot-manager update_rootfs commands (as root)
  • plugged it via Ethernet cable to my Turris Omnia, re-connected power cable …and nothing happened (LED diod went on and is permanently on) and nothing in Forris and nothing in netboot-manager list

Bottom line - it does not work… I got feeling the MOX does not boot however I have no idea how to find out why? Is there any way to diagnose?

Feedback - guys this sucks so much - Turris Omnia was AWESOME… Turris MOX is so far piece of crap - you did not do very good job here - it does not work for dozens of users (as seen above) and still after such long time since release there is no solution, no documentation, etc…

1 Like

So did some research and seems best way to debug is to check system log via command logread - found there following error messages:

2019-07-14 18:03:07 info dnsmasq-dhcp[5128]: DHCPDISCOVER(br-lan) xx:xx:xx:xx:xx:xx
2019-07-14 18:03:07 info dnsmasq-dhcp[5128]: DHCPOFFER(br-lan) 192.168.1.142 xx:xx:xx:xx:xx:xx
2019-07-14 18:03:07 info dnsmasq-dhcp[5128]: DHCPREQUEST(br-lan) 192.168.1.142 xx:xx:xx:xx:xx:xx
2019-07-14 18:03:07 info dnsmasq-dhcp[5128]: DHCPACK(br-lan) 192.168.1.142 xx:xx:xx:xx:xx:xx
2019-07-14 18:03:07 err dnsmasq-tftp[5128]: file /srv/tftp/C0A8018E.img not found
2019-07-14 18:03:07 err dnsmasq-tftp[5128]: file /srv/tftp/pxelinux.cfg/xx-xx-xx-xx-xx-xx-xx not found
2019-07-14 18:03:13 err dnsmasq-tftp[5128]: file /srv/tftp/pxelinux.cfg/xx-xx-xx-xx-xx-xx-xx not found
2019-07-14 18:03:22 err dnsmasq-tftp[4312]: Last message 'file /srv/tftp/pxeli' repeated 1 times, suppressed by syslog-ng on turris
2019-07-14 18:03:23 err dnsmasq-tftp[5128]: file /srv/tftp/pxelinux.cfg/xx-xx-xx-xx-xx-xx-xx not found
2019-07-14 18:03:28 err dnsmasq-tftp[5128]: file /srv/tftp/pxelinux.cfg/xx-xx-xx-xx-xx-xx-xx not found
2019-07-14 18:03:29 err dnsmasq-tftp[5128]: file /srv/tftp/pxelinux.cfg/C0A8018E not found
2019-07-14 18:03:38 err dnsmasq-tftp[4312]: Last message 'file /srv/tftp/pxeli' repeated 1 times, suppressed by syslog-ng on turris

I have to join to Tomas.
Same symptoms. Obviously MOX is trying to do something but without a success. Just lighting red.

From Omnia logs after Mox power-on:

2019-07-15 17:55:44 info dnsmasq-dhcp[4787]: DHCPDISCOVER(br-lan) d8:58:d7:xx:xx:xx
2019-07-15 17:55:44 info dnsmasq-dhcp[4787]: DHCPOFFER(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:44 info dnsmasq-dhcp[4787]: DHCPREQUEST(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:44 info dnsmasq-dhcp[4787]: DHCPACK(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:44 err dnsmasq-tftp[4787]: file /srv/tftp/C0A80A66.img not found
2019-07-15 17:55:44 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/01-d8-58-d7-xx-xx-xx not found
2019-07-15 17:55:44 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A80A66 not found
2019-07-15 17:55:44 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A80A6 not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A80A not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A80 not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A8 not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0A not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C0 not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/C not found
2019-07-15 17:55:45 info dnsmasq-tftp[4787]: sent /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox to 192.168.1.102
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/default-arm-mvebu not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/default-arm not found
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/pxelinux.cfg/default not found
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPDISCOVER(br-lan) d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPOFFER(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPREQUEST(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPACK(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/boot.scr.uimg not found
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPDISCOVER(br-lan) d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPOFFER(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPREQUEST(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 info dnsmasq-dhcp[4787]: DHCPACK(br-lan) 192.168.1.102 d8:58:d7:xx:xx:xx
2019-07-15 17:55:45 err dnsmasq-tftp[4787]: file /srv/tftp/boot.scr.uimg not found

So obviously some file is found but then boot is not. And there is quite not much things in the tftp directories:

root@turris:~# ll /srv/tftp/
drwxr-xr-x    1 root     root            52 Jun 20 13:35 .
drwxr-xr-x    1 root     root           106 Jun 20 13:34 ..
drwxr-xr-x    1 root     root            56 Jun 20 13:35 pxelinux.cfg
drwxr-xr-x    1 turris-n root             6 Jul  4 02:16 turris-netboot
root@turris:~# ll /srv/tftp/pxelinux.cfg/
drwxr-xr-x    1 root     root            56 Jun 20 13:35 .
drwxr-xr-x    1 root     root            52 Jun 20 13:35 ..
-rw-r--r--    1 turris-n root             0 Jun 20 13:35 default-arm-mvebu-turris_mox
root@turris:~# ll /srv/tftp/turris-netboot/
drwxr-xr-x    1 turris-n root             6 Jul  4 02:16 .
drwxr-xr-x    1 root     root            52 Jun 20 13:35 ..
-rw-r--r--    1 turris-n turris-n  16078772 Jul  4 02:16 mox

So Turris team, what are we doing wrong?
Thanks.

My problem is probably this one:

2019-07-15 21:40:18 info dnsmasq-dhcp[7296]: DHCPDISCOVER(br-lan) d8:58:d7:00:**:**
2019-07-15 21:40:18 info dnsmasq-dhcp[7296]: DHCPOFFER(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:18 info dnsmasq-dhcp[7296]: DHCPREQUEST(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:18 info dnsmasq-dhcp[7296]: DHCPACK(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:18 warning dhcp_host_domain_ng.py[]: Add_lease, hostname check failed
2019-07-15 21:40:19 info dhcp_host_domain_ng.py[]: Refresh kresd leases
2019-07-15 21:40:23 info dnsmasq-tftp[7296]: sent /srv/tftp/turris-netboot/mox_0000000D3000**** to 192.168.18.192
2019-07-15 21:40:23 info dhcp_host_domain_ng.py[]: DHCPv4 new lease
2019-07-15 21:40:23 warning dhcp_host_domain_ng.py[]: Add_lease, hostname check failed
2019-07-15 21:40:23 warning dhcp_host_domain_ng.py[]: DHCP unknown update operation
2019-07-15 21:40:23 info dhcp_host_domain_ng.py[]: Refresh kresd leases
2019-07-15 21:40:39 info dnsmasq-dhcp[7296]: DHCPDISCOVER(br-lan) d8:58:d7:00:**:**
2019-07-15 21:40:39 info dnsmasq-dhcp[7296]: DHCPOFFER(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:39 info dnsmasq-dhcp[7296]: DHCPREQUEST(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:39 info dnsmasq-dhcp[7296]: DHCPACK(br-lan) 192.168.18.192 d8:58:d7:00:**:**
2019-07-15 21:40:39 warning dhcp_host_domain_ng.py[]: Add_lease, hostname check failed
2019-07-15 21:40:39 info dhcp_host_domain_ng.py[]: Refresh kresd leases
2019-07-15 21:40:39 info sshd[19186]: Connection closed by authenticating user turris-netboot 192.168.18.192 port 50046 [preauth]

I’ve looked at what goes into the dhcp_host_domain_ng.py script as the hostname, and it is *. Then it seems right the DHCP script fails…

Got it - I only had to factory reset MOX. Now it shows up correctly even in the Setup tab (with an exclamation mark, but it works).

I had same problem.
I used to have Boot over a network.

This is optional:
Disconnect Mox from Omnia.
Maybe backup of tftp folder (not so necessary, because Mox tftp is in different folder).
Than revert changes from Boot over a network tutorial.
Reboot?
Than do a snapshot if you want (whatever seams reasonable to you).

Factory reset of Mox.
Try follow this guide:
Mox netboot requirements of DHCP (I think there should also be quotes at the end of the line „ssh-keygen…“).

That didn’t help me, because of a missing file.
So what I did next?
Disconnect Mox.
Revert to snapshot before netboot.
Factory reset of Mox.

Install Turris MOX network boot in Foris.
Create file C0A8018E.img CLI:
touch /srv/tftp/C0A8018E.img

Follow previous guide:
Mox netboot requirements of DHCP (remember quotes).
Reboot Omnia.

Wait…

If it still works you can delete file C0A8018E.img (if is still there).
And you can revert file permissions of /srv/tftp/pxelinux.cfg to previous state (just my guess no answer from turris team).

So I decided to factory-reset both routers… with no success - still did not work even on freshly wiped devices => so this is clearly defect in the Turris OS - I suspect the one on Turris Omnia…

Then I read the link provided by Perry (big thanks - seems community cares more than Turris team)…

In short this is what I did (following guidance from Petan there):

  • checked file default-arm-mvebu-turris_mox - indeed it is size 0 (empty)

    root@turris:/srv/tftp/pxelinux.cfg# ls -la
    drwxr-xr-x    1 root     root            56 Jul 14 19:14 .
    drwxr-xr-x    1 root     root            52 Jul 14 19:14 ..
    -rw-r--r--    1 turris-n root             0 Jul 14 19:14 default-arm-mvebu-turris_mox
    
  • removed file default-arm-mvebu-turris_mox

    root@turris:/srv/tftp/pxelinux.cfg# rm default-arm-mvebu-turris_mox
    
  • run netboot-manager regen

    root@turris:/srv/tftp/pxelinux.cfg# netboot-manager regen
    /usr/bin/netboot-manager: line 96: can't create /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: Permission denied
    
  • fixed owner (I think this is cleaner then setting permissions to 777)

    root@turris:/srv/tftp/pxelinux.cfg# chown turris-netboot /srv/tftp/pxelinux.cfg
    
  • run netboot-manager regen

    root@turris:/srv/tftp/pxelinux.cfg# netboot-manager regen
    
  • checked file default-arm-mvebu-turris_mox - now it has some content

    root@turris:/srv/tftp/pxelinux.cfg# ls -la
    drwxr-xr-x    1 turris-n root           120 Jul 16 16:34 .
    drwxr-xr-x    1 root     root            52 Jul 14 19:14 ..
    -rw-r--r--    1 turris-n turris-n       562 Jul 16 16:34 default-arm-mvebu-turris_mox
    
  • then repeat the procedure here: https://doc.turris.cz/doc/en/howto/mox_network_boot

  • now I can see the MOX router correctly displayed in Forris UI in section Managed Devices > Netboot

  • then I clicked “Accept” and it is displayed in Wi-Fi section - however status there is showing Exclamation Mark icon - so not sure what this means

    image

  • the setup was tested and where was no signal is now good coverage - so it seems it somehow works…

1 Like

I wonder if there is any way how to see if the MOX really works without issues and that the Exclamation Mark icon means…

Update: I checked and there is no Web UI - however there seems to be ssh open - when I tried to connect (tested both password and ssh key) it refused the connection… there is probably some default password coming as part of the image… No idea how to connect to MOX to check it’s heath…