wlan-pi/neo2

WLAN Pi Release Repository

WLAN Pi

The goal of the WLAN Pi is provide wireless LAN professionals with a ready-to-use device capable of providing throughput measurements for assessing network performance.

The WLAN Pi can be used to test Wired-to-Wired, Wired-to-Wireless, and even Wireless-to-Wireless. These tests can be used to assist in establishing baselines, help with troubleshooting, testing consistency, as well as measuring end-to-end network throughput.

Resources

You can check out our home page at wlanpi.com and read our docs at docs.wlanpi.com.

Feedback

Do you have feedback for us? Stop over at WLAN-Pi/feedback and drop us a message.

neo2's Issues

Hotspot mode - add “Show PSK” menu item

Add a “Show PSK” menu item to show the current WPA2 PSK. Useful when you boot off an old SD card and can’t remember what the PSK was

tcpdump permissions fix

Add in fix for tcpdump permissions issue impacting wlan-extcap & wlan-extcap-win.

Add in final steps of this process to ensure that tcpdump permissions maintained if 'apt upgrade' overwrites existing tcpdump file: https://peternixon.net/news/2012/01/28/configure-tcpdump-work-non-root-user-opensuse-using-file-system-capabilities/

Kismet GUI is not working

Hi Guys,
Wanted to test Kismet in new release and found that it is not working properly.
Starting from CLI works fine and prints those info messages like INFO: Detected new 802.11 Wi-Fi device D4:6A:6A:C2:26:C0
but when I go to the server web page, it shows this initial dialog to provide user and password, then when I put the data and Save nothing is showing - blank page with Kismet logo and empty drop-down menu, no content. When I refresh the page it shows again initial dialog with user and password. As I remember in previous version I had to provide correct login credentials for the server - maybe this is not working?
Thanks for Your job!

It takes about 2 mins for the Pi to become available on 169.254.42.1

After the WLAN Pi v2 boots up, it takes about 2 minutes before it becomes available for ping or SSH on 169.254.42.1 via usb0 OTG interface.

Tested on macOS Catalina 10.5.5

md5sum for wlanpi-neo2-v2.0.0.img.gz

I have downloaded the image file several times, for me md5sum is always same as following.

1e7a0b883aa289ea8350c29d19caf34f wlanpi-neo2-v2.0.0.img.gz

"port blinker" feature

It would be great if we could add a "port blinker" feature to the system. In this way, the ethernet port's "phy" is enabled/disabled every x seconds (3 seconds up, 3 seconds down for example). In this way, one can plug the wlan-pi to a remote port, set the port-blinker feature on and then look at the switch -either in CLI, log or directly at the port LEDs and see which one is blinking. Thus finding your port.

This would be like a virtual "cable beeper" / "cable locator".

Pre-build checks - Lessons from v1.8.4

1. check following files are executable in ~/NanoHatOLED/BakeBit/Software/Python/scripts:

• bettercap_ctl
• kismet_ctl
• profiler_ctl

2. Check /etc/sudoers.d/wlanpidump looks like this:

• wlanpi ALL = (root) NOPASSWD: /sbin/iwconfig, /usr/sbin/iw, /bin/date

display types

how about e-ink display types? for example dfrobot e-ink with 2-4 buttons intergrated.
for example one of this: https://www.dfrobot.com/search-e-ink.html
we could use some rpi instead nanopi: rpi0wh (with OTG) with ethernet hat, ups-lite hat and one of this e-ink display.

Investigate DHCP client behaviour and "dynamically assigned IP address stickiness" on eth0

Steps to replicate the issue

1. Disable the below workaround by commenting the two "sudo /sbin/dhclient" lines in /home/wlanpi/NanoHatOLED/BakeBit/Software/Python/scripts/networkinfo/networkinfocron.sh
2. Reboot the Pi
3. Plug eth0 of the WLAN Pi to a network that is using DHCP
4. It will successfully get an IP via DHCP
5. Disconnect the Ethernet cable and connect the Pi (without powering the Pi off) to a different network that is using DHCP
6. The WLAN Pi will keep using its original address from step 2 and it will not request a new IP via DHCP from the new network

Currently BakeBit dev branch code works just fine thanks to this workaround

• Release DHCP IP address leased for eth0 after eth0 goes down (using networkinfocron.sh cron script to execute "sudo /sbin/dhclient -r eth0")
• Renew IP via DHCP when eth0 goes up (using networkinfocron.sh cron script to execute "sudo /sbin/dhclient eth0")

Test enhancement for v1.9

test 1 2 3

Putty installer should be updated to 0.73

https://www.chiark.greenend.org.uk/~sgtatham/putty/

It seems that this release also include security fixes...

Add TFTP server to the WLAN Pi

Hotspot mode - show number of connected clients

Add the number of connected clients to the OLED display. And also testing image attachments on Github;)

Wrong broadcast-address in dhcpd.conf

Hello,
please correct me if this issue should be reported in different place.

Looks that option broadcast-address is set to 192.168.42.1 in dhcpd.conf

wlanpi@wlanpi:~$ tail /etc/dhcp/dhcpd.conf
# WLAN Pi DHCP Server config
subnet 192.168.42.0 netmask 255.255.255.224 {
  range 192.168.42.2 192.168.42.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 192.168.42.1;
  option broadcast-address 192.168.42.1;
  default-lease-time 600;
  max-lease-time 7200;
}
wlanpi@wlanpi:~$ 

