|
Broadband-Hamnet™ Forum :: Problems & Answers |
|
|
|
|
|
Subject :DTDLink Co-located nodes..
2014-09-14- 07:50:22
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
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
|
IP Logged
|
Last Edited On: 2014-09-14- 07:51:18 By W3RC for the Reason Corrected Subject typo |
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-14- 09:08:12
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
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. |
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-14- 09:22:16
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
I knew I was missing a step. I'll look into shutting down DHCP on the Bullets and let the Linksys be the master DHCP for the site. Currently we have about 12-14 UBNT devices on our mesh.
Thanks for the help Conrad!!
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-16- 14:03:52
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
After a few days of running DTDLink, I've decided to just go back and take the RF hit on site. Since running the DTDLink, the Bullets (namely our grid node) fall off quickly. Today after powercycling the PoE, it only lasted 20 minutes before it went into never never land. So far, from our experience here, the OLSR lasts longer without DTDLink. Yes, we've had to "soft" reset a time or two a day but can do remotely. Now with DTD, I'm having to physically go to the site to hard reset them. Don't know if this gives anyone on the dev team any more clues to the issues with UBNT.
73,
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 03:43:41
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Just an update if anyone is following along with this...
After disconnecting DTDLink, our nodes have been up and running 15+ hours, so far stable (as 2.4GHz can be ;)) and happy meshing away. Will update this post (even if it's just for the post counts LOL) if anything changes.
73,
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 12:19:50
|
|
|
AE6XE |
|
Member |
|
Joined: 2013-11-05- 00:09:51
Posts: 116
Location: |
|
|
|
Thanks for the data point. I'm working to debug this. The symptoms I've seen so far point to an increase in failures with increase in olsr traffic--a scalability issue. We all still see crashes with/without Secure plugin. If you find that you are not getting crashes at all when DtDlink is taken out, this would be significant to known.
The coredumps I have inspected show stack corruptions (for the programmers in the crowd). I have olsrd recompiled with mudflap code insertions to find the bad code causing this. It will take a few more days to find the time and try to reproduce the problem to collect this debugging data.... |
IP Logged
|
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 12:27:02
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Not a problem. Glad to help out. Saw the posting of v3 firmware today so we are going thru our nodes and trying it out on our setup here. Will keep an eye on stuff and report out.
We had 1.1.2 running solely on RF and had everything running for 24 hours with no hiccups. I was also thinking olsrd had something to do with the crashes as well.
73,
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 12:27:07
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Not a problem. Glad to help out. Saw the posting of v3 firmware today so we are going thru our nodes and trying it out on our setup here. Will keep an eye on stuff and report out.
We had 1.1.2 running solely on RF and had everything running for 24 hours with no hiccups. I was also thinking olsrd had something to do with the crashes as well.
73,
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 12:27:35
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Not a problem. Glad to help out. Saw the posting of v3 firmware today so we are going thru our nodes and trying it out on our setup here. Will keep an eye on stuff and report out.
We had 1.1.2 running solely on RF and had everything running for 24 hours with no hiccups. I was also thinking olsrd had something to do with the crashes as well.
73,
John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-17- 12:27:37
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Sorry for the multi-posts, was trying to update nodes, talk on repeater, post note to forum, and watch a 2 year old all at once. And, apparently my cell phone hates me LOL. So far v3 is running smoothly. RF only, not trying DTDLink yet. I would like to get a baseline of operation first, then take the next step. I'll start a new thread on v3 in the appropriate place if needed and update DTDLink finds here in this post. 73, John W3RC
|
IP Logged
|
Last Edited On: 2014-09-17- 13:09:30 By W3RC for the Reason |
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-18- 13:45:06
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
So far we've been up and running just over 24 hours, RF only, without a single crash or need to reboot any node. Due to our setup and paths, nodes have been going in and out but every time everything gets picked back up and runs smoothly. Tomorrow I'm planning on trying DTDLink at our repeater site and observe for 24 hours as well. V3 btw. 73, John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-18- 15:54:07
|
|
|
AE6XE |
|
Member |
|
Joined: 2013-11-05- 00:09:51
Posts: 116
Location: |
|
|
|
What is the node count on your mesh? Ideally send the olsr-topology-view image. http://www.broadband-hamnet.org/download/firmware/olsr-topology-view
ae6xe@cox.net |
IP Logged
|
Last Edited On: 2014-09-18- 15:55:48 By AE6XE for the Reason |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-18- 16:03:52
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
I will load the topology viewer tomorrow after work. We have 15 nodes running right now. Of that, 9 are UBNT and remaining are Linksys. I still have 2 more yet to turn on, both are Linksys. John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 10:54:29
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
So apparently on Linksys device the eth0.2 interface is not activated? Trying to DTDLink via a Linksys at the repeater site and I'm not getting anything. Though I could be missing a step again, however when I looked into olsr config (via webpage) it's showing eth0.2 down. Tried to telnet into router but was unable. Basically used win7 builtin telnet client. So for now nodes are still RF only but I did see 2 of my ubnt devices report a olsr restart of about 5 hours ago on status screen. I'll have to look into the router later but for now I'm unable. Maybe someone can look quick? John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 11:36:57
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
Correct, Due to the issues with the onboard switch on Linksys devices DTDLink ships in a disabled state in the 3.0.0 beta build. Please see http://ubnt.hsmm-mesh.org/products/BBHN/wiki/HowTo/Enable%20DTDLINK%20on%20Linksys for the current procedure to enable DTDLINK on Linksys
|
IP Logged
|
Last Edited On: 2014-09-25- 09:27:59 By KG6JEI for the Reason Pull out procedure and redirect to updated developres wiki page |
Note: Most posts submitted from iPhone |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 14:37:26
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Thanks Conrad. I figured something had to be off, but wasn't sure if it was meant to be or not. I'm going up the site tomorrow to do some work on one of our repeaters, so I'll try this then. But, so far, 48+ hours of uptime on our nodes here and nothing crashed down...no hard power cycles, no soft power cycles, just 2 olsr restarts reported on status screen of 2 nodes (one each after around 36 hours of uptime) though I have yet to check them all. And with our path variables and some temp setups, nodes have been popping in and out. John W3RC |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 16:18:56
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
"just 2 olsr restarts reported" thats excessive on it's own, so maybe more useable but goes to show something much more than OLSR secure was at work, just enough of a solution to let things run but FAR from a fix... |
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 16:28:37
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
After going thru all of our nodes,4 of them show an olsr restart. 3 say runtime 0 and 1 says runtime 2. All nodes were ubnt based, specifically bullet m2 hardware. Don't know if that points anything out further. I agree, any error report is 1 too many, however considering how it was previously, this vast improvement towards regaining usable stability. As far as scalability goes, didn't the 0.6.6 version address that? Sorry, I'm coming a bit late to the table if this was already addressed. |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 16:37:16
|
|
|
W3RC |
|
Member |
|
Joined: 2014-09-01- 18:58:19
Posts: 22
Location: Freeland, PA FN-21 |
|
|
|
Sorry, a quick look on their page and I'm referring to 0.6.5.5 which includes fixes on memory leaks when adding and deleting routes, and some other olsrd tweaks. Just curious if it's been considered...sorry if I'm stepping on any toes here. |
IP Logged
|
73,
John W3RC |
|
|
|
|
|
|
Subject :Re:DTDLink Co-located nodes..
2014-09-19- 18:43:53
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
No worries, We are very much attempting to embrace a more open development environment than had been seen with the group in the past so feedback, comments, suggestions, etc are welcomed. i think you are reffering to this commit http://olsr.org/git/?p=olsrd.git;a=commit;h=2beaac8b9b1b9eef09e312b165fe61e3fef99eda Which is actually in the Quagga module only. Quagga is another routing daemon and we don't utilize it and we don't load the quagga module so if this is the one you mean it should not be related. If it's a different unrelated commit than honestly I haven't seen it and would love the pointer as i would certainly consider it relevant. |
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|