|
Broadband-Hamnet™ Forum |
|
|
|
|
|
|
Subject :Re:Intermittant Link Resolution - Cold boot vs. Warm boot..
2014-08-10- 17:59:40
|
|
|
AF5RS |
|
Member |
|
Joined: 2014-06-23- 22:21:23
Posts: 9
Location: Highland Village, TX EM13LC |
|
|
|
Forum :
UBNT Firmware
Topic :
Intermittant Link Resolution - Cold boot vs. Warm boot
Andre, if it helps the effort, our networks is not large, however, the links are weak at this time due to experimentation and poor paths. I suggest it has to do with links coming in and out often which most likely is more probable in larger networks, however, it's happening on intermittent small networks. i.e. 2 to 3 nodes.
Bob AF5RS
|
IP Logged
|
|
|
|
|
|
Subject :Re:Intermittant Link Resolution - Cold boot vs. Warm boot..
2014-08-10- 17:28:48
|
|
|
K6AH |
|
Member |
|
Joined: 2012-03-05- 10:47:45
Posts: 181
Location: San Diego, CA |
|
|
|
Forum :
UBNT Firmware
Topic :
Intermittant Link Resolution - Cold boot vs. Warm boot
There appears to be a bug in release BBHN 1.1.2 which causes OLSR to crash periodically. It seems to be limited to larger, UBNT-based, networks, as it has not been reported on Linksys nor recreatable on UBNT networks of only a few nodes.
We are looking into the issue and will likely release a patch in the coming days which includes a watchdog reset of the OLSR as an interim workaround until the problem can be better understood and a fix put in place.
We are sorry for the inconvenience it may cause deployed networks, but wanted to get the word out to anyone planning such a deployment in the near term.
Andre, K6AH |
IP Logged
|
Member of:
Beta Test Team
San Diego Mesh Working Group
Running 3.0.1 |
|
|
|
|
|
Subject :Intermittant Link Resolution - Cold boot vs. Warm boot..
2014-08-10- 16:43:34
|
|
|
AF5RS |
|
Member |
|
Joined: 2014-06-23- 22:21:23
Posts: 9
Location: Highland Village, TX EM13LC |
|
|
|
Forum :
UBNT Firmware
Topic :
Intermittant Link Resolution - Cold boot vs. Warm boot
We're finding the latest firmware (1.2.1 (-v2)) for the Rocket M2 shows differing link results on a known prior good link. We have confirmed link may re reappear on a warm boot, may not. But a cold boot (POE power down and back up), the link most likely reappears. It also seems to be time related, the longer the link is up, the more likely it will become unstable, a warm boot doesn't seem to help, but then on a cold boot,and presto! back to normal. What's happening here? Kernel leak? Seems to take about a day of up-time before a cold boot is required. We're seeing this on multiple nodes with the -v2 firmware. Also, can't seem to reconcile the LQ with the S/N. Any body else seeing this? Bob AF5RS
|
IP Logged
|
|
|
|
|
|
Subject :Linksys access point..
2014-08-10- 15:52:35
|
|
|
KT4VOL |
|
Member |
|
Joined: 2014-08-09- 21:34:18
Posts: 6
Location: |
|
|
|
Forum :
Hardware
Topic :
Linksys access point
I have a WAP54G version 3.1. Is this supported for use with the mesh?
It has 2 detachable antennas with N connectors. I have seen some 2.4GHz amplifiers (up to 8W) on eBay. Has anyone had any luck using amplifiers?
|
IP Logged
|
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-10- 05:33:43
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
Forum :
Firmware
Topic :
WRT54G v2 & 1.1.2: DHCP issue
It was discovered as existing in 1.1.2 and a changset committed to the 'develop' branch of the code base to resolve it.
The 'develop' branch is the "may be less than stable, not everything 100% works or is 100% tested, not production ready" code line we use for the program development. Its a step on the way into being part of an official build.
|
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-10- 01:05:29
|
|
|
VE2ZAZ |
|
Member |
|
Joined: 2014-05-21- 19:29:55
Posts: 8
Location: Canada's Capital region |
|
|
|
Forum :
Firmware
Topic :
WRT54G v2 & 1.1.2: DHCP issue
Hi Conrad, thanks for providing a link.
I do not know about this issue being a duplicate of ticket #55. #55 is a vague description of a potential problem. Do I read that it got fixed in 1.1.2? If so, then it is either 1) not the same issue, or 2) that the problem did not get fixed.
What next?
Bert. |
IP Logged
|
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 15:52:42
|
|
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 14:13:34
|
|
|
VE2ZAZ |
|
Member |
|
Joined: 2014-05-21- 19:29:55
Posts: 8
Location: Canada's Capital region |
|
|
|
Forum :
Firmware
Topic :
WRT54G v2 & 1.1.2: DHCP issue
OK, but this is where I was checking, and I could not find ticket #55. Any link? |
IP Logged
|
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 14:08:12
|
|
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 14:02:45
|
|
|
VE2ZAZ |
|
Member |
|
Joined: 2014-05-21- 19:29:55
Posts: 8
Location: Canada's Capital region |
|
|
|
Forum :
Firmware
Topic :
WRT54G v2 & 1.1.2: DHCP issue
Hi Conrad, I have been trying to find the place where Ticket #55 is tracked, but cannot find it. Can you please provide a link to Ticket #55?
Thanks a lot and 73.
Bert, VE2ZAZ |
IP Logged
|
Last Edited On: 2014-08-09- 14:03:16 By VE2ZAZ for the Reason
|
|
|
|
|
|
Subject :Re:Bug in v1.1.2 whereas it mis-reports a node as a current neighbor..
2014-08-09- 13:47:15
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
Forum :
Bugs
Topic :
Bug in v1.1.2 whereas it mis-reports a node as a current neighbor
If I understand the concern correctly (node with a path one way show as a neighbor ). This sounds correct behavior to me. The node is indeed a neighbor (as defined by our routing service olsrd). It is a neighbor with a 1 directional path. Currently the software will not use such a route however it does keep track of it as a neighbor it can hear and could possibly become a bi directional neighbor if the RF path changed.
|
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|
|
Subject :Re:WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 13:41:29
|
|
|
|
|
|
|
Subject :Re:Lost connection..
2014-08-09- 09:05:01
|
|
|
KC9UUM |
|
Member |
|
Joined: 2013-08-21- 14:33:57
Posts: 1
Location: |
|
|
|
Forum :
Problems & Answers
Topic :
Lost connection
I've also been having problems since upgrading (I see this has been happening). Nearly went the TFTP route, then I tried something- it doesn't much fix the problem, but at least you know it's not totally bricked: (this assumes you have a "regular" network in your house) - On a computer connected to the home network, open your home router's status page which shows locally connected clients and their MAC/IP addresses.
- Connect the Internet/WAN port of the BBHN router to one of the LAN ports on your home router.
- Watch the home router's status page. You may have to refresh manually. A new device should pop up in the list.
- Open up the new IP address with port 8080. So, if the new device appeared as 192.168.0.103, type 192.168.0.103:8080 into your browser.
- You should be looking at the BBHN status page.
Now, this isn't solving the problem yet, just letting you know that it is alive and (almost) well. I tried to telnet and ssh to the BBHN router, no luck. I ran nmap against it, and the sole open port was 8080. Sounds like something puked during init. I plan on adding a serial port to see if I can get in that way and see what is going on.
/Ben |
IP Logged
|
|
|
|
|
|
Subject :Re:Mesh in the UK..
2014-08-09- 08:36:53
|
|
|
M0HER |
|
Member |
|
Joined: 2012-11-18- 07:24:42
Posts: 8
Location: |
|
|
|
Forum :
General
Topic :
Mesh in the UK
Thanks for the clarification Eddie. I just assumed you couldn't use the satellite frequencies as it didn't state otherwise.
Hopefully I can get some Linksys routers at some point to set up a network.
Thanks,
Jack. |
IP Logged
|
Last Edited On: 2014-08-09- 08:37:39 By M0HER for the Reason Formatting
|
|
|
|
|
|
Subject :Re:DCARA Recommended Equipment..
2014-08-09- 05:24:40
|
|
|
WX5WTF |
|
Member |
|
Joined: 2014-07-04- 06:48:17
Posts: 2
Location: Denton, TX |
|
|
|
Forum :
Denton/North TX
Topic :
DCARA Recommended Equipment
Dont forget that with the Ubiquiti equipment they only have one RJ45 port. This means you'll need a managed switch that supports 802.1q VLAN tagging if you wish to connect it to your existing home network. The cheapest one I've been able to find is around $50, here: http://www.newegg.com/Product/Product.aspx?Item=N82E16833127450
I'm new to VLAN stuff so this is definitely a learning experience. |
IP Logged
|
Last Edited On: 2014-08-09- 05:26:35 By WX5WTF for the Reason WYSIWYG Editors and I don't get along.
|
WX5WTF
|
|
|
|
|
|
Subject :WRT54G v2 & 1.1.2: DHCP issue..
2014-08-09- 02:57:42
|
|
|
VE2ZAZ |
|
Member |
|
Joined: 2014-05-21- 19:29:55
Posts: 8
Location: Canada's Capital region |
|
|
|
Forum :
Firmware
Topic :
WRT54G v2 & 1.1.2: DHCP issue
Hi, First of all, let me thank you all for the excellent work you have been putting on BBHN. Keep on the good work! OK, now the issue. I am seeing a DHCP bug with a WRT54G v2 unit running the latest firmware BBHN 1.1.2. Linksys ATA (Analog Telephone Adapter) SPA2002 or SPA3000 units will not receive a DHCP lease under any circumstance. My netbook and the raspberry Pi will get a lease, but not the ATAs. When connected to a WRT54GL v1.1 with the latest firmware, DHCP is working fine with the ATAs. Actually, all is fine under DD-WRT or the original Linksys firmware. It is only with 1.1.2 that this WRT54G v2 is showing this DHCP issue. I have tried a manual IP configuration on the ATA but that too does not seem to work. Thanks in advance, Bert, VE2ZAZ
|
IP Logged
|
|
|
|
|
|
Subject :Re:QUESTION about selling of nodes on this board..
2014-08-08- 10:28:17
|
|
|
KE6WEZ |
|
Member |
|
Joined: 2013-12-26- 22:12:13
Posts: 7
Location: |
|
|
|
Forum :
Hardware
Topic :
QUESTION about selling of nodes on this board
W8FS -
What would the price be?
Do they have the "new" or "old" firmware?
What would the package include (node/router, wall wart power, cat 5 cables, etc., etc.)?
Is shipping included or a separate cost? |
IP Logged
|
|
|
|
|
|
Subject :Re:Bug in v1.1.2 whereas it mis-reports a node as a current neighbor..
2014-08-08- 03:58:34
|
|
|
w6nct |
|
Member |
|
Joined: 2014-07-16- 16:29:30
Posts: 12
Location: |
|
|
|
Forum :
Bugs
Topic :
Bug in v1.1.2 whereas it mis-reports a node as a current neighbor
[Looks like I can now paste into input field, so will add original description of problem (below). I also sent it directly via eMail.]
======================================
I am sorry to draw attention to a possible shortcoming, because I am generally more than happy about what the development team has done thus far.
Background:
•For simplicity, I am shortening the node names, but all were based on user's call-sign and unique suffix.
•All nodes were configured the same (e.g., matching SSIDs, in ad-hoc mode, running the v1.1.2 firmware, un-encoded, with vertically polarized antennas, and valid node names).
•Node-101 was a standard Linksys (WRT54x), which we connected to a laptop using their LAN port connections and a standard CAT-5 Ethernet cable.
•Node-850 was a Bullet with a 24dBi directional antenna, on a 6 ft. mast. It was powered through a CAT-5 Ethernet cable, using a 24 VDC (PoE) power interface. The other port of the power interface was unconnected, such that the node only interfaced using its Wifi radio link.
•Node-851 was a Bullet with an omni-directional antenna, on a 15 ft. mast. It was powered through a CAT-5 Ethernet cable, using a 24 VDC (PoE) power interface. The other port on the power interface was unconnected, such that the node only interfaced using its Wifi radio link.
•Node-S was positioned on a distant hilltop; and was believed to be a Bullet, with an unknown type of antenna.
•Node-101 was placed on the roof of a vehicle, with the laptop inside; Node-850 was mounted on a mast, whose base-mount was affixed under the front tire of the vehicle; and Node-851 was initially positioned at the rear of the vehicle, and had a line-of-sight path to Node-S.
•After power-up and initialization, Nodes -101, -850, and -851 could all connect directly to each other; and could see each others' status screens.
•Prior to pointing Node-850's directional toward Node-S' location, none of the three local nodes could detect Node-S.
Information specific to alleged bug:
•The directional antenna connected to Node-850 was pointed toward Node-S.
•After a small delay, Node-850 could see and connect to the Node-S as a current neighbor (as reported by its Mesh Status).
•Node-101 could not detect Node-S as a current neighbor, but could see and connect to it as a remote node.
•Believing that we had a receiver de-sense issue (for a non-related reason), we relocated Node-851 to a fence post behind the vehicle (approximately 40 ft. away, but still having a line-of-sight path to Node-S).
•Node-851 reported that it could detect and connect to Node-S as a current neighbor; but when queried, Node-S did not also report Node-851 as its current neighbor. Node-851 and Node-101 were both listed as a remote nodes for Node-S. This seemed strange, so we investigated further.
•We decided to power-off Node-850; and after a small delay, Node-851's mesh status changed to report Node-S by its IP address only (presumably because it didn't have sufficient signal amplitude to connect as a current neighbor).
•This configuration was repeatable.
•We believe that this is a BUG; whereas a distant node is mis-reported as a current neighbor (instead of a remote host) if it has sufficient local signal to detect its IP address, but not enough signal to connect or report its node name, AND another of its current neighbors DOES have sufficient signal level to connect to the distant node and display (and share) its node name.
•This is not a critical BUG, and can easily be worked around.
•Screen captures and additional details are available, if needed.
Please Advise? |
IP Logged
|
|
|
|
|
|
Subject :Re:issue with [OLSR Status] link..
2014-08-07- 20:17:26
|
|
|
KG6JEI |
|
Member |
|
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: |
|
|
|
Forum :
Firmware
Topic :
issue with [OLSR Status] link
Trying to integrate to an existing network qualifies as an advanced deployment from the standpoint of BBHN. Every network will be different and will depend on how it's laid out and what tools they have so the only real answer that can be given is "set a route for 10.0.0.0/8 through the mesh node and to set DNS to query the mesh node". How you do that will depend on your existing network layout, how you wish client setup to go, etc. I can think of several topologies off hand in this scenario and each has it's advantage and disadvantage but they all depend on the tools and the desired layout. If it's a new user the best thing is to plug directly into the node and not try and complicate the deployment by integrating into an existing network. |
IP Logged
|
Note: Most posts submitted from iPhone |
|
|
|
|
|
Subject :Re:Ubiquiti Bullet M5-HP..
2014-08-07- 17:32:50
|
|
|
K6AH |
|
Member |
|
Joined: 2012-03-05- 10:47:45
Posts: 181
Location: San Diego, CA |
|
|
|
Forum :
Hardware
Topic :
Ubiquiti Bullet M5-HP
Yep. You select the center frequency (20MHz bandwidth) and the device stays on that channel. Andre, K6AH |
IP Logged
|
Member of:
Beta Test Team
San Diego Mesh Working Group
Running 3.0.1 |
|
|
|
|