CLOSED: LuCI reporting strange IP address?

Installing and Using OpenWrt
1

I have two WiFi domains (SSID_0 & SSID_1). When a specific (24:6F:28:19:A2:F8) station with a static IP address of 192.168.0.80 joins SSID_1, the LuCI page "Network | Wireless" reports the association as: 192.168.0.56.
I can ping 80 from all valid locations. There is no static or dynamic lease in play that I can detect. If I change the IP address of 80 to say 90, LuCI still reports 56.

I hope the following image gives a flavor of my local network. Station 80 is lower-right. Breaking the WiFi STA connection between OpenWRT_0 and OpenWrt_1 makes no difference.
Hazelhurst

Regards, M.

2

You did a static lease, OpenWrt is not involved. You didn't use DHCP.

1 Like
3

Yes. I realize that. But the world and his dog say that station 80 is 80. But LuCI says its 56.
I'd like to know why? If I can't trust this one report what else is it not reporting correctly?
There must be a cache or something that needs clearing or refreshing?

Regards, M.

4
  • Do you happen to have a static config in OpenWrt?
  • Was it previously 56?
5

What happens if you run do a PTR lookup for 192.168.1.56 and .1.80? (something like dig -x 192.168.1.56; dig -x 192.168.1.80)

I assume both IPs are present in your ARP table? Same MAC possibly? Could be dnsmasq caching a hostname, Luci looking up the MAC to resolve an IP and returning the first result, or something.

1 Like
6

Good idea!

Test One:

mprowe@localhost:~> dig -x 192.168.0.235

; <<>> DiG 9.16.6 <<>> -x 192.168.0.235
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45959
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;235.0.168.192.in-addr.arpa.    IN      PTR

;; ANSWER SECTION:
235.0.168.192.in-addr.arpa. 0   IN      PTR     Gzunder.localnet.

;; Query time: 7 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Nov 18 20:27:11 GMT 2020
;; MSG SIZE  rcvd: 85

Dig is working. 235 is listed as gzunder.localnet at 192.168.0.1. All is as it should be.

Moving on, Test Two:

mprowe@localhost:~> dig -x 192.168.0.80

; <<>> DiG 9.16.6 <<>> -x 192.168.0.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26595
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;80.0.168.192.in-addr.arpa.     IN      PTR

;; Query time: 3 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Nov 18 20:29:51 GMT 2020
;; MSG SIZE  rcvd: 54

Station 80 in NOT found in the DNS Server (192.168.0.1)
So, check 56? Test Three:

mprowe@localhost:~> dig -x 192.168.0.56

; <<>> DiG 9.16.6 <<>> -x 192.168.0.56
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58994
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;56.0.168.192.in-addr.arpa.     IN      PTR

;; Query time: 3 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Nov 18 20:32:30 GMT 2020
;; MSG SIZE  rcvd: 54

Nop! No station 56 either.

I'll keep looking...

Regards, M.

7

Re-built bridge and problem went away!
Not SOLVED but I'm CLOSING.

Thanks for all the help.

Regards, M.

8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.