See that rule there in your floating - its forcing traffic that is TCP, ie http or https out your gateway. So no your not going to get to your other vlans. See the bypassing policy routing section here. https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html#bypassing-policy-routing You need a rule that allows the traffic to your other vlans - before you shove traffic out the wan.. Which isn't going get your vlans.

@kom thank you

@viragomann said in Can't Hit Port Forward From Inside LAN: not necessary to enable it for a single forwarding rule Did not realize that, thanks.

@perphide Something strange just happend. I disabled IPv6 and all of a sudden I can ping the IPv4 address of the vmx0.10 interface. I am sure this has nothing to do with IPv6 being disabled. I have no clue what just changed. Perhaps another pending setting has been applied by this action?

I create in Vm a windows server 2012r2 and I set the hyper V. Then I create 2 virtual switches one external and one internal. I create a vm in hyper v for pfsence and when Istart the installation I try to configure a WAN 192.168.1.25 4 subnet mask 255.255.255.0 and when I set LAN 192.168.100.1 it tells me not in subnet

Hi Steve, Thanks so much for the quick response here. This issue has been solved. It was definitely a turn it of and turn it back on again issues. So sorry about that rookie mistake. I just had to reset both the modem and pfSense in the correct order. Once the devices rebooted and everybody got new addresses it all started working correctly. I am just getting started on this journey. The next step is for me to add a consumer wifi router behind psSense. If you have any tips or links for that let me know. Otherwise, thanks again, and have a great day!

@zkab said in WhatsApp call on mobile: Thanks ... I skipped Whatsapp and use Signal now. Hahaha this is a SPAM suspicious stuff.... (the OP has only been registered for 3 hours) But we agree on Signal

@steveits Yes, pfBlockerNG-devel definitely is what kills things for me too. This Redmine report was opened a month ago. Very frustrating.

You'll be needing some pfSense package upgrade troubleshooting. So, here you go : pfsense package upgrade troubleshooting But, it's actually a good thing you can't see packages, as you are not 'allowed' to install or upgrad ethem anyway. As per ANY pfSense install notice : https://www.netgate.com/blog/pfsense-2-4-5-release-p1-now-available.html : Read the "Upgrade Notes" => 'Do not update packages before upgrading pfSense!'.

@jimp Thanks for the reply!

@devey I hope others more knowledgeable would chime ... all I can think of off the top of my head is use a USB key in conjunction with certificates to be able to manage the group without system admin privileges

In bridge mode it would only expect one device I imagine. It could have been handing a public to one of those other devices. It's more likely though that the OpenVPN connection was causing an issue if you're using that as a WAN. Especially if it's the default gateway. Anyway glad you got up and running. If you're connected over VDSL2 without g.fast then you won't see any benefit to going to a 'modem' with 1G ports. You will never pass >80Mbps anyway. Steve

@axala said in Login pfsense 2.5.0 amd64: 192.168.1.1 is my isp provider box adress As you will be using your ISP router as a 'dumb' upstream router, change its default LAN network 191.168.1.1/24 to something else, like 192.168.100.1/24. Will doing so, check also if its DHCP server changed accordingly, the pool should be in 192.168.100.0/24. Now you can use the "192.168.1.1/24" on your soho network, as before. @axala said in Login pfsense 2.5.0 amd64: I have access to graphical interface in the console That's new to me. The console is text based only.

@gertjan Thanks for your quick response You Are completely Right Thanks very much

FWIW we just switched to MintMobile two months ago from Consumer Cellular, Mint rides on the TM network. I use WiFi calling all the time in the house and never had an issue. here’s my settings Outbound NAT Mode is set to Automatic outbound NAT rule generation. Firewall Optimization Options – Conservative Disable Firewall Scrub – unchecked Generally I wouldn’t even be in the advanced section but a few years ago on the previous ISP we were having issues with VoIP call quality and I read somewhere to change a few pfsense settings, as I remember the Firewall Optimization Options was one on the tweaks. Looking back I think the issues were with the prior ISP itself. Anyway we switched ISP’s again last June and never bothered to change that settings. Using a Linksys EA8500 running dd-wrt in Access Point mode and I have an Samsung 2017 Galaxy J7 connecting on the 2.4GHz band.