mr-canoehead
commented
4 years ago One thought I have is that you may be experiencing USB power issues; Raspberry Pis have a low limit for the amount of power that can be delivered to USB devices (1.2A for all devices combined). I experienced USB power issues when I started using a Vantec dual gigabit ethernet adapter for the bandwidth monitoring bridge (it consumes a lot of power). I could not reliably get all USB interfaces working at the same time. After changing the configuration so that all USB devices were connected via an externally powered USB 3 hub I had no further issues.
I am using a D-Link DWA-182 for monitoring the 5GHz network, the internal WiFi adapter is monitoring the 2.4GHz network. I used the D-Link because I happened to have one when I started this project. Unfortunately I hesitate to recommend any D-Link products since the company has a history of changing chipsets between versions of the same product, so a DWA-182 adapter with a different version number may not work at all. I had to build the driver from a GitHub repository since the adapter is not supported by D-Link for Linux devices. It took several attempts to find a repository with a driver that worked.
I have not had anyone submit info about other dual band adapters, so I can't suggest any others to try at this time.
Here's my current interfaces.json config, the if_5GHz interface is the D-Link adapter. It's in the root network namespace since its driver doesn't support the set_wiphy_netns command.
{
"configure_interfaces" : true,
"test_exec_namespace" : "ns_eth0",
"interfaces" : {
"wlan0" : {
"type" : "wireless",
"wpa_supplicant_config" : "/etc/wpa_supplicant/wlan0.conf",
"ipv4_addr" : "10.1.2.111",
"ipv4_gw" : "10.1.2.1",
"namespace" : "ns_wlan0",
"alias" : "if_2.4GHz"
},
"wlxf48ceb9b7044" : {
"type" : "wireless",
"wpa_supplicant_config" : "/etc/wpa_supplicant/wlxf48ceb9b7044.conf",
"ipv4_addr" : "10.1.2.112",
"ipv4_gw" : "10.1.2.1",
"namespace" : "root",
"alias" : "if_5GHz"
},
"eth0" : {
"type" : "ethernet",
"ipv4_addr" : "10.1.2.110",
"ipv4_gw" : "10.1.2.1",
"namespace" : "ns_eth0",
"alias" : "if_lan"
}
},
"bandwidth_monitor_bridge" : {
"configure" : true,
"namespace" : "bwmonitor",
"bridge_name" : "bwmonitor",
"modem_interface" : "enx000acd28f63a",
"router_interface" : "enx000acd28f639"
}
}
christasich
I recently purchased TP-Link Archer T3U Dual WiFi Adapter to set up 2.4GHz monitoring on my network. I'm using the RPi4 internal antenna to monitor the 5GHz channel. I had to install drivers for the adapter (per this guide), but I was able to connect it to my network. I reran the configuration per the wiki. After bringing the system back online, I tried manually issuing a network test and received this error.
After some debugging, I determined the issue was assigning an IPv4 to the interface which caused the configure_interfaces.py script to fail on startup. Hence, no interfaces to test. When I manually run configure_interfaces.py, I get this error.
I've tried the configuration in a number of different ways including changing the USB port, making it the only wlan interfaces, changing the assigned IP, etc. All signs point to an issue with the adapter. Also, the adapter does not support network namespaces and was assigned to "root". I'm unsure why it's having trouble grabbing an IP. When it's not part of the configuration for this project, I see it on my network at an IP assigned by my DHCP. Any advice? For context, here is the non-working interfaces.json
And the working one...
Also, a couple of follow-up questions...