Quote from: nero355 on Today at 07:54:23 PMIt's all a matter of readingYour comment is not nice and not necessary in a helpful context. Please be kind.
Quote from: Patrick M. Hausen on Today at 08:23:06 PMNetflow is a behemoth designed for large ISPs. It will scrub your SSD to death in weeks if you log locally and have some considerable amount of traffic.Good to know! Thnx! :)
The smallest recommended deployment - even for a home lab - for Elastiflow is 4 cores, 16 G of RAM, a couple of hundred G of disk.
They promise the license will be free forever, they just want you to register an account and extend the license once per year. Like e.g. Maxmind, too.
The limit for the free tier is 4000 flow records per second. If you outgrow that, you have bigger fish to fry ;-)
Quote from: stefan21 on Today at 11:42:00 AMDid an upgrade to the latest OPNsense version.That does not mean you had to do this too :
QuoteMigrated to NEW firewall rules.Because it does bring some changes along you might not like and the migration is not something you must do for now !!
QuoteMigrated from ISC to KEA.That's something you could have done in 25.7 too first and then upgrade afterwards once you were sure everything is still working as it should ;)
Quote from: Patrick M. Hausen on Today at 01:36:32 PMDon't save netflow data on OPNsense. Export to a netflow collector like Elastiflow and save your SSD 🙂Looks seriously sweet as far as I can tell from your other recent post : https://forum.opnsense.org/index.php?msg=264974
Quote from: JamesFrisch on Today at 01:32:58 PMSorry, I should have been clearer in my writing. This is not the setting I have, this is the setting my ISP recommends.I see now :)
Here ist the link: https://www.init7.net/en/support/faq/mit-welchen-uebertragungsarten-funktionieren-die-tv-streams/
On the buttom left, you have to activate nerdmode. That shows you the "Rules for multicast streaming" which are the rules I posted.
But it could very well be that these settings are just some old leftovers. I contacted support and asked them exactly this.
Maybe they are long gone to IGMPv3. I would also assume that the mentioned old servers are no longer running, but they are still described there.
QuoteI even tried something similar like you linked. I created a whole seperate VLAN just for the AppleTV Box, but still no luck.AFAIK most modern IPTV setups require Quickleave anyway so I don't see that as being wrong to be honest.
My current setting is this:##------------------------------------------------------As you can see, this is not exactly what my ISP recommends, since it has quickleave enabled.
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint cxl1 upstream ratelimit 0 threshold 1
altnet 77.109.129.0/24
phyint vlan0.51 downstream ratelimit 0 threshold 1
phyint wg0 disabled
phyint cxl0 disabled
phyint vlan0.25 disabled
phyint vlan0.50 disabled
phyint vlan0.52 disabled
...
...
...
Quote from: jonm on Today at 02:39:42 PMThere's a reasonably active init7 sub on Reddit, it may be worth also asking your question there?Aren't there any "German Tech Community Forums" that talk about this stuff very often ?
Quote from: disorganise on Today at 02:45:09 PMHowever, DNS is confusing me in several ways.
First confusion: I don't know what DNS servers it is using, but it doesn't appear to be anything I set.
As far as I understand, I'm using Dnsmasq and Unbound, though I don't really understand the relationship between the two.
QuoteI even migrated to KEA DNS for a bit and moved back when it didn't solve anything.All a matter of reading : https://docs.opnsense.org/manual/dhcp.html
QuoteI have a wireguard set up to another OPNSense 900km away. They each have their own domain; ie, mg.home.arpa and dy.home.arpa.My guess is you told DNSmasqd about it instead of Unbound but again : Read the documentation and go through everything step-by-step ;)
I can't seem to resolve clients in the other domain. I've cheated for the time being by adding my Emby box as a static. On my new box I set a 'Query Forwarding' domain to the OPNSense private IP address in the 2nd location, but resolution doesn't work.
nslookup <client name> <2nd location OPNsense IP> does resolve successfully, so DNS traffic through the tunnel works ok.
Quote from: pseudonym3k on Today at 03:37:04 PMThat's a deal breaker for me then, for unknown reason Unbound isn't stable in my config and that's why it's disabled. (Have whole thread here about it.)Just fix this bug :
QuoteUnbound, PiHole... and I'm not using any of those.By using this : https://docs.pi-hole.net/guides/dns/unbound/
QuoteThank you, had no idea.It's all a matter of reading https://docs.opnsense.org/manual/dhcp.html before making any huge changes to your OPNsense.