I'm not familiar with pppoe so I can't speak to that part, but what I always recommend to people starting out is to keep it simple. Just get default OPNsense working with WAN and LAN only. Don't worry about all of the extra functionality or network options.Once you have a basic setup working to replace your consumer router, then you can slowly expand and experiment with things one piece at a time. If something breaks, you can easily restore the old config, even if you need to completely reinstall.
I tried and got it working (only lan and wan) when I was tagging the router ports and not using a switch. Also my firewall rules where allow all When I tried to bring the switch into the game and incorporate some VLANs hell broke loose.
Quote from: panseit on March 01, 2024, 12:46:30 amI tried and got it working (only lan and wan) when I was tagging the router ports and not using a switch. Also my firewall rules where allow all When I tried to bring the switch into the game and incorporate some VLANs hell broke loose.If your firewall rules are allow all, I would say you didn't have it working. It sounds like you're still trying to do too much at once.Also, you should be able to use the switch without VLANs to start and then add them slowly as you verify things are working.
what's your DNS question?
I like HNG, but I feel like his guide to setting up OPNsense causes people more problems than it solves. I suspect he realized this as well since he created a simpler one. https://homenetworkguy.com/how-to/beginners-guide-to-set-up-home-network-using-opnsense/This is why I recommend people to do things in stages, via small discrete steps. This allows them to get familiar with things before moving on to the next piece to learn.
answer is: it depends.Like CJ wrote, your initial post is super convoluted. It's now unclear to me what is being setup and therefore what rules might be needed. I thought you were going to be without VLANs to begin with.If going with VLANs, then the default allow rule will allow the queries from clients to get to Unbound listening on all interfaces. Have you tested it? You don't need to add firewall rules if you enable DoT on Unbound.
1. Seeing this guide (https://forum.opnsense.org/index.php?topic=21207) I see that he has assigned WAN completely different than mine (assigned it to physical and vlan). Is my assignment correct or wrong?2. Firewall rule to allow one PC that belongs to VLAN 20 and has static IP (192.168.20.20) to be able to manage LAN devices (switches, router) and the Grandstream that belongs to VLAN 30.
Quote from: panseit on March 01, 2024, 07:22:48 pm1. Seeing this guide (https://forum.opnsense.org/index.php?topic=21207) I see that he has assigned WAN completely different than mine (assigned it to physical and vlan). Is my assignment correct or wrong?2. Firewall rule to allow one PC that belongs to VLAN 20 and has static IP (192.168.20.20) to be able to manage LAN devices (switches, router) and the Grandstream that belongs to VLAN 30.1. That link is for an ISP that provides different services on different VLAN tags. If yours requires only one tag for all, your good if you get services the way you have set it up.2. You need a firewall rule on interface VLAN20, direction IN, destination Any.