WRT3200ACM - DHCP(dnsmasq) failing to allocate IP to Wireless Camera (2.4Ghz)

gxgani · March 2, 2018, 7:14pm

I am trying to setup the Wireless camera to connect over 2.4Ghz radio (WPA2 PSK CCMP) of my 3200ACM running Lede SNAPSHOT r6302-0f54d96d24 but DHCP doesn't seem to allocate an IP. I see the connection being initiated in the Wireless tab with hostname "?".

Logs:

Fri Mar  2 14:07:05 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 4)
Fri Mar  2 14:07:06 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:07:06 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (RSN)
Fri Mar  2 14:07:17 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated
Fri Mar  2 14:07:51 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:07:51 2018 kern.debug kernel: [43300.431211] ieee80211 phy1: staid 4 deleted

On the contrary, I am able to setup the camera to connect to my Velop Node (2.4Ghz radio, WPA2 PSK CCMP).

EDIT:
After allocating a static ip for the camera's mac address, the log:

Fri Mar  2 14:10:22 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 1)
Fri Mar  2 14:10:23 2018 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX
Fri Mar  2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (WPA)
Fri Mar  2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: group key handshake completed (WPA)
Fri Mar  2 14:10:27 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:30 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:33 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:37 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:40 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:43 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:43 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated
Fri Mar  2 14:10:48 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:51 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:54 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:10:59 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:02 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:05 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address
Fri Mar  2 14:11:08 2018 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX

jeff · March 2, 2018, 8:13pm

Looks like the camera associated with a different AP the second time. Is that expected?

Seeing the packet trace (or lack of it) would help. tcpdump-mini should install enough of tcpdump to be able to capture the packets.

tcpdump -vni wlan1 udp and port 67 or port 68

gxgani · March 2, 2018, 8:36pm

hey, yes. I tried to setup a second 2.4ghz radio wth different encryption(s).

I tried monitoring the tcpdump unfortunately no connections appeared when camera tried to connect

anon57995562 · March 2, 2018, 9:02pm

SSH in to the router an run the following...

cat /etc/config/wireless

Note: Make sure to obscure the "option key" value(s) in the wireless config results before posting.

gxgani · March 2, 2018, 9:26pm

config wifi-device 'radio0'
	option type 'mac80211'
	option channel '36'
	option hwmode '11a'
	option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
	option htmode 'VHT80'
	option disabled '1'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'OpenWrt'
	option encryption 'none'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
	option country 'US'
	option legacy_rates '1'
	option htmode 'HT20'
	option txpower '30'
	option channel '2'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid '2_4_SSID'
	option key 'SECURE_PASS'
	option wmm '0'
	option encryption 'psk2'

anon57995562 · March 2, 2018, 9:32pm

I would recommend the following changes for your config...

2.4 Ghz -

Use either channel 1, 6, or 11.

Set channel width to HT20.

Transmit power can be set up to 25.

5 Ghz -

Change the channel to one in the higher range that doesn't require DFS, In the US, I recommend starting at 153.

Set channel width to VHT80.

Transmit power can be set up to 30.

Both -

Set encryption to WPA2-PSK and AES.

I would also recommend Lizard Systems free WiFi Scanner to see what wireless traffic in your area looks like…

https://lizardsystems.com/wi-fi-scanner

If you have set up a static IP on the router for the device, the IP also needs to be set up on the device as well. Set the duration for the lease to unlimited.

gxgani · March 2, 2018, 9:38pm

I've setup only 2.4Ghz on 3200ACM to connect to my IoT devices on channel 11. During testing, I changed it to Auto and I have my gigabit devices on ethernet and for 5Ghz I use my velop nodes hence it is disabled. I don't think this issue is associated with wireless connection as you clearly see from the logs that the camera gets authenticated but dnsmasq fails to discover and allocate an IP.

anon57995562 · March 2, 2018, 9:41pm

Channel 2, unless you just changed it to 11...

I use the above recommendations for all my wireless devices, and they work with no issue.

If you set a static IP, it's already allocated. The IP should be either below the start of the pool range, or above the end of the pool range. (i.e. pool is 192.168.1.100 to 192.168.1.199, so either 192.168.1.99 or 192.168.1.200 would work to avoid the possibility of a collision.)

What does the WiFi camera config look like?

gxgani · March 2, 2018, 9:44pm

Oh yea, 2. I was checking the traffic congestion and trying all the ways possible to eliminate the issue with wireless AP. All my IoTs are able to connect and get IP, it's just this cam.

config host
        option name 'Hikam-0505'
        option dns '1'
        option mac '88:83:5d:xx:xx:xx'
        option ip '192.168.1.200'
        option leasetime 'infinite'

anon57995562 · March 2, 2018, 9:46pm

Should be unlimited.

How is the camera configured to connect?

gxgani · March 2, 2018, 9:49pm

It's the same

anon57995562 · March 2, 2018, 9:49pm

Post screenshots of the camera configuration GUI.

gxgani · March 2, 2018, 9:55pm

Accessed from Velop's 2.4Ghz AP.

21%20PM

mbo2o · March 2, 2018, 10:01pm

Have you updated the Hi-Kam firmware

anon57995562 · March 2, 2018, 10:01pm

See the HiKam setup instructions.

http://supportus.hi-kam.com/en/support/solutions/articles/16000069347-initial-setup-by-lan-cable-hikam-a7-

gxgani · March 2, 2018, 10:07pm

The app says it's on the latest.