@nimrod Cool! When I first did this, the option you showed did not exist. I have not tried this since they are grown now and I don't limit internet this way. Phizix

@stephenw10 yes, static IPs, sending you in DM. please check

@ydderf2426 said in Newbie pfSense user - configuration using DMZ: Created client export leaving selected option hostname resolution with interface IP address value Yes you need to specify the external IP address for server resolution there. Or an FQDN if you have a real host/domain setup.

Bell gives you a PPPoE password when the service is first setup/activated. You can plug that into pfSense immediately without ever having to visit a Bell website or the IP of the GigaHUB. Since the password is limited to 6-8 characters, I'd argue there's no sense in creating a new one - it's not going to be any more "secure" than the original one. :) And this doesn't put the GigaHub into bridge mode. It's still happily doing everything it did before on its own public IP. If you're feeling it, you can continue to use its WiFi as a separate network.

@stephenw10 Thanks :) I have been rebooting between each change. It feels like i've been rebooting all day lol

@cyberconsultants To avoid lockout I'd try to set up rules on each interface, or maybe an interface group if you have a lot. Something like: allow from my_pc to pfsense:443 allow from my_pc to pfsense:22 reject from LAN Subnets to any (rest of LAN rules) Then client devices can't resolve DNS or get past pfSense.

Hi @Gblenn , thank you for your information, I just find out they use a split tunelling VPN .... so some of the software on the work PC pass through the VPN. So that is why Chrome see the Chrome-cast on my Lan. Your right they ca do whatever they want on that PC. The document I saw was not for me to view, it was an error, but I had time to see a quick 2 sec results. Again, thank you for your information. I have my response a long time ago : can we stop this thread now? Thank you all, Richard.

Well I'm not sure why you have the outbound NAT rule on OPT. That shouldn't be required, everything there is routed. But that test is not something I've done with PIMD. I have done it with IGMPProxy and it did work last time I tried it.

It sounds like the /30 CGN subnet is used for transport only and it not routed (or NAT'd) by the ISP. In which case you would need to source traffic from the firewall itself from the public VIP. To do that you need an outbound NAT rule that matches it. An alternative here might be to set the public IP as the primary WAN address wit the CGN address (100.64.136.210) as the VIP. To add the gateway to the WAN you would need to set the advanced gateway option: Use non-local gateway This is a very unusual config!

You should see it reported on the dashboard after rebooting. It requires a SWAP partition to copy the crash report onto though. Does your system have SWAP? How often does it crash? Can you log the console output, assuming it has a serial console?

@SteveITS Cheers for the link, still confused but will give it a go and see where I get to!

Based on my own experience, Wake-on-LAN can be a great thing when it works, but there will always be a situation where this thing won't work under any circumstances, even with the manufacturer's assurances that it should. In my case, it ended with assembling and connecting a PiKVM to the power button, and as a result, I also got a full KVM over IP setup.

If you have multiple downstream subnets on the LAN you will need to add static routes to the mik2 switch and firewall rules on LAN to pass that. The default firewall rules only pass traffic from clients in the LAN subnet directly. Also make sure you don't have a conflict between WAN and LAN. Make sure pfSense itself can connect out from Diag > Ping.

Yes you'll still need to configure VLANs 5 and 6 since they're passed tagged to something external. But WAN, LAN and OPT can just be assigned to NICs directly in the other device.

@stephenw10 Yep, did that and all is working now. Appreciate you help! Bill

It certainly could be a BIOS setting. But try running: sysctl kern.smp

@allkemyst said in Can't connect to 9443 port on a host in the same subnet: Subnet: 20.0.0.1/24 | DHCP4 on while technically that can work, its a horrible idea to use public IP space internally. Not not just 10.0.1/24 as your lan2 network? I try to test the port on PfSense, i can reach the port 22, but can't reach the other ports, including 9443. that screams firewall on that box or your vm host.. To validate this to yourself sniff on your lan 2 interface while you send a test to these ports.. Do you see the traffic leave pfsense, but not get an answer.. But you can ping and ssh works - that screams host firewall to me. edit: or the config of whatever service this is set to listen on IP 192.168.1.x (whatever your old network was) and not 20.0.0.x Unless the traffic is routed over pfsense, pfsense has nothing to do with the traffic - if it is routed, maybe your doing a policy route and this is sending traffic out your wan gateway. Without seeing the rules we really have no idea, maybe you set the rule to allow tcp, but this is udp?

@stephenw10 I tried it, works! Thanks a lot

@JeGr said in Under attack, anything I should do?: I don' even know how that got so famous in the first place! I guess grc.com, Gibson and affiliates. I remember vaguely some talk shows ...

Ok. thank you that was super helpful