IP address resolution of the firewall itself

[gurpal2000]

I've been on OPNsense for a while now, but one thing has always bugged me.

From within the lan, when I ping the OPNsense server, I get the IP address assigned by the ISP as opposed to the internal network subnet (192.168.10.x) - from a Windows machine. I use unbound. Dhcp clients are registered.

Windows example:

C:\Windows\System32>ping sense

Pinging sense.lan [x.y.115.212] with 32 bytes of data:
Reply from x.y.115.212: bytes=32 time<1ms TTL=64

Linux seems to be fine, but there is a short delay before the pings return.

gurpal@proxmox:~$ ping sense
PING sense.lan (192.168.10.1) 56(84) bytes of data.
64 bytes from sense.lan (192.168.10.1): icmp_seq=1 ttl=64 time=0.163 ms

Is there something mysterious Windows clients are doing? When I do ipconfig, it all looks great to me.

thanks

[IsaacFL]

Mine always pings the interface my Windows machine is on.  When i do nslookup for the opnsense, I see all of the addresses for every interface.

[gurpal2000]

OK. nslookup from windows does that for me too. Something to do with the order perhaps?

C:\Windows\System32>nslookup sense
Server:  sense.lan
Address:  192.168.10.1

Name:    sense.lan
Addresses:  x.y.115.212
          192.168.10.1

and Linux seems similar

gurpal@proxmox:~$ dig sense

; <<>> DiG 9.16.22-Debian <<>> sense
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1223
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;sense.                         IN      A

;; ANSWER SECTION:
sense.                  3600    IN      A       x.y.115.212
sense.                  3600    IN      A       192.168.10.1

;; Query time: 0 msec
;; SERVER: 192.168.10.1#53(192.168.10.1)
;; WHEN: Sun Jan 09 08:38:10 GMT 2022
;; MSG SIZE  rcvd: 66