Broadband-Hamnet™ Forum
Welcome Guest   [Register]  [Login]
«StartPrev251252253254255256257258259260NextEnd»
 Subject :*** Rilasciato firmware BBHN 1.0.1 per Ubiquiti ***.. 2014-02-02- 22:17:14 
IZ5FSA
Member
Joined: 2013-02-23- 03:47:38
Posts: 13
Location: JN53OS
Forum : Italy
Topic : *** Rilasciato firmware BBHN 1.0.1 per Ubiquiti ***

La versione UBNT è ora disponibile. Sono supportati i seguenti dispositivi:
1) Rocket M2
2) Bullet M2 HP
3) AirGrid M2 HP
4) NanoStation Loco M2 (NSL-M2)
5) NanoStation M2 (NS-M2)

*** Note di Rilascio BBHN 1.0.1 per Ubiquiti ***

Vi preghiamo di tenere presenti le seguenti note quando operate sui dispositive e rilevate problemi.
Occorre tenere presente le seguenti distinzioni dovute  in gra parte alle differenze fisiche presenti fra i dispositivi Linksys e quelli Ubiquiti:

Descrizione Porte DMZ e LAN
Dal momento che i dispositivi Ubiquiti hanno una sola porta Ethernet, ogni dispositivo in sé supporta solo una connessione LAN cablata. Se volete connessioni LAN aggiuntive, allora avrete bisogno di aggiungere uno switch Ethernet esterno. La connessione allo switch può richiedere un cavo cross-over, piuttosto che un cavo standard patch.
Se avete bisogno della rete WAN, allora si rende necessario uno switch Ethernet esterno che supporti le VLAN – Virtual LAN (802.1Q). Tipicamente si tratta di un "managed switch" (1). Configurare le VLAN come segue:
     Untagged = LAN
     vlan1 = WAN
Nota: questa configurazione utilizza due porte, quindi se si vuole ottenere l'equivalente di ciò che il Linksys WRT54xx offre, allora avrete bisogno di uno switch a 6 porte. Verificare il supporto aggiuntivo per questa configurazione nel Forum di Supporto UBNT.

Operazioni fuori canale
I dispositivi Ubiquiti non cercano nodi BBHN su altri canali. Il canale configurato è l'unico sul quale opererà il dispositivo. Stiamo valutando le caratteristiche operative di Linksys per questa funzionalità e probabilmente le prossime versioni del firmware per Linksys si conformeeranno a questo comportamento.

Controllo limiti di banda
Dispositivi Linksys utilizzano lo standard 802.11g in cui i dati trasmessi sono contenuti all'interno di canalizzazioni a 22MHz. Tuttavia, se i dispositivi Ubiquiti limitrofi hanno collegamenti RF ad alta qualità, possono arrivare fino allo standard 802.11n. Questo standard opera all'interno di canali a larghezza di banda di 40MHz. Nella maggior parte dei casi questo non sarà un problema, perché le reti BBHN sono in genere configurate per la loro impostazione predefinita, ovvero il canale 1. Se si sceglie un canale diverso, quindi è necessario prestare attenzione al fine di garantire la permanenza del canale all'interno del proprio spettro operativo concesso n licenza licenza (2). Ad esempio, se si tratta di operare a 2.4GHz negli Stati Uniti ai sensi della FCC part 97, allora occore rimanere sui canali 1 o 2. Tutti i canali superiori possono causare il superamento della banda concessa all’uso di amatore.

Criptazione
Questi dispositivi possono essere configurati per permettere o vietare il traffico crittografato sul link RF. Spetta a voi decidere se l’uso della crittografia è appropriato in base a come verrà utilizzata la rete(2). Queste regole variano da Paese a Paese, così come la frequenza e la destinazione d'uso. Siete invitati a leggere e comprendere queste regole relativamente a dove operate.
Questi dispositivi sono pre-configurati con restrizioni per il tipo di dati passati e sono attualmente compatibili con il firmware BBHN Linksys serie WRT54G.

Vengono fornite apposite istruzioni se si vuole impedire il traffico crittografato sul link RF. Ciò include: SSL (443), SSH (22), Node SSH (2222), secure e-mail (465, 995, 993).
Il forum non ammetterà discussioni su quale di queste opzioni è appropriato per una determinata situazione. In definitiva l'operatore di controllo ha la responsabilità di tale scelta.

