From: Sven Eckelmann <sven@narfation.org>
To: Oguzhan Kayhan <oguzhan@kayhan.name.tr>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: configuration issue
Date: Tue, 28 Apr 2020 11:51:38 +0200 [thread overview]
Message-ID: <9817716.HyuBmzvnZK@bentobox> (raw)
In-Reply-To: <CANKYHpcYxPD1tF4EB2hFT891X=FwqiRbo3xCTofxSgdteqES6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2556 bytes --]
On Tuesday, 28 April 2020 11:28:25 CEST Oguzhan Kayhan wrote:
[...]
> Now my config is as follows on both wifi nodes
>
> wireless:
> config wifi-iface 'wmesh'
> option device 'radio0'
> option ifname 'mesh0'
> option mode 'mesh'
> option mesh_id 'test'
> option mesh_fwding '0'
> option mesh_ttl '1'
> option mcast_rate '18000'
> option encryption 'none'
[...]
> Now here comes the second part..
> How can I make the encryption over mesh?
This is not an Gateworks OpenWrt 18.x support mailing list btw.
And the OpenWrt documentation [1,2] explains how to do this.
Anyway, you can enable it on OpenWrt by selecting wpad-mesh-openssl (or
wpad-mesh on older OpenWrt versions). and then using something like:
config wifi-iface 'wmesh'
option device 'radio0'
option ifname 'mesh0'
option mode 'mesh'
option mesh_id 'test'
option mesh_fwding '0'
option mesh_ttl '1'
option mcast_rate '18000'
option encryption 'psk2+ccmp'
option key 'thisisaverysecretkey'
But as said earlier, the gateworks OpenWrt 18.x is in rather bad shape. So
expect that there are a lot of important fixes [3,4,5,6,7,8,9,10,11,12,13,..]
missing.
Kind regards,
Sven
[1] https://openwrt.org/docs/guide-user/network/wifi/mesh/batman
[2] https://openwrt.org/docs/guide-user/network/wifi/mesh/80211s
[3] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=166741240afd396c41b284edaa5180b162232741
[4] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8f24653184536e1f8259bb43cffdae5673fb593a
[5] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=eba3b028e46dbfe54f1208e9edf47bb0c6f73ac8
[6] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ff8df2b3f9c161edc3ab543bdbeb04a9fb45c959
[7] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=a4322eba2b129adde45e3f7ac6c3805889623dd5
[8] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=3a456683e5da7ed3a26ffb71e1dbbf1d1db0d036
[9] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=6e0fa4a76db667d7f0c1d84a3af5017df26d3fad
[10] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=574e4377fad5137595dea8a281061a3c945187c2
[11] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=547042398afac3ce702adab28c753e7c9ebed452
[12] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ba5ec6b77c94a21bbd78b66c63317a4ff9b62962
[13] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=96f4792fdb036ecf5c8417fce6503412b0b27e5f
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-28 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 12:26 configuration issue Oguzhan Kayhan
2020-04-27 15:27 ` Sven Eckelmann
[not found] ` <CANKYHpe_cG=dKv5z4tecjb24U_P2ipWoQPownNCxKySU_FozQw@mail.gmail.com>
2020-04-27 17:19 ` Sven Eckelmann
[not found] ` <CANKYHpcZU09emNFy3yf4K0F5s8gzT6giosqfCDNj278f6Z3_mQ@mail.gmail.com>
2020-04-28 9:28 ` Oguzhan Kayhan
2020-04-28 9:51 ` Sven Eckelmann [this message]
2020-04-28 10:36 ` Oguzhan Kayhan
2020-04-28 11:17 ` Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9817716.HyuBmzvnZK@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=oguzhan@kayhan.name.tr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox