@netboy if you change the pool, then yes the devices that had lease with say IP .40 would get a new lease.. But its not going happen instantly.. The client would need to release and renew.. Unless you kill off the old lease it would still be able to renew that .40 etc..

If for example this .40 IP you want to know get something in your new pool that starts at .50 - would be to make sure that device does a release of the lease, and then gets a new one. Or you make sure you remove the lease on pfsense, the client might still continue to use that .40 until the lease expires on the device and he does a new discover and gets an ip in the new .50 pool.. But he wouldn't be able to "renew" it because pfsense no longer has that lease to renew.

If your device that currently has .40 is one of the ones you want with a reservation of .40, it wouldn't really matter - just setup the reservation for the .40 mac and whatever name you want to call it.

@karlossimo I asume you did it according to the 7100 documentation? https://docs.netgate.com/pfsense/en/latest/solutions/xg-7100-1u/configuring-the-switch-ports.html

With these kind of switch config you have to include the CPU in every VLAN. Assuming that is port 9 and 10 you gotta include these too for VLAN 20.

@stephenw10
I don't know this, thanks.

Is this also for 2.7.2 CE?

@JonathanLee I do not have an NVMe

Just to finish this thread :
It was the watchdog.

When you change your DHCPd from ISC to KEA, you have to delete the dhcp watchdog and re-create it with the right kea dhcp option after the change. That's all !

Thanks !

@eagle61 Das ist ein Testaufbau, da ich wegen der ganzen IPv6 Probleme auf dem Hauptsystem nicht alle 5 Minuten irgendwelche Neustarts machen kann.
Ich kann das Testinterface auch komplett löschen, verhält sich genauso. Hatte nur ein 2. Interface angelegt um zu testen.

@periko I agree with you. Most if not all firewalls today provide some ability to peak into what kind of traffic is flowing through your device.

@padrino121
Drop the WAN circuits on a switch will work as far as not having to physically go on site but unfortunately the FRR configuration still requires manual intervention.
8300s is expensive gear. I would follow up with sales and see if they can provide a better solution. The money you paid it’s really unacceptable that there is this level of shortcomings especially with something so basic

@Gblenn

Thanks for your reply.
I have two diferent wireguard tunnel instances on my pfsense.
The first instance is running between pfsense and debian servers with a wireguard server installed on it.
The second instance is running between two pfsense firewalls.

The first instance is running fine
The second instance is not connecting.
And i did not see no connection attempt from any firewall.
Thats a bit strange.
Site A

Bildschirmfoto 2025-01-26 um 12.50.35.png

Site B

Bildschirmfoto 2025-01-26 um 12.53.27.png

The Port is the same on both sides. The Port is open and is begin logged.

But i cannot see any connection attempt from both sides in the firewall log.

@IonutIT said in Alias tables don't contain IPv6 addresses anymore:

Make sure after you switch back to ISC to go into DNS Resolver and recheck "Register DHCP leases in the DNS Resolver" and "Register DHCP static mappings in the DNS Resolver" as they were unchecked for some reason after the switch.

Yeah, didn't do that, so that explains it, that switching back made problems for me.

Squid kaldırılması bizim için hiç iyi olmayacak, ağ filtreleme, log tutma, erişim kısıtlama gibi bir çok nimetinden faydalanıyorduk. Şu an güncel sürümlerde hala paketleri var ama ilerde ne olur bilmiyoruz. Umarım alternatif birşeyler bulurlar.

@Mathias-HH You can find the p@sw*rd in this very thread. I have not tested it yet, but I am pretty sure it will work. Just look for a firewall image ;)

@Asmodeus666 hi, did you ever resolve this issue? I'm having the same problem and don't know how to fix this! Any help appreciated

I use it, I mean it is updated so the security issues are gone from it.

@jdeloach Just found it, I am searching for IPv6 only websites, apps, services.

I found this one also..

https://k6usy.net/

The problem with eMMC would hardly ever have occurred if the eMMC size had been chosen appropriately. After all, TBW is proportional to this parameter. Essentially, in this sense, the difference from SSDs is minimal, except for the type of connection and the fact that SSDs can be replaced without hot air soldering skills . What seems most odd to me is the choice of such small eMMC sizes, especially considering that eMMC prices in those years didn’t significantly increase the final cost of the product.