Big antennas, small elements!
Em 1 de jul de 2017 9:10 PM, "Nicolás Echániz" <nicoechaniz(a)altermundi.net>
escreveu:
thanks foe the pics
if you can send an image of the antenna internals, we can see if it is a
known dual band model.
I'm thinking we can use ufl pigtails, like these :
https://www.data-alliance.net/u-fl-extension-cable-18-inch-
20-in-22-in-2ft-28-in-30-in-3ft-42-inch-u-fl-male-to-u-fl-female/
... to be able to use these antennas the way we use those provided with the
3500/3600 models.
On July 1, 2017 7:11:42 PM GMT-03:00, bruno vianna <bruno(a)pobox.com> wrote:
>
>
>
>>
>> Bruno, can you send pictures of this router without it's cover?
>> I'd like to see how the antennas are connected to the board.
>>
>> Also, do you know if the antennas are bi-band or the 2.4Ghz antenna is
>> inside the router like in other models?
>>
>>
>>
>
> Here they are. It looks like both antennas are connected to both chips
> (there is a track in the other side of the board connecting the antenna on
> the left to the MT7620 chip).
>
> Is there anyway I can test this?
>
>
>
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi all,
my plan is to setup multiple LiMe routers in the house I live in to
connected me and my neighbors.
For testing I setup only two nodes and face the first problem: The
gateway router works just fine, resolving DNS requests. The "client"
router, connected via Ethernet to the gateway router routes all IP
traffic correctly but does not handle DNS requests at all.
I'm using a wdr4300 as gateway and a wr841 as client, using flavor
lime_default and lime_mini. The configuration is below.
config lime system
option hostname 'ZE-%M4%M5%M6'
option domain 'ze.lan'
option keep_on_upgrade 'libremesh base-files-essential
/etc/sysupgrade.conf'
config lime network
option primary_interface eth0
option main_ipv4_address '10.%N1.%N2.0/25'
option main_ipv6_address 'fc23:4237:3407:%N1%N2::/64'
option bmx6_mtu '1500'
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list protocols olsr:14
list protocols olsr6:15
list protocols olsr2:16
list resolvers 8.8.8.8 # b.resolvers.Level3.net
list resolvers 141.1.1.1 # cns1.cw.net
option bmx6_over_batman false
option bmx6_pref_gw none
option bmx7_over_batman false
option anygw_mac "aa:aa:aa:%N1:%N2:aa"
config lime wifi
option channel_2ghz '11'
option channel_5ghz '48'
option htmode_5ghz 'HT40'
list modes 'ap'
option ap_ssid 'ze net'
option ap_key 'password'
option ap_encryption 'psk2'
Currently I'm not intending to use any Wifi Mesh functionality, only via
Ethernet, enabling roaming within the house.
Thanks for all comments!
Best,
Paul
Hi all
I’ve noticed LEDE supports 802.11r and 802.11w and has the respective settings section in LUCI under wireless security. I’m not familiar with these protocols other than knowing they exist and I’m very happy to see them available for use with free and open software. Is there any way we could start some testing for them for LiMe [especially the first one, which would make roaming inside the network even more seamless, since it’s one of the core advantages and of LiMe]? I read that 802.11r requires only one DHCP server to exist on the network and no separate subnets, but I assume that our replication of such a network with every node handing out the same leases on the same subnet perfectly simulates this behavior even in this respect, and the “trickery” works also for this requirement, is this correct?
Also, is there a good rule of thumb to figure out the right way of enabling features available in LuCi from the LiMe configuration in SDK? I’ve been trying to put all nodes on SSH port 42022 [I know, security by obscurity, but it’s better than nothing, and our keys are 4096, so there’s a solid base already ;] and disable password authentication for instance. Or adding hostnames, and so on. If there’s a quick way of figuring these things out, I won’t have to bother any of you for every single customization I need to make ;]
Thank you in advance
Nk
Hi,
Ultimately, I would like to get rid of the double SSID broadcasting, and have only our mesh network name as SSID no matter what nodes.
I see how to do that from Luci or the config. But then I'm not sure how I would acces a particular node Luci UI.
What am I missing?
Thanks,
Antoine
Hi,
I just added some detail to a open issue for luci:
https://github.com/openwrt/luci/issues/1192
Basically I cannot set a password on a fresh 17.01.02 install for mini. normal disbrib works fine.
Do you have any workaround for that issue?
Thanks!
Antoine
Hi
In order to understand how to start using 802.11s from SDK, I’ve downloaded a pre-built image from http://repo.libremesh.org/lime-17.04/ [downloads.libremesh.org isn’t responding at least for me - I think I need a 17.02 version to compare with an SDK output, no?].
I’ve noticed a few changes such as the directory /etc/config/ becoming /etc/lime-config-firstboot/ and more in luci-defaults and so on.
Do you have a list of changes?
How do I maintain a https://github.com/libremesh/network-profiles/ community in a way that is future-consistent?
I’d like to be able to have details in there that really only override things I’ll always want to override, such as the SSID, but allow for all other file changes [like adhoc becoming 802.11s for instance] from upstream to pour down into my SDK images, with no interference at all and no risk of having conflicts. Also because images I’m building now, once flashed, don’t work at all, so there is a big risk in upstream changes conflicting with network-profiles, don’t you think?
I know this means a line-based granularity and not a file-based one such as now, but there must be a way, no?
In any event, for now, what changes do I have to make to my community files in order to get SDK to cook valid and up-to-date in every way images?
Thank you!
Nk
