Well naturally it was an operator error,   and I apologize for posting..    I was using hssm instead of hsmm

Appears to be working now..   sometimes the smallest of errors make a BIG difference..

All OK at present

2nd node

update appears to take effect, but (root/hssm) or original (login/pw) no work, this is 2nd node have tried so far..   same thing..

#1 was a WRT54GL

#2 was a WRT54GS

Once update is applied, get redirected to device, but no login / password that I have tried so far appears to be working..

These were working nodes and applied the update,  top of software download list for Linksys working nodes..  All appeared to be working and normal, before applying update..

Thanks.

I'm designing a mesh network for our county and i wish to thank the developers for the updates including the 5ghz to the mesh topology I'm wanting to use the 5ghz as a back haul for the mesh and have 2.4ghz for mobile and portable access some say use switch non configure and some say use configure witch is the best way to go and can you manage the switch on the mesh if you have the user configure the switch.

The node should revert to all default after loading (root/hsmm) and will be avaliable at http://localnode:8080/

You should be able to see the status page showing 1.1.0 as well.

if not chdxk to make sure your PC has obtained a new dhcp lease after uploading the firmware (the node will revert to initial configuration mode )

After updating with file for existing firmware, not able to log in with (used to be working login/password)

tried several that upload instructions mention, but no luck so far.  Appears the update was accepted, but made where not able to log in with original password, or default password..

thanks.

Hi N6HTV Here in Sacramento.

Looking to meet with someone in the area to talk about mesh,voip,solar,R-Pi, aurduino,etc..

916 740-6842

Are we having an HF net or meeting anytime soon?

N6HTV Lincoln Ca

"The Internet standards (Request for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. However, a subsequent specification (RFC 1123) permitted hostname labels to start with digits. No other symbols, punctuation characters, or white space are permitted."

--- http://en.m.wikipedia.org/wiki/Hostname

This means that the name chosen can not have an underscore and be valid. This actually sounds like a bug in your operating system in letting you choose a name with an underscore and sending it out in the DHCP request. 

The BBHN WebUI properly refused to let you register this invalid name and that is where the message came from.

Howdy,

So during field day I set up a mesh network to network all our computers and loggers together. During this period one of the computers was having trouble. I was using a wrt54g with the latest firmware, and the router couldn't see this computer. I was trying to give it a static ip address but it would partially show up or not at all. For some reason when I tried to add a dhcp reservation, it told me something about the name being invalid. The hostname on the computer was DELL_DUAL_CORE or something to that affect but the firmware didn't like it. After changing the name of the PC the router had no problems seeing the PC and adding the dhcp reservation. 

Thanks,
KK4URZ 

I've just ordered a couple of Ubiquity and WRT54GL devices to start playing around. Keen to get started.

While searching about hsmm-mesh online I've come across other mesh technologies, such as qmp, batman, cjdns, etc.

QMP for example is what's used in Guifi.net.  QMP is not an amateur specific technology, but it's been rolled out in Spain for thousands of nodes. They might be running low EIRP - but the network can support a LOT of nodes and traffic.

In comparison - would hsmm-mesh be up to the challenge if we were to run hundreds of nodes together?

I'm keen to learn how the 2 technologies compare.

For starters I'm working on an AREC (aka ARES in New Zealand) solution where it wouldnt really matter - but as time goes on and more networks were linked (say even over VPN to the US or otherplace) I'd like to learn if there will be any bottlenecks.

Thanks.

Hello,

I recently got a DL435-30 from doodle labs...

http://www.doodlelabs.com/products/radio-transceivers/sub-ghz-range/420-450-mhz-dl435-30/

It is an interesting toy that does everything you can do with 802.11 standard but on 420-430 Mhz band... It works with openwrt..

I had worked after reading and following instructions provided by David Bern (W2LNX).

http://www.tapr.org/pdf/DCC2012-Experimenting-...-Wireless-Networking-in-420-MHz-Band-W2LNX.pdf

I used two DL435-30 on both sites with partial line of sight. The two sites were 12 miles away from each other... 

I successfully established a strong link between these two sites.

I used two M2 420 MHZ Yagi antennas..

http://www.dxengineering.com/parts/msq-4205011

I'm looking for a bigger antenna more powerful than the yagi for a base station...

Can you guys help with finding the right antenna ?

Thanks

This sounds like a switch configuration issue not routing the vlan you have configured or not in tagging it later.

Your internet needs to be connected to the same vlan as what's used for the mesh node (default of 1)

http://www.hp.com/rnd/support/config_examples/primary_vlan.pdf

you can change the primary vlan on the switch.

it boils down to (by default which you have changed)

tagged vlan 1 out of Ubiquit node = wan

You need to untag it and treat it as the parent vlan on the port you connect to your access network.

im not an expert at procure switches but I would assume the easiest setup should be leave parent vlan the same across the board and primary vlan,  set the switch to expect vlan 1 to be tagged on the port with the Ubiquiti node and add a 2nd vlan (such as 10) as in tagged on that same port to be used for local users. 

Hello everyone.  I am trying to setup a Rocket M2 to act as an internet gateway.    I have run across the article that talks about the need for setting up a managed switch to split off the single ethernet port on the M2 using VLANS.  I have the common port set to tagged on my vlan for WAN.  It is eth0.3 on the M2 (1 is the default vlan on the Procurve I have so I found how to change it to 3).  The port on the switch to connect to the internet source is tagged on vlan 3, no tagging on any other vlan.  The LAN port eth0 is untagged on the default VLAN (1).  

In sanity testing I have verified that I can get an IP address from the rocket on my default vlan and not from my internet source.  This leads me to believe the vlan config is correct.

I am not having luck on the WAN port though.  It is on VLAN 3.  I have tried to let DHCP issue it an IP address.  I never see it send the request to the DHCP server.  I have verified this by tailing the syslog on my dhcp server and port monitor the port on the switch.  I have tried manually assigning the WAN port an IP address on the same subnet as the internet source.  I can not ping the gateway address.  Watching the monitor port does not show the pings going out the port.  This leads me to believe that the M2 is not using eth0.3.  When manually assigned, I do show the default GW to be my gateway to the internet source.

Other documentation I found on the forum says to disable WAN, put LAN on the same subnet as the internet source, set the default gateway, disable the DHCP server, check the gateway box (that is in the WAN section), and reboot. The documentation does not say anything about vlans.   I tried that earlier and had no luck.

First question,  am I going down the totally wrong path here or do I have something setup wrong on the M2?

The Denton County Amateur Radio Club is starting on MESH as a project and internet access is a starting point.  I will be adding a proxy server later to deal with content issues.

73 and thank you,

Guy

KC5GOI

KJ6DZB,

It might be better if you start a new thread rather than reviving older resolved threads.

This would allow you to not need to post the same message in multiple forums and will also allow users to find your post easier.

Update...... Im looking to lay the ground work to allow a user to set the VLAN-ID "???", in the mean time im looking for the config file... If the Dev team has interest in creating a Gui for it? Q:were is the 8021q trunking config at in /? and what Lib is being used? I dont see kmod-8021q in the package list http://www.broadband-hamnet.org/download/backfire/10.03.1/ar71xx/packages/Packag es.gz. So? kmod macvlan looks interesting...

Im just not seeing how 8021q aka Stacked VLANs 802.1ad is being configured.  

http://wiki.openwrt.org/doc/networking/network.interfaces

Ron,

Maybe this is why its not advertized like the IRC server: I noticed when reading about "Operating in Direct Mode" that when a DHCP reservation is made (which it was for the FTP server, but wasn't for IRC server),...it states,

"when the LAN is operating in Direct mode...the mesh works a little differently [than NAT mode].  Since in Direct mode the LAN hosts are accessed directly from the mesh and no port forwarding is involved, the advertized services are based upon which LAN host exists, and this is determined by the DHCP addresses defined. AFTER THE DHCP RESERVATIONS HAVE BEEN MADE SERVICES CAN BE OFFERED IN THE SAME WAY AS BEFORE WITH THE ADDITIONAL REQUIREMENT OF SELECTING THE NAME OF THE HOST THAT IS PROVIDING THE SERVICE."  (emphasis added).

That said, I have to select the name of the host which is provide the service, which is W4LLZ-N1, and access the service that way versus selecting the service itself which is seen and advertized on the remote node.

I think that's why its not showing up.

Well, as far as "what's next"...so far I've managed to get 17 nodes installed with the hamnet software and distributed to our ARES group. I've managed to get video/audio set up on the mesh for EmComm as well as IRC w/ mIRC which does file sharing as well (but I wanted to have numerous files available to the group - thus, the FTP service), and set up one node as a mesh gateway to the internet. What's next is, trying to get the rest of the group to buy their antenna's! I've got a couple 2.4 ghz antennas and have done some demos for them but their a bit slow and crusty. Ultimately, we want to demo the system to our county officials and try get permission to get some antennas put up on county buildings for city wide mesh availability. Thanks for the help, I really appreciate it (cause I have zero experience with networking) but have managed to get what our ARES group needed to function on the mesh.