ROBIN - Open Source Mesh Network

funchip

While I'm still debugging an OrangeMesh server, I ran into a bigger problem. If the network failed to make the switch from open-mesh to OrangeMesh, it pretty much died.

In theory, the network should still operate without a dashboard. Unfortunate, the connection became on-and-off in this case. The network access status on my Vista laptop showed a swing between "local and internet" and "local only" back and forth in a few minutes. When "local only", you can't google nowhere.

As other folks pointed out, updt_srv is one place where the value changed when switching. So I ssh to all the nodes and edited the /etc/config/general, reset the value of 'updt_srv' back to 'checkin.open-mesh.com'.

All nodes then returned to the open-mesh dashboard. But some repeaters disconnected once a while. I posted the logread status at

Only registered users can see links on this forum!
Register or Login on forum!

Seemed something wrong with "ath_mgtstart: discard, no xmit buf."

I think we need a procedure to recover when failed from making a switch.

Any idea?

chance · User Joined: 24 Jul 2008 Posts: 12 Location: Michigan USA

I think a flash back to stock would do you well. I have done it about 5 times now while modifying things I shouldn't be inside the firmware. The procedure is documented on the Open-Mesh site.

If you have an older firmware I would use that one since the one on the site defaults to OLSR.
_________________
Stuff goes here

nebula · User Joined: 04 Dec 2009 Posts: 26

I've made the dashboard switch from Open-mesh to OrangeMesh. I am trying to re-flash the original firmware and switch back to Open-mesh dashboard. I might have changed the channel from 5 to 11. Following the re-flash guidance, I got:
Expect arp length 60, received 42
Non arp received, Make sure, the device is connected directly,
Expect arp length 60, received 42
Expect arp length 60, received 42
Expect arp length 60, received 42
Expect arp length 60, received 42
Non arp received, Make sure, the device is connected directly,
Non arp received, Make sure, the device is connected directly,
Expect arp length 60, received 42
Expect arp length 60, received 42
Expect arp length 60, received 42
Expect arp length 60, received 42

^C

Anybody can help?

Thanks

ispyisail · Posted: Fri Jan 22, 2010 5:05 pm Post subject:

@nebula

You need to connect your node (ROBIN router) direct to your PC. If your PC has more than one NIC you need to make sure you have selected the correct NIC.

What is you router model and make?
Where did you get the firmware from?
Flashing method?

Check your hardware is good e.g. a few people have posted that their Cat5 cable was bad
_________________
Open-Mesh Wiki:

funchip · Posted: Fri Jan 22, 2010 5:29 pm Post subject:

@nebula, if you were not too far down alter the firmware, you might have an easy way out if you just want to switch back to open-mesh dashboard. SSH (use putty.exe if on a PC) to the node, edit (use vi in my case) /etc/config/general, and change the value of 'updt_srv' field from you current dashboard to 'checkin.open-mesh.com'.

A formal way of doing it would be something like

Code:

uci set general.services.updt_srv="checkin.open-mesh.com"
uci commit general
reboot

But I typically just vi and edit the file directly, my bad practice. ;-\

nebula · User Joined: 04 Dec 2009 Posts: 26

guys, thanks a lot for your helpful responses.

Hardware: open-mesh/accton router (mini)
Ethernet Port connection: verified;

\open-mesh-flash
Usage:
open-mesh-flash [ethdevice] flashes embedded kernel + rootfs or ubqui
open-mesh firmware r2671
open-mesh-flash [ethdevice] rootfs.bin kernel.lzma flashes your rootf
nel
open-mesh-flash [ethdevice] ubnt.bin flashes your ubiquiti image
open-mesh-flash -v prints version information

The 'ethdevice' has to be one of the devices that are part of the suppo
ce list which follows.
You can either specify its name or the interface number.

1: \Device\NPF_{8F7F0179-EC85-4E0A-85D0-266A3AB95494}
(Description: MS Tunnel Interface Driver)

2: \Device\NPF_{39C81507-9BF4-4704-996B-7BBE45D498B1}
(Description: Microsoft)

3: \Device\NPF_{73B71B62-7C2B-49EB-8561-C7879A23F0F2}
(Description: Intel(R) 82566MM Gigabit Network Connection)

..\open-mesh-flash 3

Expect arp with length 60, received 42
Expect arp with length 60, received 42
Expect arp with length 60, received 42
Expect arp with length 60, received 42
Expect arp with length 60, received 42
Expect arp with length 60, received 42
Expect arp with length 60, received 42
Non arp received. Make sure, the device is connected directly!
Non arp received. Make sure, the device is connected directly!
Non arp received. Make sure, the device is connected directly!
Non arp received. Make sure, the device is connected directly!

ispyisail · Posted: Fri Jan 22, 2010 8:21 pm Post subject:

Try "Fon Flash"

see wiki
_________________
Open-Mesh Wiki:

nebula · User Joined: 04 Dec 2009 Posts: 26

I will try it out and keep you guys updated.

nebula · User Joined: 04 Dec 2009 Posts: 26

My mistake... I should've powered off the router before I initiated the flash process. Now the open-mesh-flash works and so does the Fon-flash.

Thanks a lot!

nebula wrote:

I will try it out and keep you guys updated.