@jasonsansone I just acquired a sg-3100 and currently struggling to identify how to implement the hardware. Preferably I would rather replace the Pace hardware from AT&T with the 3100. Note: Currently, I have the Pace in use with a netgear router in bridge mode.

Traffic is neither passed nor blocked. It is matched. You can do things like assign a queue or a tag or log it but it does not change the pass or drop status of the traffic. quick has no bearing on match rules. They always flow though and rule processing continues.

have you checked the wan drivers ? Idk, I have never experienced anything like that. I am playing a lot of CS GO and everything is fine. I am sure that there is a software problem, maybe you should reinstall the drivers. By the way, when you will solve that problem, we could play together a couple of games. If you have a very low rank it's not a problem, you can always use a rank boosting service like eloboss.net. If you are interested, leave me a message! It's going to be really cool! I am waiting for your message, dude!

The driver built in to FreeBSD for Realtek chips will crash under load. You can use the latest official Realtek driver to achieve stability, but if you already got Intel cards you're better off anyway.

A device with a Celeron CPU and 8 GB of ram wouldn't be my first choice to install a hypervisor on. Not to mention, the Realtek NIC's aren't doing you any favors either. The first thing I would do is install PFsense on bare metal and blow Proxmox away. Also, if that ZBOX is modular, grab some Intel NICs.

@iberiaerik did you reboot the firewall since enabling the proxy? I believe this is required.

@beria-pl said in Issues after upgrade 2.4.4p3 to 2.4.5: @bmeeks Thanks - works like a charm, after setting up 1 vCPU on both. At least it working now for 30 minutes without any issues. Is there any timeframe to expect this fix? Or in longer-term it may be better to wait for 2.5.0p1 ;) and now survive with 2.4.5 or downgrade to 2.4.4p3 ? I am not privy to the release dates as I am not affiliated with Netgate. As with pretty much every software company out there, Netgate is usually tight-lipped about release schedules (at least ones with very specific target dates). I suspect companies do this to minimize flak in the event they miss the release date due to unforeseen issues that may crop up. I personally don't expect a long delay in the 2.4.5-p1 fix for this issue, but whether that is later this week or several months from now, I have no idea. If one virtual CPU appears to be working for you, then I would suggest staying on the 2.4.5-RELEASE and not moving to 2.5.0-DEVEL as that branch understandably may have issues crop up -- especially if you keep up with the snapshot updates. The upstream FreeBSD guys merged the fix into FreeBSD-11.3-STABLE on May 11th, and so far as I can tell from the Github updates, the pfSense team is keeping up. So maybe the fix release won't be too far away.

Restarted the Virgin Superhub 3 last night and it's great again, we monitor again, but it will start to degrade later today or tomorrow as others have mentioned. If I set back to just use their Superhub as an all in one again all is fine, it has to be something to do with the hub in modem mode and the way it talks to pfSense.

Sorry for troubling you guys. I got it solved by adding following line to the moodle config file. (Instead of using a hardcoded IP) $CFG->wwwroot = $_SERVER['REQUEST_SCHEME'].'://'.$_SERVER['HTTP_HOST'].'/lms';

@Rico Thanks.. I saw LAN when I read the OP the first time. ^^ what Rico said. :)

you welcome bro :-)

@stephenw10 Ah gotcha. I'll stay tuned for the 2.4.5_1 release. Thanks!

@YannTKO I had it on wan! ive changed the rules to lan thanks lol

@JKnott I now have a stratum 2¹ server on my pfSense firewall. One thing I've noticed since switching from pool.ntp.org, is that the clock on my computer appears in closer agreement with a WWVB radio clock I have. When I was using pool.ntp.org, my computer seemed to lag the WWVB clock by a half second or so. Now it appears the same, at least as close as I can tell by eye. pool.ntp.org provides stratum 2, which means pfSense provided stratum 3. TorIX provides stratum 1, so pfSense can be stratum 2.

@johnpoz said in Not all devices are listed in DHCP: If you just pinged it from pfsense, it would be in the arp table!! it worked Thanks

if there are no other alternatives to edit xml file exported, e.g. with 'sed' command directly from the console, I can try only this way best regards, thanks!