Potenza d’Uscita
I dispositivi Ubiquiti presentano livelli di uscita di potenza significativamente più elevati rispetto ai loro omologhi Linksys . Sulla base del modello e il guadagno dell'antenna, si può facilmente superare i limiti di potenza irradiata (EIRP) previsti dal 47 CFR Parte 15(2).
Crediamo che il controllo del livello di potenza fornito nell'interfaccia utente sia generalmente abbastanza preciso , anche se abbiamo ragione di credere che si può sopravvalutare il livello di potenza effettivo di ben 3 dB per i dispostivi NanoStation Loco M2. Saremmo grati a chi effettuerà una misura precisa e la invierà al forum.
La potenza dei dispositivi “a doppia antenna”, come il Rocket M2, quando configurati in modalità “diversity”, viene divisa fra le due antenne… causando un decremento di potenza di circa 3dB.
I livelli di potenza dipendono dalle antenne configurate. Si può notare che non è possibile impostare piena potenza massima del dispositivo quando si utilizza una sola antenna . Si può inoltre notare che non è possibile utilizzare il valore della potenza minima elencata nella tendina dell’interfaccia . Alcuni di questi dispositivi hanno amplificatori esterni al modulatore che per essere eccitati hanno bisogno di una potenza minima di gestione.

Dispositivi UBNT Testati e/o Non Supportati
Il rilascio richiede 32MB di memoria e 8 MB di Flash . Il tentativo di caricare questa versione in qualcosa su dispositivi con minori risorse creerà errori . Questo preclude in genere il supporto ai modelli più vecchi.
Ci sono due classi di dispositivi UBNT che non sono supportati :
Testato: Questi dispositivi possono funzionare con pochi o nessun problema . Tuttavia , non avendo avuto l'opportunità di testarli con questa versione, non forniremo il supporto tecnico fino a test avvenuti . Vedrete un “banner” sull’interfaccia grafica che indica questo stato . Si prega di non chiedere aiuto se non si è disposti a collaborare nel testare il dispositivo. Gestiremo questi dispositivi in un successivo rilascio, tempo permettendo. Nota : i dispositivi " Titanium" sono identificati internamente in maniera diversa dai loro “cugini non- titanio”, quindi per il momento anch’essi rientrano nella questa categoria non testati .
Supportato: Si tratta di dispositivi per i quali il software non è destinato. Possono caricare il software e può anche sembrare funzionare in qualche modo, ma non siamo disposti ad aggiungerli fino a quando abbiamo non ne avremo pianificato lo sviluppo per il supporto. Vedrete un “banner” sull'interfaccia grafica che indica che il dispositivo non è supportato.

Supporto
Siamo rimasti  tutti sorpresi da ciò che questi dispositivi possono fare e siamo sicuri che sarete entusiasti di costruire la rete a maglia con loro. Vi invitiamo a condividere i vostri successi, scrivendo le vostre esperienze nel forum.
Come regola generale, forniremo un sostegno prioritario ai progetti di realizzazione di una rete di "produzione", come quelli per EMergency COMMunication (EMCOMM). Per coloro che sperimenteranno questa tecnologia o che creeranno una rete in ambiente di laboratorio, chiediamo la vostra pazienza. Riconosciamo l’interesse intorno a questa versione e speriamo di poter fornire un sufficiente livello di supporto per coloro che ne hanno più bisogno.


Detto questo, abbiamo un gruppo esperto di test che ci ha aiutato nel rilascio di questa versione:

    Andrew, KF7JOZ
    Clint, AE5CA
    Doug, W1DUG
    Garry, KD2DDK
    Gordon, W2TTT
    Karl, W2KBF
    Leo, IZ5FSA
    Mark, KD5RXT
    Randy, WU2S
    Richard, W2LCN

Ci aiuteranno a dare risposte alle vostre domande e risolvere i problemi. Quando come utilizzatori avrete realizzato la vostra esperienza con questi nuovi dispositivi, vi invitiamo a partecipare e sostenere i nuovi utilizzatori meno esperti.

73,

Il Team di Sviluppo BBHN


_______________________________________________
Note:
(1) come ad esempio i Mikrotik RBxxx oppure l’economico Netgear GS105e
(2) specifica tecnica per regole FCC (Nord America). Conformarsi a quanto disposto dal proprio Paese.

IP Logged

73 de Leo IZ5FSA
 Subject :Re:Re:Re:HSMM-MESH in Utah.. 2014-02-02- 17:32:36 
AF7J
Member
Joined: 2013-10-08- 10:00:30
Posts: 8
Location: Ogden Utah
 
Forum : Utah
Topic : HSMM-MESH in Utah

