@cmcqueen said in Finding pfSense on WAN, using Zeroconf:
I access the pfSense web config via its WAN interface (on my LAN
Not a good test test set up.
You should bring a collection of devices, if not all of them, - your "test environment" - and hook them all up to a LAN on pfSense. Then test that LAN segment - and pfSense. You'll be having a router-after-router setup which is for outgoing (== Internet) traffic completely transparent.
Making WAN accessible is not part of real set up.
The exception might be : testing a NAT rule (while IPv4 lasts).
"Zeroconf" (whatever it actually is) needs ports to be open and/or redirected to some LAN (pfSense) based device with a running service that implements Zeroconf. That will normally never be the case as you do not want the Internet to "Zeroconf" your installation.
Keep in mind that pfSense is a firewall and router : nothing from a WAN perspective can be seen. Shut down the firewall part, define routes on your main LAN's router (the one that hands out a WAN IP to pfSense) and set up pfSEnse as a basic router.
@cmcqueen said in Finding pfSense on WAN, using Zeroconf:
how can I find the pfSense address?
If the initial LAN works well, the DHCP (client) request made by pfSense to the upstream ISP router registers it's DNS name 'pfsense' into the upstream LAN DNS (your ISP router). So, as soon as it is powered on, you could use it's name :
cb2465ae-5965-4e8c-9f83-e2045b3c61a7-image.png
Typically, when you type
ping pfsense
on a PC on the ISP LAn, it (the ISP router) would resolve 'pfsense' to pfSense's IP first, and then starts to ping to this IP.
But nothing will happen ... no reply.
You have to add a firewall rule on the pfSense WAN interface so it can actually receive these ICMP requests - and thus reply.
