Thank heavens for this thread! With your help, I was able to successfully re-deploy my obsolete WRT54G3G-ST router in the service of ham radio!

I had tried flashing it with the standard issue WRT54G3G bin file but "upgrade failed". Once I put in the first four bytes as "W3GS" using GHEX (ubuntu Linux 12.04), it went perfectly.

Vy 73, aa4bb

If this is a Linksys node it is likely BBHN->ticket:55 which had already been discussed in the rest of the forum.

I am assuming both mesh nodes can see each other. What are your mesh nodes using (NAT or Host Direct)? Do you have another router available (say...node 3), that you can try? It could be a node-specific issue.

Yes I'm using NAT

You are likely seeing BBHN->ticket:59 where the olsr shuts down depending upon number of nodes in network.

In addition only one node can have a DHCP server running on a LAN.

If you power up a second node after one is already running and they are connected together already the onboard DHCP server detects that another dhcp server is already running and will not issue dhcp addresses I till rebooted.  If you used static addressing you should be able to access it directly.  This is more likely than the node dying.

Greetings all-

We've been playing around here with a bunch of nodes and recently at our repeater site, we've installed a Grid and Omni on the tower. I've seen the info regarding DTD Linking and figured with our setup that would be a better approach to tying the nodes together instead of RF.

Here's our setup: BulletM2 on 24dBi grid and BulletM2 on 9dBi Omni. In the shack we have a WRT54. I added patch cables from the Bullets' POEs and plugged them into Ports 3 & 4 on the Linksys.

Under current neighbors I see the nodes via RF and dtdlink. I've seen that traffic has passed via DTD as ETX numbers have came down considerably. However, it seems doing this crashes the nodes into non-existence after a short time (the Bullets are not even accessible even when directly connected to my laptop). Am I missing something in the whole scheme of DTD (ie., should we just be using L2 switches to tie the devices in or disable something in the Linksys or something on the Bullets)?? From all I've read it seems like all we should have to do is connect Ethernet together and go.

TIA,

John W3RC

I tried to set a Web server on the mesh but I can't get it to pass port 80 through the Bullet.  The service gets advertised OK but the port won't open.  I also tried the DMZ option but still nothing.  It works fine on the LAN.  Is this a known issue or am I doing something wrong?

Couple quick questions...What phone are you using? Are you using the correct RJ-45 jack on the back of the phone? Usually there are two jacks and one allows Ethernet pass-through. Have more than X devices (where X is from the X Host Direct) been plugged into the device at any particular time?

While setting up my pbx ive ran into a problem.  Phone 1 is set up to a node attached to the PBX server.  Phone 2 is set up on node 2 in the office.  While trying to configure phone 2 I can not get the router to give a IP Lease to the phone so I can add it.  If I plug into a computer it will show it but not the phone.  I swapped phones around and still get the same problem.  Any help would me appreciated.

Zack

Andrew, I'll second Conrad's statements. We still have confidence that these issues with olsrd can be worked through to provide a suitable connect security that fulfills a need in our community. The alternative is to wait 1 to 2 years for the olsr.org community to create olsr v2 implementation that they are working on now. We know that secure plugin is "not maintained" by olsr.org developers.

Note, it is also an option to comment out the secure plug in in the olsrd config file and take it out. This enables use of the 1.1.x features, e.g. 5g, DtD, fixes, etc.

So far we've found a 32bit overflow (fix already in 1.1.x images), an uninitialized variable (just compiled a linksys fix 2 days ago to test), and we have renewed focus on the crash issue.

The description of your environment sounds like you may be able to contribute? If you can reproduce an olsrd crash, please run valgrind - http://www.olsr.org/?q=valgrind . I am working to build an environment with sufficient memory to do this. Of particular interest is a lead from a coredump we have that occurred in file descriptor functions. There is a valgrind option to report file descriptor usage. If the array length is exceeded in the code of using too many socket/files opened, stack corruption occurs like you are seeing. Need to rule this possibility in/out... Please CC me on the other logs and continue discussion directly at ae6xe@cox.net .