Team Talk on mesh node Hi tonight while the super bowl was going I decide to turn on my two nodes and install Team Talk Client server on my Laptop connected to one node. I then had a client on another laptop connected to another node. Team Talk allows you to do a lot. voice and text chat and video. and file sharing. my OS on client-server was windows 7 pro. and the other laptop has windows 7 home premium. the server needed the firewall opened and then I was able to connect the two via ip address. I need to know can I set up a welcome page so hams can conect to my Team Talk server??? Thks 73 AF7J
IP Logged
 Subject :Re:How do you connect two or more co-located nodes via Ethernet cable.. 2014-02-02- 14:52:48 
KJ6ACE
Member
Joined: 2013-12-14- 16:27:01
Posts: 8
Location
Forum : Firmware
Topic : How do you connect two or more co-located nodes via Ethernet cable

Conrad, Thanks for the reply. With what you have stated you are already thinking ahead as well. The only solution that I think I can do right now is turn off the DHCP on all of the nodes and the router, then make a routing table in the WRT54G which can't be used for a node, and see if that works.
IP Logged
 Subject :K5KTF - More info on iCruze display to Node?.. 2014-02-02- 13:38:38 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Forum : Hardware
Topic : K5KTF - More info on iCruze display to Node?

Hey Jim!


Do you have more information on how you integrated the iCruze display to your node?  Namely pinout, etc.


Thanks!!


IP Logged
Last Edited On: 2014-02-04- 17:25:24 By W5LMM for the Reason
 Subject :Re:Water tight enclosures.. 2014-02-02- 12:55:12 
KE7ZOE
Member
Joined: 2014-02-01- 14:52:00
Posts: 1
Location
Forum : Hardware
Topic : Water tight enclosures

I know that many hams use the sprinkler control boxes from Home depot or pelican/otterbox cases. That's what I am planning on using for this and an external HF tuner.
IP Logged
Is this thing on?
 Subject :Re:Ubiquiti Rocket M3.. 2014-02-02- 10:51:03 
ZL1WTT
Member
Joined: 2014-01-29- 00:41:50
Posts: 2
Location: Auckland
 
Forum : UBNT Firmware
Topic : Ubiquiti Rocket M3

Hi again, I was talking Robert ZL1FLY today about the M3 units, there is another thing that needs to be worked out. This is common microwave band plans world wide, this is the same for the Mesh networks as ATV/DATV as both are wide band modes. It's important that manufactures have international market available for their equipment. This way data products can be made to be plug and play for Ham radio. Maybe this should be another topic in it's self?
IP Logged
 Subject :Re:Why is WiFi defaulting to Channel 1?.. 2014-02-02- 08:16:28 
af5fh
Member
Joined: 2014-01-31- 23:50:02
Posts: 2
Location
Forum : General
Topic : Why is WiFi defaulting to Channel 1?

Thanks! After I read your response, I searched online and found a picture showing what you said on Wikipedia. Jim, AF5FH
IP Logged
 Subject :Re:Why is WiFi defaulting to Channel 1?.. 2014-02-02- 06:46:30 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location
Forum : General
Topic : Why is WiFi defaulting to Channel 1?

Channel 1 has been the standards for some time now, it was a common channel used by hams prior to the mesh firmware.

On 802.11g networks in the US you have only 3 channels that don't overlap (1,6,11). Every other channel will cause at least some overlap so 1,6,11 have been common use.

802.11n uses double the "channel" sizes so to stay in the ham band and not overlap with any other channel you really only have channel 1@ 2402-2442 MHz).

This means to have the best chance of talking to another mesh node channel 1 is the sensible default.

Yes there are other devices in this area, but as hams we can run higher gain antennas (higher EIRP) to have an advantage on signals.


IP Logged
Last Edited On: 2014-02-02- 08:52:06 By KG6JEI for the Reason Correct non overlapping channel list
Note: Most posts submitted from iPhone
 Subject :Why is WiFi defaulting to Channel 1?.. 2014-02-02- 06:15:13 
af5fh
Member
Joined: 2014-01-31- 23:50:02
Posts: 2
Location
Forum : General
Topic : Why is WiFi defaulting to Channel 1?

I am new user, just loaded firmware onto WRT54G rev. 2 that I purchased used. Seems to work fine, thanks to everyone's hard work to provide this!

Where I live (Albuquerque) the local phone company offers DSL internet, and their wireless access point appears to default to Wifi Channel 1. When I click WiFi scan on my node, I see many signals on Channel 1. Channels 2, 3, and 4 are empty, and 5 and 6 have sometimes one signal each. Is my location unique, or do others see lots of signals on Channel 1?

