@qinn
Sent him an email Dan an email to the address on his site.. Not sure what is happening, my Teams stopped working. Disable it/turn it off and the problem went away.

Mmm, seems like it could be a real upstream issue then. What hardware are you running pfSense on?

@chpalmer said in Strange behavior with gateway:

???

When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365
That's unexpected.

Yes if you are policy routing traffic from LAN via a specific gateway you need another rule above that to allow traffic to other local destinations that avoids policy routing.

So for example:
Screenshot from 2025-07-25 01-17-11.png

There I'm using an alias 'LOCAL' that contains all the subnets I need to bypass policy routing for.

@pfsvrb
this was an issue on my system also..
Target & Interval were default set to 0..
change to 5 & 100 fixed it

@stephenw10 you are of course correct. I meant click on the icon which would generate an emoji-like response.

Make sure you are using Python mode in DNSBL.

Do you see anything blocked in the firewall logs?

Connectivity from that host is otherwise good?

Is it using the same DNS server(s) when configured statically?

Ultimately I would run a packet capture when you run the failing task and see what's actually failing there.

@sub2010
Idee ja, jedoch keine Lösung, und letzteres ist ja, was du suchst laut Titel. 😊
Und mit Plex habe ich keinerlei Erfahrung. Daher weiß ich auch nicht, wie der Stream vom Server zum Plexamp Client kommen soll. Streamt da die App am Smartphone zum Client, oder wird das nur benötig, um die Verbindung herzustellen und den Client zu steuern?

Wenn nicht bekannt, könntest du das mal austesten. Wäre ggf. hilfreich.

Ich würde vermuten, dass die App in den Stream eingebunden ist. Und dafür könnte ein weiteres Protokoll erforderlich sein, vielleicht UPnP / DLNA.

Um herauszufinden, was die Geräte benötigen, könntest du ein Packet Capture an beiden Interfaces jeweils mit einem IP Filter auf Smartphone bzw. Plexamp Client und UDP laufen lassen.
Schau dir an, was so auf Broadcast u. Multicast IPs geht.

Dann ist mir nicht klar, was genau ist diese Unify Zeugs? Ist das tatsächlich nur ein AP und das Subnetz der Clients liegt an der pfSense an?
Ist es nicht eine Mesh-Konstrukt?

OK so it looks like you had two issues:

The installer didn't work as you expected it to but you were able to get 2.8 installed and booted.

The resulting install didn't behave as you expected. That's independent of the installer and 2.7.2 would have behaved identically in that situation.

So after install you assigned two interfaces, pfSense names them WAN and LAN but any interface can be anything. And you configured them both to be DHCP since both subnets already have a DHCP server?

The typical subnet conflict that users hit when installing behind another firewall if that pfSense uses 192.168.1.1/24 as the default LAN address and that subnet is also used by the upstream firewall WAN side.
I assume you didn't hit that since both subnets already existed in your network so must be using different subnets? What are they?

However you then say you set the LAN back to a static address? Presumably in the same subnet?

By default pfSense creates firewall rules on the LAN interface to allow access to the webgui there. That applies whether the LAN is static or DHCP.

How exactly were you trying to connect? From where?

@Bob-Dig
Not seeing those in my firewall logs. Yours do look rather odd.

@Lars_ said in How to update No-IP IPv6 (dynupdate.no-ip.com does not have an AAAA record):

@SteveITS Determined testing pays off. It works now 🎉

Same for
dynupdate.no-ip.com/nic/update?hostname=thisismydomain.ddns.net&myip=%IP%
with option "HTTP API DNS Options = Force IPv4 DNS Resolution" enabled.

I was actually quite close. The solution is to update the AAAA record using IPv4:

Service Type: Custom (v6)

HTTP API DNS Options = Force IPv4 DNS Resolution

Update URL:
dynupdate.no-ip.com/nic/update?hostname=thisismydomain.ddns.net&myipv6=%IP%

Note: It has to be &myipv6=, not &myip=

Is this something that makes sense to be implemented in No-IP (v6) and No-IP (free-v6)? It would not work if IPv4 DNS resolution isn't available, but I guess that is not very common in the wild.

Haven't found a way to tag this thread as SOLVED.

This solution worked for me!

Yes, it's in the RC.

No, just ordered from Amazon.

It restarts ntpd because that page has the external ntp server settings on it. But nothing there looks like it would affect the firewall... 🤔

@revengineer yeah my issue is different from yours than, but we actually don't know if @70tas 's is. They are using xfinity also so it could be the same issue as mine.

@coxhaus I no longer care either because the source code does not seem compilable for the average use. I used to have fun with compiling many years ago as a former smoothwall user.

While it may be preferable not to give the source away, the fact that pfsense if forked from an open source project (monowall) two decades ago may still require this. (I am not a legal expert on open source licensing.)

To bring this back to the title of the topic, this is solely about the release of an iso of the full compiled v2.8.0 for direct installs, not asking for anything more.