@jimp:

@jimp:

I need to fix Easy Rule so it can find the openvpn ruleset properly.

FYI- This bit should be fixed on new snaps. I just committed a fix.

Easy rule works, but OpenVPN packets still be blocked by "default rule":
  block
Feb 17 16:36:55 ovpns1 192.168.220.6 192.168.200.2 ICMP

Looks like the 1.2.3 machine needed to be rebooted - appears that there's a bug (or at least unexpected behavior) regarding OpenVPN-interface assignment and filtering.  After the reboot of the 1.2.3 machine, everything works more or less as expected.

@overand:

Worth noting - the 1.2.3 machine may have had firewall rules enter into a temporarily-defined "OPT" interface associated with "TUN" - and may not have been rebooted since.  (That is likely my nest section to check out)

For anyone doing a search on this in the future,  I can report success with my Novatel U727 USB gizmo - configured with SPRINT - though I had to select "Verizon" as the configuration type.

I also believe I ended up selecting some profoundly low connection rate, like 19200 - It "seemed to work better" like this, but given the flakiness of 3G, I'd have to prod that a lot more to have any sort of certainty.

What's interesting about this 3G interface is that on Windows and Linux, it appears as a CD-Rom drive (containing a "CD" with windows drivers) when first inserted, with a USB ID of (something-I-forget) - after you "eject" the CD drive, the device re-presents itself, with a new USB ID.  With linux-based workstations or router platforms, I've had to "manually" (or script-wise) eject the "CD" before setting up the "airprime" module or connecting.

FreeBSD or pfSense appears to be doing the magic for us - which is quite awesome.

(If anyone has tests they'd like me to perform with this device, let me know!)

Thanks for the fix. I just upgraded to the latest Feb16 snapshot and all of my widgets came up. :)

After fixing the bug I found here:
http://forum.pfsense.org/index.php/topic,22321.msg118156.html#msg118156

I tried to paste in your widget tag on my install and everything worked as it should. Hopefully that was the root cause of this one as well.

OK, I found the bug and it should be fixed now. (Or in snaps later that this time, or if you gitsync)

Whoops. Should be fixed now.

Well it seems you're luckier than I am :)
I could't even install snort-dev, it throws and error when searching for dependencies. After that it shows like it's installed and won't let me uninstall nor reinstall it.

Thanks to you both for the clarification.

Squid isn't developed or maintained by us ("us" being those who work on the base system). dvserg said he'll fix it at some point. As for any enhancements, he'll have to answer that.

The em driver problems appear to be gone since switching to RELENG_8 and adding a couple patches to fix edge cases like lagg.

The cryptodev patch you linked is nearing 5 years old, and on a file that doesn't even exist in RELENG_8. Doubt it's applicable anymore. Last I tested, with 7.2, every algorithm we support was properly accelerated. It's not that much of an improvement with glxsb, though the hifn cards are considerably faster.

Four ports on bsd/pfsense. /dev/cuaU0.0, 0.1, 0.2, 0.3 (in addition to the 2 integrated rs232 ports that show up for the host box itself(/dev/cuau0, 1))  More show up when attached to a windows box.  It is a Sierra Aircard 881 (cardbus) model.

This already exists in 2.0. See the "Additional BOOTP/DHCP Options" choice. You can add any numbered option you like.

I believe this was already noticed, not sure if it's had a fix yet.

I'll give the newest snap a try on my ALIX and see if I can figure out what's wrong, unless it's already been fixed.

That's how it should work, just means it was returned from cache.

confirmed.
http://redmine.pfsense.org/issues/show/354

Confirmed. http://redmine.pfsense.org/issues/show/352

Well, the button is back where it should be, the error is gone as well, so I think this is a Firefox 3.7a2pre issue. Please disregard. :)

"at some point" is the best timeline you're going to get.  The focus is on fixing bugs with 2.0 and getting it into shape for release candidate.