I dontknow whats the difference between mask on pipe and mask on queue when using round robin. I dont see any difference. Probably ive set something wrong.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: BrandyWine on September 25, 2025, 06:42:29 AMQuote from: Siarap on September 24, 2025, 11:29:36 PMI got important question. What if malware starts using dns over https?This nat trick is in another thread, I have to find it.
You add a NAT rule as a WANout rule, src-any dst-any dst-port tcp/udp-53, nat dst-IP to 9.9.9.11
You do also want your std access LAN rule for dns, allowing your LAN net to 9.9.9.11 tcp/udp-53
Quote from: allenlook on September 25, 2025, 02:15:52 PMHow is your Maltrail configured now, e.g. are you using firewall rules to block packets on WAN and LAN, IN and/or OUT, and on which interfaces?
Quote from: meyergru on September 25, 2025, 08:39:53 AMWell, "solved" would be to find the root cause and eliminating it. As long as you have infected clients in your LAN, this is not over. Even more so with the observation that already, multiple trojans seem to have invaded your network and it seems not to be segmented into different levels of security by VLANs. Such as it is, the bots are free to spread in your network - you just do not see that any more.
Quote from: BrandyWine on September 24, 2025, 10:50:00 PMQuote from: meyergru on September 24, 2025, 07:11:11 PMAre you sure about that? When your internal clients use DNS via port 53 to a specific DNS server, then obviously those requests go via the WAN IP via NAT. It seems ~10x more likely that some client has been infected than OpnSense...Yep.
This is why it's best to dst NAT (WAN out rule) any outbound DNS to 9.9.9.11 or the like. Because OPNsense has that default "allow from self", so to protect against self (malware) using some other DNS that would return malware IP from query, forcing it with NAT to a malware blocking DNS service would help. Not 100%, but helps.
All DNS settings should be using malware blocking DNS service, and, WAN out NAT rule to force all DNS to a specific server, even if it's the same as dns from dhcp or hard set on hosts.
Quote from: Patrick M. Hausen on September 24, 2025, 09:43:06 PMPlease attach on this forum. I block external image hosting sites.
Quote from: Patrick M. Hausen on September 24, 2025, 09:07:55 PMQuote from: Siarap on September 24, 2025, 08:56:02 PMALL ports closed. Im just gamer no need to open ANY ports. Im not hosting games.
Then nobody can possibly have infected your OPNsense directly from outside. From inside via a previously infected client - yes. But as @meyergru wrote: highly unlikely.
Turn on the query log for whatever you use as a recursive server on your OPNsense, watch them, try to find the source of the queries step by step. Only method. No silver bullet.
If you want more help let's start with you describing your DNS setup in detail. Which servers - Unbound, DNSmasq, Adguard Home ... to which ports are they bound ... how did you configure DoT ... how exactly (show the firewall rules!) did you make sure clients cannot go directly to the Internet ...
The problem is - you probably think there's something obvious that experienced people like @meyergru and me know. Fact is, there is nothing obvious. It's all 100% particular to your specific configuration. When trying to help we build a mental image of your network (lacking real access). For that to be successful we need all relevant information.
Quote from: meyergru on September 24, 2025, 07:11:11 PMQuote from: Siarap on September 24, 2025, 06:45:20 PMThis connecions was made from WAN ip adress not from lan.
Are you sure about that? When your internal clients use DNS via port 53 to a specific DNS server, then obviously those requests go via the WAN IP via NAT. It seems ~10x more likely that some client has been infected than OpnSense...