Jim, AF5FH

IP Logged
 Subject :Re:Ubiquiti Rocket M3.. 2014-02-02- 02:33:13 
KD7RYY
Member
Joined: 2011-10-27- 10:48:43
Posts: 21
Location: Vancouver, WA CN85rq
Forum : UBNT Firmware
Topic : Ubiquiti Rocket M3

Excellent, as I have a couple of PicoStation5's here to use.
IP Logged
 Subject :Re:How do you connect two or more co-located nodes via Ethernet cable.. 2014-02-01- 20:28:57 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location
Forum : Firmware
Topic : How do you connect two or more co-located nodes via Ethernet cable

Happy to see the forward thinking.

I know this answer doesn't solve the need for performing this 'right now today' but want to give a bit of the road map.

A standardized protocol for device to device linking is currently being looked into, preferably with the intent of allowing it to be "plug the nodes together and be done" (if possible) in order to keep with the simple setup nature.

This was always expected to be an item to need to be addressed with Ubiquiti gear only having 1 physical port and some devices only have 1 antenna port, or no external RF feeds (Bullets or NanoStations for example).

The goal of the initial UBNT release (1.0.1) was to maintain as much the same to being with (as possible) and start adding features as we go down the road.

Some thoughts and configurations have already been bounced around on the subject and are going through various stages of testing an analysis to be sure they are the best way.

I would suggest looking for a much easier method on the Ubiquiti build in the next release, and the linksys build to follow it as well.

Best Regards,
Conrad Lara
KG6JEI

IP Logged
Note: Most posts submitted from iPhone
 Subject :Re:V1.0.0 and moving data across the mesh.. 2014-02-01- 17:29:44 
KF5JIM
Future Astronaut
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland
Forum : Firmware
Topic : V1.0.0 and moving data across the mesh

Maybe this will get you pointed in the right direction? http://kb.iu.edu/data/ahrs.html

IP Logged
My opinions and views expressed here are solely my own.
 Subject :Re:V1.0.0 and moving data across the mesh.. 2014-02-01- 17:15:18 
N6SXR
Member
Joined: 2012-07-30- 08:05:31
Posts: 35
Location: Stormy Acres
Forum : Firmware
Topic : V1.0.0 and moving data across the mesh

I see said the blind man.  I'm still not able to get to a shared drive on another confuser so there is some other things that need to be set.  I will keep trying.


Kirk - N6SXR

IP Logged
 Subject :Re:Questions.. 2014-02-01- 14:32:58 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location
Forum : UBNT Firmware
Topic : Questions

Correct, the Bullet only has one port. The GS105 will not let you 'pull out' the other vlans... The GS105E (note the E, its what NetGear is calling an "Unmanaged Plus" switch ) will. NOTE: You only need a 'managed' switch to 'pull out the vlans' if you intend to use your node to provide internet (Mesh GW), or need it to 'connect to the internet' directly (download firmware, and packages, however you can upload those from your computer w/o internet on the package screen so internet is NOT required for this). If you are using it solely for a end node connected to local computers and not connecting to the internet or acting as a MESH GW than you do NOT need a smart switch and any switch you can find should work. As for the NanoSation M2, the 2nd port didn't make it into the release, It is there, its available to be used, but what to use it for hasn't been figured out yet.
IP Logged
Note: Most posts submitted from iPhone
 Subject :Re:Questions.. 2014-02-01- 14:31:14 
AE5CA
Member
Joined: 2012-05-19- 21:52:33
Posts: 81
Location
Forum : UBNT Firmware
Topic : Questions

K2VKJ I helped with the Beta Testing and I have used successfully with the Ubiquiti nodes is a 5 port GS105E. The GS108E is a similar switch with 8 ports that another member of the beta team used. Both support VLAN. With VLAN, one port can be set up to be your WAN port and the remaining ports function just like the lan ports on a WRT54G. If all you want to do is connect multiple computers to the node without a WAN port (internet connections) then any dumb switch should work. Connecting Ubiquiti nodes back to back through the switch has been discussed as a future upgrade but I don't think it make it into the initial release. My nodes connect just fine through the wireless side where I have them installed. Clint
IP Logged
 Subject :Re:Questions.. 2014-02-01- 14:02:43 
n2vqm
Member
Joined: 2014-01-10- 23:37:42
Posts: 3
Location: Reston, Virginia
  
Forum : UBNT Firmware
Topic : Questions

The UBNT Bullet only has one ethernet port, so (as I understand it), if you wanted two physical networks (LAN / WAN) then you'd need a "managed switch" and assign some VLANS.

