Recent posts

#11

High availability / Re: CARP - Preventing individu...

Last post by browne - Today at 10:30:27 AM

Alright, thank you very much for all the effort you put into it and even looking into it in the first place.

i was thinking of a ping using only the pfsync interface, but i havent thought about what would happen if only the pfsync interface would fail.

This is solved for me now. Again thank you very much.

#12

German - Deutsch / Re: OPNsense VM klonen, irgend...

Last post by meyergru - Today at 10:00:53 AM

Ich verstehe unter "Klonen" die entsprechende Funktion der Virtualisierungs-Software, beispielsweise PVE.

Die klont typischerweise die gesamte Maschine, inklusive der virtuellen Platten, bei Beibehaltung der Plattengrößen. Und dabei spielt das Dateisystem darauf keine Rolle. Was allerdings aus Sicherhetsgründen meist gemacht wird - damit die neue VM keine Konflikte hervorruft - ist, die MACs der NICs zu randomisieren.

#13

26.7, 26.10 Series / Re: No link with Intel E810 on...

Last post by redge - Today at 09:59:25 AM

The DEC devices carrying E810 25G ports were tested extensively with multiple modules going from 26.4 -> 26.10, tests passed just fine. Seeing the reports makes it likely the link partner plays a role in combination with the updated DDP package. We've seen at least one case where setting the mentioned tunable will cause a link down on 26.4, this is why it can't be set generically.

The options are:

dev.ice.X.requested_fec=auto
dev.ice.X.requested_fec=none
dev.ice.X.requested_fec=rs
dev.ice.X.requested_fec=fc

When using short range (SR) fiber, "fc" seems to be the right value, when using long range (LR), it's likely "rs".

I don't have any further insight or experience to contribute at this stage, but what module coding and link partners have been tested? We don't have a non-production DEC appliance, but we do have DACs, AOCs, and SR/LR SFP28 modules on hand that we can recode at will, so if there's a specific combination that hasn't been tested (or needs validation) I might be able to provide another test case.

#14

German - Deutsch / Re: Performance verbessern

Last post by sternchen45 - Today at 09:47:27 AM

single-threaded bedeutet, dass alles auf die Performance *des* einen Cores begrenzt ist, der die Arbeit macht. Völlig egal, wie viele Cores die CPU hat. Das schreibt der Hersteller übrigens auch selbst als Hinweis.

#15

German - Deutsch / Re: OPNsense VM klonen, irgend...

Last post by sternchen45 - Today at 09:45:30 AM

erwähnenswert wäre vielleicht noch, dass meines Wissens nach nur sektorweises Klonen geht, ohne Unterstützung der Dateisysteme (UFS, ZFS), d.h. der Zieldatenträger muss zwangsweise mindestens so gross sein wie die Quelle (es sei denn, man hatte schon beim Anlegen der Dateisysteme mit dem Hintergedanken deutlich kleiner partitioniert).

#16

26.7, 26.10 Series / Re: No link with Intel E810 on...

Last post by tuto2 - Today at 09:09:50 AM

The DEC devices carrying E810 25G ports were tested extensively with multiple modules going from 26.4 -> 26.10, tests passed just fine. Seeing the reports makes it likely the link partner plays a role in combination with the updated DDP package. We've seen at least one case where setting the mentioned tunable will cause a link down on 26.4, this is why it can't be set generically.

The options are:

dev.ice.X.requested_fec=auto
dev.ice.X.requested_fec=none
dev.ice.X.requested_fec=rs
dev.ice.X.requested_fec=fc

When using short range (SR) fiber, "fc" seems to be the right value, when using long range (LR), it's likely "rs".

#17

Zenarmor (Sensei) / Re: CPU spikes from Elasticsea...

Last post by mlenje - Today at 08:14:04 AM

Heard back from Zenarmor after the 2.7.2 update... "this got pushed to 2.7.3 because of the urgent fixes in 2.7.2"

#18

General Discussion / Re: Anyone installed mdns-brid...

Last post by maplecrane52 - Today at 07:50:12 AM

The mdns-bridge package seems to be a feature-complete and up-to-date implementation of mDNS forwarding across interfaces for both IPv4 and IPv6. It handles only mDNS as opposed to the general-purpose (and IPv4-only) UDPBroadcastRelay, but at least it should make it easy for mDNS. It's getting harder to live without IPv6 nowadays, due to IoT gadgets, Apple and Google insisting on it.

There's no OPNsense plug-in for it, but it is in FreeBSD ports, so it should be ok to try. Anyone have any experience with it on OPNsense 25.7 or 26? Just looking for any concerns before I end up flooding everything :-)

I'd be more wary of the interface filtering than raw flood risk, mDNS gets noisy fast once multiple VLANs can see each other. The IPv6-only gap in UDPBroadcastRelay is exactly why this package looks tempting though.

#19

26.7, 26.10 Series / Re: KEA DHCP to Unbound DDNS P...

Last post by Monviech (Cedrik) - Today at 06:35:52 AM

For home use I would have expected dnsmasq:

https://docs.opnsense.org/manual/dnsmasq.html#dhcpv4-with-dns-registration

#20

General Discussion / Re: Anyone installed mdns-brid...

Last post by Pat.Ryan - Today at 06:34:44 AM

I'm not specifically using this for IPv6 but I do have it running on v26.7. I had previously used this on pfSense but have switched to OPNsense now and was missing this. It installed fine but outside of the OPNsense GUI.

I am working on a plugin for this and am nearing completion. I have the GUI working and am able to configure / reconfigure the mdns-bridge from the GUI. Next steps are to finish the package creation and submit to the OPNsense group to get this added as os-mdns-bridge.