no data over mesh #50

chaosenze · 2016-07-25T22:29:01Z

2 Accesspoints 1 arch linux with aseauth package(mesh0) and 1 openwrt 15(mesh1)

meshpint0:

iw mesh0 station dump

Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 76 ms
rx bytes: 4200719
rx packets: 55032
tx bytes: 594
tx packets: 4
tx retries: 0
tx failed: 0
rx drop misc: 1437
signal: -49 [-66, -49] dBm
signal avg: -50 [-62, -50] dBm
Toffset: 18446744019042612758 us
tx bitrate: 1.0 MBit/s
rx bitrate: 1.0 MBit/s
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: UNKNOWN
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:1000
connected time: 2777 seconds

meshpoint1:
%iw mesh0 station dump
Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 76 ms
rx bytes: 4200719
rx packets: 55032
tx bytes: 594
tx packets: 4
tx retries: 0
tx failed: 0
rx drop misc: 1437
signal: -49 [-66, -49] dBm
signal avg: -50 [-62, -50] dBm
Toffset: 18446744019042612758 us
tx bitrate: 1.0 MBit/s
rx bitrate: 1.0 MBit/s
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: UNKNOWN
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:1000
connected time: 2777 seconds

both ecome ip adresses 10.0.0.1 and 10.0.0.2 bit no ping is possible.

The connection is established but no data trafic is possible over this mash connection. I don't know why? I'm confused about mesh peer PS mode status. sometimes is on one node ACTIVE but not on both side...

my config mesh 0:

cat /etc/authsae.cfg

/* this is a comment */
authsae:
{
sae:
{
debug = 480;
password = "TESTZPW";
group = [19, 26, 21, 25, 20];
blacklist = 5;
thresh = 5;
lifetime = 3600;
};
meshd:
{
meshid = "testmesh";
interface = "mesh0";
band = "11g";
debug = 1;
};
};

starting meshpoint in bash:
iw phy0 interface add mesh0 type mp
iw mesh0 set channel 3
ip link set dev mesh0 address 04:f0:21:14:c9:34
ifconfig mesh0 up
/sbin/meshd-nl80211 -c /etc/authsae.cfg -i mesh0 -B

config (openwrt) mesh1:

cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option path 'platform/ath9k'
option htmode 'HT20'
option txpower '17'
option country 'DE'
option channel '3'

config wifi-iface
option ifname 'mesh0'
option device 'radio0'
option network 'mesh'
option mode 'mesh'
option mesh_id 'dmesh'
option encryption 'psk2+aes'
option key 'TESTZPW'
option macaddr '00:23:EB:2C:FC:42'
option debug '1'

both mesh side-interfaces have an valid ipv4 adress but ping is not possible.

please contact me for further informations.

mporsch · 2016-07-26T20:57:54Z

Hi,

could you give it a try without the encryption?

mesh peer PS mode: UNKNOWN
The mesh peer power save mode is determined on the first receipt of a QoS data frame.
Beforehand the non-peer power save mode is assumed
mesh non-peer PS mode: ACTIVE
which is ok.

option hwmode '11g'
option htmode 'HT20'
And are you sure this setting is valid?

This is weird as well:

mesh llid: 0
mesh plid: 0

Are the kernel versions you are using on both machines similar?

--Marco

chaosenze · 2016-07-27T07:05:13Z

Hi Marco,

without encryption it works fine.

mesh0 (arch linux: kernel 4.6.4-1-ARCH) without config file, my commands are:
% iw phy phy0 interface add mesh0 type mesh mesh_id dmesh
% ip link set dev mesh0 address 04:f0:21:14:c9:42
% iw dev mesh0 set channel 3
% ifconfig mesh0 10.0.0.2 up

% iw mesh0 station dump
Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 56 ms
rx bytes: 910260
rx packets: 13891
tx bytes: 783
tx packets: 10
tx retries: 0
tx failed: 0
rx drop misc: 45
signal: -56 [-65, -57] dBm
signal avg: -57 [-65, -57] dBm
Toffset: 18446743962739979724 us
tx bitrate: 78.0 MBit/s MCS 12
rx bitrate: 18.0 MBit/s
expected throughput: 43.303Mbps
mesh llid: 17217
mesh plid: 286
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:1000
short slot time:yes
connected time: 715 seconds

------ second meshpoint

mesh1 (openwrt 15.0: Kernel 3.18.20)
Config file:
% cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option path 'platform/ath9k'
option htmode 'HT20'
option txpower '17'
option country 'DE'
option channel '3'