If you only want one network (presumably LAN) then I can't think of any reason why an ordinary 10/100 ethernet switch wouldn't work for you. 

I'm curious though, because I see the firmware for Nanostation M2, and it does indeed have two ports.  However the documentation for the HSMM firmware seems to indicate that ALL UBNT devices have only one port.  So I'm wondering, if maybe HSMM won't support the second port, or (insert unknown quantity here).

 

IP Logged
Last Edited On: 2014-02-01- 14:04:27 By n2vqm for the Reason
Often implicated, but never duplicated!
 Subject :Re:Questions.. 2014-02-01- 13:46:02 
k2vjk
Member
Joined: 2013-11-25- 10:55:46
Posts: 15
Location
Forum : UBNT Firmware
Topic : Questions

2 Bullets coming. Would an unmanaged switch like a Netgear GS105 work for a switch? If so, I'm rearing to go!!
IP Logged
 Subject :Re:dual antennas, questions or ideas.. 2014-02-01- 12:28:24 
KF7MCF
Member
Joined: 2013-02-09- 08:16:21
Posts: 3
Location
Forum : How we used HSMM-MESH™
Topic : dual antennas, questions or ideas

No, that will usuall not work well.. (two antennas of different types, one on each of the antenna jacks of a WRT54G at the same time) The WRT54G has a basic diversity antenna system - The unit is looking for the same signal (from the same target node)on each of the antennas. It will then choose and utilize the best signal from the source it is listening to on the strongest antenna connection. The two antenna connections can be used well in the dual antenna software mode with a dual polarity antenna (one with vertical polarity, and one with Horizontal phase tilt of 45 to 90 degrees) or distance offset dual antennas to greatly improve reception when experiancing phase problems. Phase flipping or distortion is usally caused by reflections in the Fresnel Zone, manifested by the receive signal level bounceing up and down. That is why the WRT54G comes with two antennas in its stock mode. An easy mistake to make is to assume that you can use two antenna types, for instance Omni and directional, putting one of each type on the two antenna inputs of the WRT54G. The unit can only listen on one of the antennas at at time, comparing the two, and then choosing the best signal from the target site to use. It can switch continuously back and forth very quickly, utilizeing the best signal from the target unit. The problem with using a gain directional, and a lower gain omni is that unless it sees the same target site on both antennas at the same time to compare which is best, it will not work in dual antenna mode properly. Most often, the high gain directional antenna will see signals it is pointed at that the lower gain omni can not even pick up, and the lower gain omni will see signals out of the beam width of the directional that the directional antenna can not see either, not allowing the software to compare the signals out of both antennas to choose the best one at each instant in time. Using two gain antennas aimed in two directions with a coupler on one antenna port (jack) would work but there are down sides to that, also. Comercial installs use that often with multiple sector antennas to beam a signal in specific areas, but remember, signal level is split between the two or three antennas used, and noise and competing signals will be picked up in the added directions. Hope that helps... David T. Bauman KF7MCF Magna Utah Bishop's Storehouse Emergency Response Communications
IP Logged
 Subject :Re:Ubiquiti Rocket M3.. 2014-02-01- 12:22:52 
zl1fly
Member
Joined: 2013-01-07- 02:07:04
Posts: 12
Location
 
Forum : UBNT Firmware
Topic : Ubiquiti Rocket M3

That is excellent news. Currently we are planning on using the 3.3Ghz freq as a backbone pipe. Potential three high sites. From there mesh members will be able to downlink at 3.3Ghz to a local mesh and then spread out locally on 2.4Ghz or 5.8Ghz. So the 3.3Ghz will be reserved for interconnecting local suburbs. The other freq's will be for general mesh use.
IP Logged
 Subject :Re:WRT54G or WRT54GS is the extra expense worth it?.. 2014-02-01- 12:05:05 
n7ego
Member
Joined: 2013-03-06- 21:51:50
Posts: 30
Location: Cedar Hills, UT
Forum : General
Topic : WRT54G or WRT54GS is the extra expense worth it?

The main reason you might want the additional memory is if you want to run additional software/services directly on the mesh node itself in addition to the BBHN software. For example, some people are running Asterisk servers or various chat servers on the mesh nodes. But most of us find it easier to run these kinds of things on computers attached to the mesh network instead of on the mesh nodes themselves. In that configuration you don't really need the additional memory.
IP Logged
Page #  «StartPrev251252253254255256257258259260NextEnd»


Powered by ccBoard


SPONSORED AD: