Modify

Opened 3 years ago

Last modified 3 years ago

#19557 new defect

Wifi in Client mode doesn't show IP Address in wifi status page

Reported by: anonymous Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

  1. Set up a wifi device in Client mode
  2. Confirm it's connected and everything is working
  3. Go to wifi status page - Network > Wifi
  4. Note that the network to which we are connected is shown under "Associated Stations", and that the "IPv4-Address" is shown as "?".

I would expect the IPv4-Address to show up as our IP address for that connection, rather than "?".

Note that our IP address shows up correctly on the main status page (Status > Overview) under the "IPv4 WAN Status" section.

Attachments (0)

Change History (4)

comment:1 follow-up: Changed 3 years ago by jow

Is the client in question present in the arp cache? If not there's no way for LuCI to know.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 3 years ago by anonymous

Replying to jow:

Is the client in question present in the arp cache? If not there's no way for LuCI to know.

How do I check the arp cache?
-gufus

comment:3 in reply to: ↑ 2 Changed 3 years ago by anonymous

Replying to anonymous:

Replying to jow:

Is the client in question present in the arp cache? If not there's no way for LuCI to know.

How do I check the arp cache?
-gufus

Found it: arp cache, /etc/ethers, dhcp leases, etc

No, there NOT in the arp cache

Is there a fix?
-gufus

comment:4 Changed 3 years ago by YodaDaCoda

Running latest r46133.

The MAC shown next to the client Wifi under "Associated Stations" doesn't match any MAC shown in arp cache or ifconfig, but it is 1-off from the MAC shown in arp cache for the IP of the AP we're connected to.

In my specific case, MAC shown in Luci is 00:22:6B:E2:8F:D9, yet MAC for the AP is 00:22:6B:E2:8F:D8.

root@OpenWrt:~# arping -I wlan0 192.168.1.1
ARPING to 192.168.1.1 from 192.168.1.101 via wlan0
Unicast reply from 192.168.1.1 [00:22:6B:E2:8F:D8] 1.785ms
root@OpenWrt:~# iw dev wlan0 link
Connected to 00:22:6b:e2:8f:d9 (on wlan0)
<snip>

Upon further investigation, it seems to be because the AP replies to ARP requests for its IP with the MAC of its ETH interface instead of its WLAN interface. Unsure where to go from here.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.