Excellent!  I reverted usr/local/www/widgets/widgets/interfaces.widget.php back to the way it was before those changes and now the widget displays correctly (see attached).

I'm definitely not the right person to comment on what is right syntax or why that change was committed in the first place.  But, it does mess things up a bit.

Thanks


As the OP: Thanks for revisiting this old thread.

Due to a firmware update for the SIP device I was using, it is now aware that's it's behind a firewall and I don't need the siproxd package anymore.
But as others probably will: thanks for the update.

Richard

@filnko:

although the default gateway get's set to the IPSec connection. (OS X Mavericks)

Can you show your IPSec config more detail? What do you mean "OS X Mavericks" here?

So be sure to wait for a new snapshot before trying a remote update!  Glad I checked here before updating today :)

Looks like Renato's already on it:  https://redmine.pfsense.org/projects/pfsense/repository/revisions/9da083fc4d3a09b7a0b602088db9878c8c392773

I made the edit to util.inc and backup and running now.

Works here on i386

A new version is now available Current version: 2.2-BETA       Built On: Fri Sep 19 23:33:28 CDT 2014     New version: Tue Oct 07 21:47:40 CDT 2014   Update source: http://snapshots.pfsense.org/FreeBSD_stable/10/i386/pfSense_HEAD/.updaters/

@thetallkid:

All working now after a clean reinstall. Also cleared up a few other problems i was having.

Great to know it is working - I was wondering if there was going to be some other obscure edge case that the code did not handle.

@ermal:

The ipsec issue should be fixed now.

Great news! Thanks for fixing this now I can really test this out on hyper-v the way we need it. When do the snapshots get pushed?

Edit
I think its posted…does the 10/7 build include the fix?

EDIT 2
Yep working now!!! Thanks again!

No no , as far as l read , there are enoughth people who were able to get dual band to work at the current stable releases. if you have a wifi card which is supported by pfsense it should work. I think / hope that this is just a problem of the current beta. In some how to's it is shown that dualband is working with pfsense. to far as I understand them you should use the card as an 2.4 wifi and then one virtual interface as 5 GHz wifi. But they are all for older versions of pfsense . And the update from 2.1.5 to 2.2. is quiet a big one.

@Wolf666:

@bmeeks:

@mais_um:

Hi

Working file but Suricata still doesn't support PPPoE interfaces yet.

Correct.  PPPoE support is a limitation within the Suricata binary itself and will require a patch.  It is actually not supported on any FreeBSD derivative at this point (by Suricata, I mean).  I plan to look into what it would take to create the required patch and then port it upstream into the Suricata source code tree.

Bill

Hi Bill,

is it confirmed that the following changes make Suricata works with PPPoE?

suricata.yaml:

pcap:   - interface: physical interface (ie. em0, igb0 etc etc)        checksum-checks: auto     promisc: yes

Thanks

No, this is not an officially sanctioned fix.  While Suricata will then not complain, it can still get confused by the PPPoE frame header that will be present.  It will work sort of, but not 100% correctly.  What this does is tell Suricata to treat the PPPoE data link as a physical Ethernet interface.  Physical Ethernet interfaces are not expected to contain PPPoE frame headers, so they can confuse Suricata.

Bill

Yep… I'll confirm the same. I went ahead and tried it with no issue. Thanks!

Yes - That will get you comcast DNS

Just a quick update - pretty sure that this is not running because Perl is not working…