config wifi-iface
option ifname 'mesh0'
option device 'radio0'
option network 'mesh'
option mode 'mesh'
option mesh_id 'dmesh'
option encryption 'none'
option macaddr '00:23:EB:2C:FC:42'

% iw mesh0 station dump
Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 56 ms
rx bytes: 910260
rx packets: 13891
tx bytes: 783
tx packets: 10
tx retries: 0
tx failed: 0
rx drop misc: 45
signal: -56 [-65, -57] dBm
signal avg: -57 [-65, -57] dBm
Toffset: 18446743962739979724 us
tx bitrate: 78.0 MBit/s MCS 12
rx bitrate: 18.0 MBit/s
expected throughput: 43.303Mbps
mesh llid: 17217
mesh plid: 286
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:1000
short slot time:yes
connected time: 715 seconds

% ifconfig mesh0 10.0.0.124
ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: seq=0 ttl=64 time=3.616 ms
64 bytes from 10.0.0.2: seq=1 ttl=64 time=1.214 ms

ping is possible.

Im not shure about these 2 options:
option hwmode '11g'
option htmode 'HT20'
but without encryption does it work.

Thanks & Regards
Sven

chunyeow · 2016-07-27T15:50:37Z

What is the chipset or wireless driver that used for both site?

Chun-Yeow

On Wed, Jul 27, 2016 at 3:05 PM, chaosenze [email protected] wrote:

Hi Marco,

without encryption it works fine.

mesh0 (arch linux: kernel 4.6.4-1-ARCH) without config file, my commands
are:
% iw phy phy0 interface add mesh0 type mesh mesh_id dmesh
% ip link set dev mesh0 address 04:f0:21:14:c9:42
% iw dev mesh0 set channel 3
% ifconfig mesh0 10.0.0.2 up

% iw mesh0 station dump
Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 56 ms
rx bytes: 910260
rx packets: 13891
tx bytes: 783
tx packets: 10
tx retries: 0
tx failed: 0
rx drop misc: 45
signal: -56 [-65, -57] dBm
signal avg: -57 [-65, -57] dBm
Toffset: 18446743962739979724 us
tx bitrate: 78.0 MBit/s MCS 12
rx bitrate: 18.0 MBit/s
expected throughput: 43.303Mbps
mesh llid: 17217
mesh plid: 286
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:1000
short slot time:yes
connected time: 715 seconds

mesh1 (openwrt 15.0: Kernel 3.18.20)
Config file:
% cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option path 'platform/ath9k'
option htmode 'HT20'
option txpower '17'
option country 'DE'
option channel '3'

config wifi-iface
option ifname 'mesh0'
option device 'radio0'
option network 'mesh'
option mode 'mesh'
option mesh_id 'dmesh'
option encryption 'none'
option macaddr '00:23:EB:2C:FC:42'

% iw mesh0 station dump
Station 00:23:eb:2c:fc:42 (on mesh0)
inactive time: 56 ms
rx bytes: 910260
rx packets: 13891
tx bytes: 783
tx packets: 10
tx retries: 0
tx failed: 0
rx drop misc: 45
signal: -56 [-65, -57] dBm
signal avg: -57 [-65, -57] dBm
Toffset: 18446743962739979724 us
tx bitrate: 78.0 MBit/s MCS 12
rx bitrate: 18.0 MBit/s
expected throughput: 43.303Mbps
mesh llid: 17217
mesh plid: 286
mesh plink: ESTAB
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:1000
short slot time:yes
connected time: 715 seconds

% ifconfig mesh0 10.0.0.124
ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: seq=0 ttl=64 time=3.616 ms
64 bytes from 10.0.0.2: seq=1 ttl=64 time=1.214 ms

ping is possible.

Im not shure about these 2 options:
option hwmode '11g'
option htmode 'HT20'
but without encryption does it work.

Thanks & Regards
Sven

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#50 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABBewoQXolKHayJ9-zt_qlaip4vmQ1n8ks5qZwMqgaJpZM4JUnKL
.

chaosenze · 2016-07-27T16:22:32Z

mesh0

Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
kernel module ath9k

        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO

mesh1

Router Buffalo WZR-HP-G300NH Openwrt 15.05
kernel module ath9k
Wireless Hardware should be: Atheros AR9160 BB/MAC and AR9103 2.4 GHz 3x3 MIMO radio b/g/n

        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO

