Afternoon all,

I am recently into the mesh side of things and seem to have made a mistake at some point I think?  I have two nodes now, one a WRT54Gv3 and the other a WRT54GSv1.1, both running 0.4.3 FW.  Both can be connected to via lan cable, both can see the other if you connect to each one respectively and can be seen from the other node, to a point.. I will explain and please feel free to let me know if what I am seeing is "normal."

If I go under the Mesh Status button I can easily see the second node but if I click on it, the second node, I get the page stating that it cannot find the server on kd5wek-moble(GS). I did swap the nodes about and try using the GS to reach the G and its the same way, under mesh status, it lists the second node and has a link for the name but again when clicking on it the same page appears ?  I am hoping to eventually make this a mobile or portable node but am trying to ensure that they are operating as designed.  I am wondering if this has to do with advertised services ?  

I also appear to not be able to hit the node using the http://localnode:8080 link but have to use the ip address.  When attempting to access using the localnode it immediately shows a www.localnode.com:8080 so not sure why this is?  I did try using a different browser, IE8, and it also has issues accessing using the localnode link? Mind you I did some more checking and yes I did read the help file regarding having Javascript and page redirection enabled. This appears to be the default for Firefox as there is a checkbox to give the browser the ability to warn when a page is redirecting.  

I am able to see the other node using the WiFi scan and am also able to see the SNR info as well.

My other question is regarding the OLSR status button..

I have been browsing the forums about the OLSR button being greyed out and read that this is normal due to only using one node and that till more than one is connected OLSR has nothing to report, having only one till recently that was the case.  However I have two now and the button is active BUT when I click on it I do not get a page, I get that Firefox was unable to find the server at kd5wek-home or kd5wek-moble depending on which node I am logging into, having tried it both ways.  Previously when I took this same node, the G model, to last months digital wednesday I was able to select the OLSR button and see information there?

So I guess I am curious to know why the OLSR Status is not producing information when previously it was as there is more than one node here and also why I cannot see the page for the other node when I click on the link under mesh status?

Both nodes have been flashed using the appropriate packages, the G and GS, I even attempted an update the the GS using the trx file in case something was not quite right, this did complete and I have been able to get back in successfully.  Both nodes have been left with the default settings, aside from changing node names, no they are not the same and the passwords.  Both nodes have been as far as 15-20 feet to within 5 feet currently.

So any information would be greatly appreciated and if anyone has any tips, tricks, hints I would love to hear these as well. 

Take Care KD5WEK, Adam

