Quote from: Patrick M. Hausen on April 16, 2026, 07:50:48 PMYou configured the host header as linked by me and activated that host header in your handler configuration under "Transport"?
Quote from: Patrick M. Hausen on April 16, 2026, 11:15:35 PMCaddy kommt mit sehr vernünftigen Standardeinstellungen.
Quote from: nero355 on April 14, 2026, 04:01:21 PMAre you sure it's not a False Positive ?!Today it's working, so either the node was removed from a list I am using, or I got routed to a different one this time. It's very rare for that to happen so that's why I was surprised.
Quote from: nero355 on April 14, 2026, 04:01:21 PMIn fact when Pi-hole v6.x.x got released somewhere around February 2025 I was seriously 'STOKED!' as they say :
- No more LigHTTPd.
- No more PHP.
- CivetWeb does almost everything now and is part of the whole FTLDNS package.
- C++ is now the way forward.
- DNSmasqd is ofcourse still part of FTLDNS.
- The API is also still available.
- Super Sweet New webGUI that's a 1:1 translation of the pihole.toml config file which is in a league of it's own when you see how nicely commented it is via SSH when you edit it via nano or vi :)
Quote from: viragomann on April 16, 2026, 09:28:49 PMI presume, your clients and servers have internet access?Yes they both have internet access, I just tried completely disabling the firewall on my server (systemctl disable firewalld.service and rebooted) but my desktop still can't ping the server
Consider that the devices might run their own firewalls, which usually blocks access from outside of their subnets. If so you need to configure them properly to permit access from the respective other subnet.
Quote from: nero355 on April 16, 2026, 10:13:34 PMWhen you install OPNsense the Default LAN has Firewall Rules that ALLOW traffic to ANY destination.Thanks for the tip, I recreated the original LAN rules so on ipv4 and ipv6 (although I don't use v6) allow any protocol from the LAN to any destination and the same for LAN2, but still can't ping or access any other ports on the server and the server still also can't ping the 192.168.1.1 gateway. Maybe I didn't create LAN2 properly? Basically to sum up what I did to create LAN2 is in interfaces I assigned igc2 to LAN2 enabled LAN2 and set the IPv4 Configuration Type to static ipv4 and gave it the ipv4 address of 192.168.2.1/24 in services under DNSmasq DNS & DHCP I added LAN2 to the interfaces in general, added a DHCP range and that's it. If there is any other configuration that I have missed to get different LAN's and or VLAN's to be able to communicate with each other please tell me
If you then create your LAN2 correctly as the next step, you could then copy that firewall rule from LAN to LAN2 and have two networks that can talk to each other.
Quote from: meyergru on April 16, 2026, 10:40:21 PMI assume you want to set up a bridge with LAN and LAN2. Follow the Offizials docs, them it will work.I believe I don't want to use a bridge, since that would place all devices on the same subnet. Instead, I'd prefer to restrict communication so that only a few specific ports are open between my desktop and the server—and similarly for my phone
Quote from: Patrick M. Hausen on April 16, 2026, 11:17:26 PMThere are tools like ntopng or netflow that give you the observability you'd like.I will take a look at these. Thanks.
Quote from: viragomann on April 16, 2026, 11:12:54 PMAutomatically, without any specific setting?