Without encryption it works fine but with encryption ping is not possible. I did the config like the wiki on this page.

Can I start the mesh first and switch the encryption later on, maybe? Or can I get any further logs to clarify what goes wrong?

chaosenze · 2016-07-30T17:48:51Z

Now I started both sides with the same config file and the same commands, after

on arch linux side:
/sbin/meshd-nl80211 -c /etc/authsae.cfg -i mesh0

..
estab with 00:24:a5:da:fa:2a
set auth flag (seq num=1469900419)
mesh plink with 00:24:a5:da:fa:2a established
Mesh plink timer for 00:24:a5:da:fa:2a fired on state ESTAB

on openwrt side:

estab with 04:f0:21:14:c9:42
set auth flag (seq num=1469901877)
mesh plink with 04:f0:21:14:c9:42 established
nlerror, cmd 0, seq 1469901880: Invalid argument
nlerror, cmd 18, seq 1469901881: Invalid argument
Mesh plink timer for 04:f0:21:14:c9:42 fired on state ESTAB
Timeout for peer 04:f0:21:14:c9:42 in state 4

chunyeow · 2016-07-31T15:47:33Z

ath9k should have no problem with hw encryption.

Chun-Yeow

On Sun, Jul 31, 2016 at 1:48 AM, chaosenze [email protected] wrote:

Now I started both sides with the same config file and the same commands,
after

/sbin/meshd-nl80211 -c /etc/authsae.cfg -i mesh0

..
estab with 00:24:a5:da:fa:2a
set auth flag (seq num=1469900419)
mesh plink with 00:24:a5:da:fa:2a established
Mesh plink timer for 00:24:a5:da:fa:2a fired on state ESTAB

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#50 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABBewsQAQWwYDUFdsTumVM5GgLtuz-Bfks5qa46EgaJpZM4JUnKL
.

sritam2 · 2017-05-15T10:49:25Z

Hi chaosenze,

Did you find a solution to your problem. You were not able to ping between the mesh nodes in a secured MESH network connection. Even I am facing the same problem.
Did you find a solution/workaround for this problem. Were you able to ping between the nodes after forming the secured MESH network.

Please help me. I am facing the same issue. In an open MESH I am able to ping. But once I form a secured MESH , I am not able to ping.

Thanks and Regards,
Sritam Paltasingh.

sritam2 · 2017-05-19T14:58:12Z

Dear All,

I was able to solve the above problem by using wpa_supplicant instead of authsae.
Please download wpa_supplicant from git://github.com/cozybit/wpa_supplicant.git. Make a copy of the defconfig file and name it as .config. In the .config file add the following lines:
CONFIG_MESH=y
CONFIG_AP=y
CONFIG_SAE=y
CONFIG_LIBNL32=y

Then build and install the wpa_supplicant using the make and make install command.
Now follow the procedure of forming the MESH network using the guidelines at the wiki page. After securely forming the MESH network, if you try to ping between the secured MESH nodes, then you will be able to do it.

Thus, wpa_supplicant performs better than authsae.

Thank you all once again.

Thanks and Regards,
Sritam Paltasingh.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

no data over mesh #50

no data over mesh #50

chaosenze commented Jul 25, 2016

mporsch commented Jul 26, 2016

chaosenze commented Jul 27, 2016 •

edited

Loading

chunyeow commented Jul 27, 2016

chaosenze commented Jul 27, 2016 •

edited

Loading

chaosenze commented Jul 30, 2016 •

edited

Loading

chunyeow commented Jul 31, 2016

sritam2 commented May 15, 2017

sritam2 commented May 19, 2017

no data over mesh #50

no data over mesh #50

Comments

chaosenze commented Jul 25, 2016

iw mesh0 station dump

cat /etc/authsae.cfg

cat /etc/config/wireless

mporsch commented Jul 26, 2016

chaosenze commented Jul 27, 2016 • edited Loading

chunyeow commented Jul 27, 2016

chaosenze commented Jul 27, 2016 • edited Loading

mesh0

mesh1

chaosenze commented Jul 30, 2016 • edited Loading

chunyeow commented Jul 31, 2016

sritam2 commented May 15, 2017

sritam2 commented May 19, 2017

chaosenze commented Jul 27, 2016 •

edited

Loading

chaosenze commented Jul 27, 2016 •

edited

Loading

chaosenze commented Jul 30, 2016 •

edited

Loading