Which is why I stated that my routers will remain unmodified (so you're preaching to the choir).

With all due respect to the human race, in my "day job" I've dealt with PHDs who don't have the sense to use a telephone.  I would expect no more or no less from a licensed Amateur Radio operator and a clearly labeled WRT54G or a homebrew POTSAC.

--
KJ4AJP

The trick to working the RP-TNC's is a hot iron (I crank my Weller up to 850 (max)), and then hold it over 2 pins (of the 4 corners) at once, and work it back and forth, lifting each side a bit at a time.

If the iron isnt hot enough, it wont budge and/or you will burn the PCB (been there done that).

Times like these I wish I had my dads ol 1950's era monster iron (it was like 450W or something...more for soldering gutters or something) :-)

Good Luck

KTF

Thanks for the offer (and testing tips from you and KD5MFW). 

I actually have a Gv2 that took the firmware but doesn't show S/N ratio, so I assume the radio's dead in it.  I kick myself for giving the guy good feedback for quick shipping before testing it, but absorbed its minimal cost in the other 5 I bought from other sellers that did work, and in particular the GLv1.1 that was given me by a non-ham (the one with DD-WRT I had issues with).  I did try desoldering the RP-TNC from the dead one but the body was acting as a heatsink and after burning my fingers enough I decided to cut the coax on the crippled one, solder on the 1/2W and put the PCB back in it's case.  The plan is to use it with a 2W amp, so I only need one output anyway.  It's working fine with the stock antenna, linking with the other 5.  I have them all set up in the office (PBX room here at the University, I'm the Telephone Tech), I'm just waiting on $$$ for antennas and adapters (and VoIP hardware... and IP cameras...). Then I can get out and do some "real world" distance tests

I'm glad to see MESH made QST's cover!  I'm having a blast with them so far, 10 years ago when I was doing the University's data wiring and 5 before I got the Ham license, I was doing things like this:

http://www.utm.edu/staff/relmore/wireless/

My main supplier was Hyperlink, this was before they were acquired by L-Com, and I bought connectors and tooling from FAB.  We had limited clients attaching to the network back then, now with every student having a smartphone looking for an IP there are around 800 Aruba APs across Campus.

Our area is fairly flat, and trees grow taller than the 4-story buildings on Campus (tallest buildings in the area), so I don't know how well MESH can be implemented for any long-range use, but I just need to get out and experiment once I have the goodies.

--
KJ4AJP

I'm sure pointing the finger at Joe will be much appreciated after the damage is done, perhaps during an emergency, or when he damages the network switch at some public safety site where your local ham radio group is helping. 

Or when you apologize because you gave Joe the wrong router and though you had given him one of the ones you hadn't modified the power on.

I had 4 nodes all running HSMM-Mesh. Today while installing some packages and doing some reconfiguring, one of the nodes locked up. The power light was flashing and the DMZ light was lit. I could not access it from the network. 

I was a able to boot into failsafe but when I tried to mount_root, it came back with the message "bus error". 

Is there a way to fix this or did the hardware fail?  I cannot find much online about this error. 

BTW, if you want, I have a couple dead wrt's that have perfectly good RP-TNC's that can be scarfed from (I have already grabbed some parts off them)

Or, you can always take the coax right to the PC board from an N connector in an enclosure or something. We have done that, removed the TNC's and wired straight to N's.

Truthfully, I think it depends on the model number of the hardware.

I have played with a number of them, and with most,  I cannot tell if there is a difference when I kick them left or right or diversity.

I think I found one where where I could actually tell the difference, so usually I just leave mine in diversity and let IT figure out the best jack to use.

Maybe the GL's do more or something, as I dont play with those much (I usually keep on the lookout for Gv2's so I can make more USB nodes, or GSv2 to make application nodes)

What I would do, to test, is have a known AP off as far as you can, then hook a directional ant to one port, and kick the setting back and forth, while looking at wifi scan. Maybe even rotate polarity as well (30db drop). Those of us without a VNA (analyzer) have to just shoot in the dark..

Sorry I couldnt help more, but that has been my experience over the last 3+ years.

73

KTF

Good to hear... seriously.  Since you're an Admin and responding, would you like to take a stab at the question I've posed 3 times so far without a response?  (I did get a response, but it was from someone scolding me for using LMR400 rather than Cat5... but ignoring the actual question). 

How do you test to see what antenna port is what?  I have a router with a bad RP-TNC jack I did a eBay "Make Offer" and got for a song.  I soldered a 47 ohm resistor on the broken jack side as a dummy load, then put enough LMR400 on the good RP-TNC to get a 12dBi panel antenna out of the shop so a wireless utility on a laptop wouldn't get signal from the dummy load.  I switched both TX and RX to Left, and then to Right in the firmware, but there was no difference in signal level.  Is the router going to send out a carrier to both antenna jacks no matter what, and only one have data on it?  Do I need to take another node out to see which setting actually passes data?
--
KJ4AJP

I took one of my nodes out of the OEM case and mounted it in a NEMA-4 (weather proof) enclosure. I removed the antenna mount that is wired across the PC board off of the board and mounted it in the bottom of the enclosure.  The other antenna fitting I left as is and left the OEM antenna on it.  The external antenna connector now has a YAGI antenna connected to it. The YAGI will be mounted on the mast above the enclousre, with the node inside. The node will be powered by POE with battery and solar panel.

My concern is temperature control inside the enclosure. Should I be concerned about the componets of the node overheating inside the small enclosure when it's closed up and mounted out in the sun ? The plastic OEM case was pretty well ventilated, but this new arrangement will not allow for any air flow inside the closed box.

Anyone else aleady been down this road and experianced any over heating issues with the node ?

Thanks,

Keith

KN5G

There are TWO ways for DMZ: NAT mode with a host IP in DMZ, and 1/5/13 DMZ-Host mode.

For NAT mode, If you have a host IP in the DMZ, it works like this :

If you add port forwarding to other machines on the LAN, those take priority over the DMZ.

Anything coming in, if there is a port-map for that port, that will take place;

If there is no port mapping (aka all other traffic), then it gets sent to the DMZ host.

Does that help?

KTF

K5KTF-50foot has been up on the push-up pole now for about 3 years, in the plastic Orbit box mind you, and has had no problems, running 14VDC up about 60' of regular cheap CAT5e (not even plenum rated) cable. Yes the sheathing may be starting to crack in places on the wire, but its still cooking.

I have taken it down for other things (webcam & other things), but the same board in the same box, and it even survived the 110*+(F)-for-80+days Central Texas drought of 2011 without a glitch.

-50foot is my longevity experiment... passing so far.

KTF

I have installed the tftp-hpa package and it works. However, if I enable the DMZ host in port forwarding, I can no longer access tftp from my workstation. 

What configuration keeps services like port 8080 and 2222, etc. bound to the mesh gateway and allows others to pass to the DMZ host?

Thanks in advance,

Jesse - WC3XS

Mine will remain unmodified, and the reasoning is that in the event mutual aid is needed, unless everyone involved in the deployment has spares for their modified equipment, there is no universal compatibility if a unit fails and needs quick replacement.  If my modified router goes out, Joe can't bring in his unmodified router to replace it. 

If one chooses to power their routers over the TP rather than a separate, larger gauge cable, then a box at each end like I originally proposed makes more sense.  The boxes are universal for either side, and with PowerPoles on both your PSU and a coaxial jumper for the router, you're set.  All you have to do is train an op on what the"Equipment" and "Cable" labels on the jacks mean.

Personally, I wouldn't do a permanent install of a $20 device designed for a indoor environment on a tower any higher than I could reach with a 10' stepladder.  I'd be spending the money on an amp and have my radios at ground level.  I realize we're Hams and experimenters and on a budget, but with all due respect to Titan Wireless and Fab Corp, take a look at how it's really done:

https://www.tessco.com/yts/systems_supported/base_station_infrastructure.html

--
KJ4AJP

wx5u -> Plugging one of our bootleg ethernet powered connectors into a "standard" gigabit ethernet device, it might cause damage.
<snip>
wx5u -> If your buddy Joe is working on your HSMM repeater site and decides to plug his laptop into your "ethernet" cable, you might damage something.

No, Joe might damage something.  Your FCC license gives you the leeway to experiment with your equipment, and if you're going to modify anything it stops being "plug and play".  So if you authorize Joe or anyone else to work on your system, you need to train them in any peculiarities of its installation and operation.  If they work on it without your authorization and training, then they take on the obligation of any smoke that gets out.

wx5u -> This is not "PoE" or "Power over Ethernet," which is a defined standard.  We should probably not use that term.

How about "Power over Ethernet Cabling" (POEC)?

Actually I like POTSAC (Power Over Too Small A Conductor). 

--
KJ4AJP