Quote from: opnsenseguy on Today at 06:25:41 PMwould rather have equipment that I can replace individual components.Then why the
QuoteA. Intel onboard NIC. Bonus points for two!?!
QuoteB. I do have SFP switch so can use SFP so any particular cards recommended?That would be Intel too, but considering :
QuoteC. Power consumption - This is going to be on 24/7. On my current setup the CPU of the Proxmox server running 3 other VM's doesn't ever hit 2% (12th Gen Intel i5-12400).You might want to avoid that ?!
QuoteAny motherboard recommendations?For some time Fujitsu motherboards were very popular for low power consumption setups.
Quote from: JoeFromNowhere on Today at 09:08:17 AMWAN1 : 7Gb/s fiber connection with a 4G backup behind that switch automatically to 4G if fiber is down.Is that the same device or do both at least have a different Gateway IP Address ?!
Quote from: viragomann on Today at 04:56:14 PMI've added all my interfaces to an interface group, called it "Internal", where I've defined common rules for DNS, NTP and alike.I wonder, if I could also do some more rules on such a group like block RFC1918, allow internet and do those as non-quick. Then I could create some local quick allow rules on the single interfaces...
Quote from: Ratfink on Today at 03:12:09 AMRep dropped the ball, bad communication, etc...Also been there with an old Businesses only ISP and know what that feels like... :(
Quote from: mooh on Today at 04:34:32 PMAlternatively, creating more specialised rules for every interface would be a pain.TIP : Create those Firewall Rules and then clone them to another Interface and see what happens! ;)
Quote from: bob9999 on Today at 04:17:30 PMI fixed the adguard home access problem by editing its configuration file, adguardhome.yaml. I gave it a different administrative port. The accepted standard is port 3000. Apparently, that port conflicts with some aspect of the setup of gateway groups, according to some search engine research. Wikipedia says the port number I gave it is unused.Technically port 3000 is in the so called 'Registered Range' and only the ports above 49152 are all completely 'Dynamic' so that sort of thing can happen indeed...
QuoteIt still fails with DNS access. Even after a router reboot. Everything returns to life after I back out the changes to the rules.Makes sense if you read this : https://docs.pi-hole.net/guides/dns/unbound/#what-is-a-recursive-dns-server
Although Adguard Home as a DNS forwarder works very well. My DNS queries are in the 12 ms range consistently.
Using Unbound as a forwarder to the DNS servers on the main system setup page, the queries were in the 20 ms range or slightly better.
Using Unbound only, the queries were in the 30 ms to 50 ms range.
That was a surprise as I always believed Unbound was a sort of superior standard.
QuoteI fail to see how Unbound is 'superior', which I also believed until I went through all this.IMHO you simply need to take it away from OPNsense and run everything on a seperate device : Raspberry Pi/Intel Atom NUC or Proxmox VM/LXC and you will be a lot happier :)
Quote from: viragomann on Today at 04:56:14 PMAnd yes I've forwarded DNS and NTP requests to the loopback address. This means, you can also use the interface group in port forwarding rules.I have been doing the same. One minor gotcha I encountered, some pre-existing rules allowing access to locally hosted services by way of an RFC1918 alias, had to be updated. Otherwise it seems a robust technique and served as a workaround for issues I've had in the past where a service was just not listening on all interfaces despite setting it as such. This wasn't in opnsense BTW.