scp works fine when you connect as root. The menu does come up when you login as root but the root account is not locked into that menu the way the admin user is.

I already got rid of them, even the auto-update copies.

I'm rebuilding the ports on the builders and then I'll start a new run, hopefully that does it. I rebuilt two ports on their own before those snaps came out, so this should fix them.

You can talk with bsd perimeter on getting such features.

The button works on 17'th snapshot.

Thanks.

I have experienced this too.

The latest snap from today - August 17 has an additional bug too.  When I disconnect a PPPoE interface, I get a :

500 - Internal Server Error

when the page tries to reload.  I was only able to get my PPPoE to reconnect by going through the interface assignment PPP tab and clicking save on each of the PPPoE interfaces.

Also, it made me re-populate the Idle Timeout under Show Advanced options.  I have this set to 0 nominally.

I still had to go into each gateway to get them to show up as available again too.

– Phob

Great!

If it's on two different interfaces you can't provide any assurance of where that ARP will end up being seen. It'll work with different gateways on two different interfaces that are on the same IP subnet, but may not use the interface you expect it to.

That's great news, thank you for taking the time to reply!

Best regards, and if you ever find yourself down here in São Paulo, the beer's on me!

Marcello

Thank you.

Are you using shared key or PKI?

That's a little odd. I haven't seen that myself, and I've been upgrading my VMs with auto a lot yesterday and today.

You might have pulled down an 'update' while it was in the middle of being uploaded, perhaps.

If it happens again, update the thread, but it was probably a fluke.

sorry it seems I did not looked carefully

Found a temporary solution for authenticate LDAP - AD:

Modify /usr/local/pkg/squid.inc

Around line 1021:

To```
$conf .= "auth_param basic program /usr/local/libexec/squid/squid_ldap_auth -v {$settings['ldap_version']} -R -b
{$settings['ldap_basedomain']} -D {$settings['ldap_user']} $password -f "{$settings['ldap_filter']}" -P {$settings['auth_server']}$port\n";

Difference: Remove -u uid parameter and add -R to work. Hope this help others and tks for great firewall.

This seems to be related to the rogue bootblocks I described in another thread. Works fine when using the correct boot loader.

I have my DD-WRT setup exactly like that …

Here is the important setup step:

Setup -> Basic Setup

Then you setup your Wireless as usual.

Since I have checked "Assign WAN Port to Switch" I can use the WAN port to connect to my pfSense (well the switch where it is connected).

The captive portal will be active for all your LAN clients, if this is what you want this will work. If you want to only have you Wireless Clients on captive portal, then you will need a different setup, involving an other net adaptor or vlan… Or you'll have to add pass-through MACs. I don't use Captive Portal so...

MageMinds

Looks like this should be fixed now, based on the ticket and commits that happened yesterday.

Sure!

Here are my three part rules, Floating, WAN and LAN rules to make it works.

In the Floating Rules, you can see a lot of what the Wizard did, but I flushed what I didn't care about. Keep in ming that the default queue is qP2P so you don't need a rule to send uncategorized traffic to this queue, but when you do so all the data will be sent to this default queue ACK included. So bulk traffic that you want to get the maximum throughput need a rule to categorize their ACK packets. You will see that the ACK for bulk are not sent to the qACK, because I don't want the ACK of bulk traffic to be sent at the same priority of the ACKs of my HTTP traffic.

I found that the Floating Rules works for anything that doesn't involve a NAT'ed port to your LAN, if you do have a server you need rules in WAN and LAN too.

In the floating rules you'll see a rule that prioritize "NetBIOS and SMB" I don't need it in WAN&LAN because I don't have a NAT, it's being used through IPSec VPN.

In WAN rules you'll see the rules created by my NAT, I gave those rules the queue where I want to traffic to go. And in LAN you'll see the rule I created myself that is a mirror of what you find in WAN and I gave them the same queues as in WAN.

Oh and I changed the queue configuration, because qP2P was limited to a certain speed, I've unlocked this queue to allow the queue to consume all the bandwidth, but share it entirely to other queue when they need it.

I'm no where near an expert with this, but this is my working setup, I might have rules that are unnecessary, but I've tested everything and this is working for me and I'm happy…

ok nice, got it.. thanks….