hi kapara could you be more specific for your statement : If you want to take it to the next level you can installpfsense directly on the host machine.... Do you mean instaling pfsense directly on a physical machine ? Is this feasable when using OVH vrack ? thanks Stephane

I don't use pf-sense beyond what the dafault settings are and when setting up the firewall threw the inital configuration wizard the only thing I changed was the DNS as I selected to use my own. I dont have to much knowledge in particular about pf-sense and everytime I have made changes you can guarantee I have borked my set-up . When I installed it, I was curious about the home lab aspects of it and it works don't get me wrong and I use it daily when I'm using my systems as my servers up most of the time.

What version of pfSense are you running? If you are not running the latest 2.4.4 version, you can't upgrade/install the latest packages due to a PHP 7.2 dependency. If you are not already running pfSense 2.4.4, remove all packages, upgrade to 2.4.4, and then reinstall your packages.

It seems somehow the shellcmd was in the config.xml twice in different places. Removed them both and just left the crontab entry so it starts up a minute after booting. Not ideal, but it may be the only way as it seems there is a conflict with pfSense executing the shellcmd too early before everything else has finished starting up. I'm guessing one option may be to have the shellcmd script look for the booted file to appear, like pfBlockerNG does, before actually starting the script. Its all very odd as it was working perfectly months ago, I can only assume either pfSense made some tweak in when the shellcmd is executed causing it to hang like this due to starting too early, or I was using some alternative way of starting the script on boot (I lost that old config so not sure). Its baffling as surely shellcmd should be the vast last thing to execute once everything else has finished, not half-way through the boot process. Seems a very questionable choice if your startup script can hang the boot process. They certainly don't seem to document all changes, possibly because some things are happening upstream in FreeBSD itself. I noticed after the upgrade to 2.4.4 I'm using a lot more RAM, I think its related to zfs as before it was detecting I had less than 4GB RAM so disabling some functionality, perhaps now its ignoring the RAM allocated to the integrated graphics so acting like I have 4GB RAM (which I do minus iGPU). But I digress.

@stephenw10 @bootable Thank you. Very sorry for late response. Currently I cant try because We have only 1 ISP and second ISP we are yet to buy. So I understood that I can use Gateway Group and with 1 Instance I can use 2 ISP Gateways. May be with in 1 month we will procure 2nd ISP and I will ask any queries at that moment. Thank you once again. Lokesh Kamath

Before you attempt to submit a bug report, please discuss it here on the forum first. That way we can be sure it's a legitimate bug with enough detail for developers to investigate. Start a new thread in an appropriate category and explain the problem in as much detail as possible.

I see. I know PHP has come a long way with 7 and was curious if that had changed the plan. I'm a Python/Flask fan, so happy to hear it's still in the long term plans.

But you can ping the pfSense interface address? Something's not right there then. Do you actually see the phones in the DHCP lease table? I'd try running a packet capture or at least checking the state table when pinging from the phones to see what's actually being sent. Steve

So I finally got around to doing some testing with my setup. To quickly summarize: (2)ESXi hosts (9) total NIC's to use Want to setup different networks to keep them separate (work, dev etc.) I have done quite a bit of reading on vmware networking (still wrapping my head around it) and setup some distributed switches and port groups, per this thread. I deployed pfsense as a VM and added the interfaces that I attached to it in Vcenter (LAN, DEVVLAN, DEVHOME). I configured IP's on the interfaces, I can reach pfsense just fine from my PC, but having problems with the VM's attached to specific networks to get a IP from pfsense DHCP server. My PFSense has three interfaces: LAN: 192.168.55.1 DEVLAN: 10.0.3.1/24 DEVHOME: 10.0.2.1/24 I am testing with one VM right now, attached to the DEVVLAN. Before I go to far down the rabbit hole, any suggestions on where to start troubleshooting? I tried to manually assign a static IP to my test VM, but I can not ping the gateway off the pfsense box on that interface (10.0.3.1 in this case.) Thinking through this, I have not done any configuration on my 24 port switch, so to my knowledge, the ports the esxi NICs are plugged into are still native 1. My brain is hurting right now, so going to take a step back and rest. I appreciate all the help. Cheers, TCG

I switched the config to http There is your problem. Never do that. Keep it on HTTPS. Beyond that it's a browser issue local to your PC.

Today. :-) https://www.netgate.com/blog/pfsense-2-4-4-release-now-available.html

Mmm, not sure why you would do that. Just leave it disabled for an always-on connection. That how to is for a much older version. The setting is still useful for cellular connections where you are using expensive data just being connected for example. Steve

@stephenw10 Thanks for your response. I do have the package installed.

@rico I had a similar issue. Thanks for your advice!!

@viragomann said in Bridging two networks: So I assume you have a setup with LAN configured and accessing the web configurator via LAN. As far as I know a restart was necessary after that to get it work. I tried both - accessing from this "LAN" interface and from other interface. I also tried assigning bridge to "OPT2" instead of "LAN" as you suggest and did reboot pfSense, but that didn't help. @derelict said in Bridging two networks: Did you then move your management device to OPT1? That would be the only port on "LAN" at that point. Yes, it supposed to be accessible via 192.168.1.x, but I can't access nor ping it. Could problem be that one of these two LAN networks is at virtual port (between pfSense VM and host machine)? I also tried adding only 1 physical port to this bridge, but still can't access it.

To expand on @heper: Yes, pfSense will do this.