no wifi traffic

Just about everything about Red Pitaya
Post Reply
cnoda
Posts: 3
Joined: Sat Oct 06, 2018 3:35 pm

no wifi traffic

Post by cnoda » Sat Oct 06, 2018 4:20 pm

Hi,

I have no traffic on the wifi link.
This problem also existed 2 years ago (firmaware version in stable at he time).

In the browser, the network manager content is as expected.
It will be nice if someone can hint what would be the problem.
See RP cli commands below.

Regards,
Claro.

claro@claro-XPS-13-9350:~$ ssh root@192.168.1.10
root@192.168.1.10's password:
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.9.0-xilinx armv7l)

##############################################################################
# Red Pitaya GNU/Linux Ecosystem
# Version: 0.98
# Build: 685
# Branch:
# Commit: 0759d718c2f98bed50c2872a4656695710d6357a
# U-Boot: "redpitaya-v2016.4"
# Linux Kernel: "branch-redpitaya-v2017.2"
# Pro Applications: b50f2409fddc9092c307e0fdde4ae2f833e0ab72 Applications (v0.97-RC6-7-gb50f240)
##############################################################################
Last login: Sat Oct 6 14:22:36 2018 from 192.168.1.107

root@rp-f01db2:~# lsusb
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@rp-f01db2:~# ip a | grep wlan
6: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
inet 169.254.7.200/16 brd 169.254.255.255 scope link wlan0
inet 192.168.1.136/24 brd 192.168.1.255 scope global dynamic wlan0

root@rp-f01db2:~# ip r
default via 192.168.1.1 dev eth0 proto static
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.136 metric 1024
default dev wlan0 proto static scope link metric 2048
default dev eth0 proto static scope link metric 2048
169.254.0.0/16 dev wlan0 proto kernel scope link src 169.254.7.200
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.200.245
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.10
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.136
192.168.1.1 dev wlan0 proto dhcp scope link src 192.168.1.136 metric 1024

root@rp-f01db2:~# ping -c 3 google.com
PING google.com (216.58.207.238) 56(84) bytes of data.
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=6 ttl=53 time=7.07 ms
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=7 ttl=53 time=7.06 ms
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=8 ttl=53 time=7.05 ms

--- google.com ping statistics ---
8 packets transmitted, 3 received, 62% packet loss, time 7171ms
rtt min/avg/max/mdev = 7.051/7.062/7.077/0.097 ms

root@rp-f01db2:~# ping -c 3 192.168.1.136
PING 192.168.1.136 (192.168.1.136) 56(84) bytes of data.
64 bytes from 192.168.1.136: icmp_seq=1 ttl=64 time=0.159 ms
64 bytes from 192.168.1.136: icmp_seq=2 ttl=64 time=0.104 ms
64 bytes from 192.168.1.136: icmp_seq=3 ttl=64 time=0.099 ms

--- 192.168.1.136 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2050ms
rtt min/avg/max/mdev = 0.099/0.120/0.159/0.030 ms

And yet, wlan0 is not reachable from outside.

claro@claro-XPS-13-9350:~$ ping -c 3 192.168.1.136
PING 192.168.1.136 (192.168.1.136) 56(84) bytes of data.
From 192.168.1.107 icmp_seq=1 Destination Host Unreachable
From 192.168.1.107 icmp_seq=2 Destination Host Unreachable
From 192.168.1.107 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.136 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2049ms
pipe 3

claro@claro-XPS-13-9350:~$ ssh root@192.168.1.136
ssh: connect to host 192.168.1.136 port 22: No route to host
claro@claro-XPS-13-9350:~$

cnoda
Posts: 3
Joined: Sat Oct 06, 2018 3:35 pm

Re: no wifi traffic

Post by cnoda » Sat Oct 06, 2018 5:41 pm

More info. It is getting interesting.
For the record, the WiFi AP seats next to the RP

claro@claro-XPS-13-9350:~$ traceroute 192.168.1.136
traceroute to 192.168.1.136 (192.168.1.136), 30 hops max, 60 byte packets
1 claro-XPS-13-9350 (192.168.1.107) 2124.266 ms !H 2124.255 ms !H 2124.251 ms !H

claro@claro-XPS-13-9350:~$ traceroute 192.168.1.136
traceroute to 192.168.1.136 (192.168.1.136), 30 hops max, 60 byte packets
1 claro-XPS-13-9350 (192.168.1.107) 258.144 ms !H 258.115 ms !H 258.097 ms !H

claro@claro-XPS-13-9350:~$ ssh root@192.168.1.136
ssh: connect to host 192.168.1.136 port 22: No route to host
claro@claro-XPS-13-9350:~$

there is a correlation between the traceroute time-of-flight and whether the LAN cable is inserted in the RP or not. Having the LAN cable makes the delays shorter, as in the second example.
Note the traffic is on the wireless interface, not the LAN.

Other programs like ssh or ping do not see the RP wireless iface, as shown in the last command response.

Post Reply
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 4 guests