Thus my desktop is getting wrong broadcast address via USB OTG

16: enp0s26u1u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether be:b8:06:ea:b2:15 brd ff:ff:ff:ff:ff:ff
    inet 192.168.42.6/27 brd 192.168.42.1 scope global deprecated dynamic noprefixroute enp0s26u1u3
       valid_lft 49sec preferred_lft 0sec
    inet6 fe80::bcb8:6ff:feea:b215/64 scope link 
       valid_lft forever preferred_lft forever

[yananet@arch-desktop]: ~>$ ping 192.168.42.1
ping: Do you want to ping broadcast? Then -b. If not, check your local firewall rules
[yananet@arch-desktop]: ~>$ 

I had to disable DHCP to access 192.168.42.1.
and now it is working if I changed the broadcast address with correct broadcast address.

wlanpi@wlanpi:~$ tail /etc/dhcp/dhcpd.conf
# WLAN Pi DHCP Server config
subnet 192.168.42.0 netmask 255.255.255.224 {
  range 192.168.42.2 192.168.42.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 192.168.42.1;
  option broadcast-address 192.168.42.31;
  default-lease-time 600;
  max-lease-time 7200;
}
wlanpi@wlanpi:~$ 

correct me if I am wrong or let me know if this is expected.

Tested version : WLAN Pi 1.9.1 [WLPC edition]

Thanks.

RFC: Use Firewalld in Cockpit in a future version of the 2.x train

While we'll proceed with using ufw for the WLAN Pi firewall in the v2.0 image version, the proposal is to use firewalld, that is native to Cockpit, in a future image release.

This will require coding updates for a few modules that use ufw (e.g. hostspot mode), but it will provide a better user experience going forwards as it has a web GUI for administration.

Perhaps we could move towards using firewalld in v2.1 or v2.2?

Comments below please...

WLAN Pi Hotspot testing

The hotspot code has been updated to reflect the enhancement from Francois which allows connectivity between interfaces so that anyone connected to the SSID can route traffic out through the ethernet port.

This has been posted in the repo but needs testing further to make sure there are no unintended side-effects when switching in and out of hotspot mode on other WLANPi functions/utilities.

cannot boot v2.1.3 on neo2

flashed wlanpi-neo-v2.1.3-231111.img.gz using balena-etcher
inserted sd card into neo2 device and waited 5 min

• ethernet port shows activity, but there is no on-screen display

same process to flash wlanpi-neo2-v2.1.0-230410.img.gz which works fine on same neo2 device

CF-953 new Vendor ID

The newer CF-953 adapters use a different Vendor ID than is currently included with the driver.

Taken from: https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md

Create a file called /etc/udev/rules.d/90-usb-3574:6211-mt7921u.rules
Copy the below lines and paste them into the above file that you are creating:

ACTION=="add",
SUBSYSTEM=="usb",
ENV{ID_VENDOR_ID}=="3574",
ENV{ID_MODEL_ID}=="6211",
RUN+="/usr/sbin/modprobe mt7921u",
RUN+="/bin/sh -c 'echo 3574 6211 > /sys/bus/usb/drivers/mt7921u/new_id'"

Save file and reboot.

Speed Test Speeds

I have one of the black cube WLANPI and I am not able to see anywhere close to line rate, which I was able to see on 1.9.

My speeds never seem to show over 400mbps.

Systemd services

Move any automatically starting services in cron to systemd

NanoPi2 - since v2.0.0 no display output or network connect anymore

on a nanopi2 I didn't have any problems until v1.9.1, but since v2.0.0 it seems the image does not work anymore. I tested several micro sdcard, which all worked until v1.9.1, but not with v2.0.0. I do not get any display output anymore and the IP169.254.42.1 is not reachable,too...

Update FPMS code to include LLDP info

FPMS code needs to be updated to add new LLDP detection code from Jiri.

Wi-Fi Console mode - add “Show PSK” menu item

Add a “Show PSK” menu item to show the current WPA2 PSK. Useful when you boot off an old SD card and can’t remember what the PSK was.

Update the WLAN-Pi README.md

The goal of the WLAN Pi is provide wireless LAN professionals with a ready-to-use device capable of providing throughput measurements for assessing network performance.

The WLAN Pi can be used to test Wired-to-Wired, Wired-to-Wireless, and even Wireless-to-Wireless. These tests can be used to assist in establishing baselines, help with troubleshooting, testing consistency, as well as measuring end-to-end network throughput.

I think this can be expanded on. We have more features than throughput measurements and tests at this point.

Implement additional driver Netgear A6210

Hi
It would be great if you could implement, as beta marked maybe, the following driver for the Netgear A6210. I've compiled and used it in my installation (via DKMS), running build 1.8.3 successfully.
Driver source: https://github.com/kaduke/Netgear-A6210
It would then support all wi-fi adapters based on:
Ralink / Mediatek mt766u, mt7632u and mt7612u chipsets.
In particular, the driver supports several USB dongles such as Netgear-A6210, ASUS USB-AC55, ASUS USB-N53 and EDUP EP-AC1601.

Thanks for considering.