I've been using Softether for many years and never had any issues. Would be very nice to add this software to pfsense ;)

I have a similar setup. Basically, rules are tied to interfaces. And interfaces are virtual based on VLANs. So, if you won't remove VLANs, rules should be fine too. You just need to: remove igb6, igb7 from the lagg create lagg1 add igb6, igb7 to lagg1 reassign interface on vlan10  from lagg0 to lagg1 Done. All rules should be untouched. No reboots, not even a downtime. But certainly perform a config backup prior to changes.

Well, that would explain it all then Facepalm What a waste of an evening!!! Thanks

I have solved my problem, it was in the member attribute and the credentials for the ldap bind. Thank you Now i can authentify my users with the authentification diagnostic. I have to setup a captive portal and Freeradius package for the connectivity between pfsense and openldap server Freeradius is obligate for ldap loggin on the captive portal ? Sorry for my english

Thanks for the reply jimp. Do you recommend any particular router to be used in conjunction with pfSense? I can try a different device and test the up/down speed.

Your 3Com switch will need to allow you to configure and use VLANs otherwise this won't work. If you connect the modem to the switch without VLANS then everything on the switch will be able to access the modem and the laptop router won't be doing anything. You will also need to make sure that the NIC on your laptop supports VLAN tagging. You will need to setup one separate untagged VLAN port for your modem (the WAN VLAN) and have all your other devices and ports untagged on another internal LAN (which everything else connects to). The port on the switch which the router laptop connects to will need to be tagged to both VLANs. In pfsense you would then create two VLANs corresponding to those on your switch, and assign one to the WAN interface (the same as the modem's VLAN) and one to the LAN interface. If your switch doesn't support VLAN tagging, then you will need to get either a USB or PCMCIA NIC for your laptop which is compatible with FreeBSD 10.1.

Is your wireless a wireless card in pfsense?  An AP on your lan network, a wifi router?  Did you configure this wifi router as AP or is it also natting? So your saying clients wired to pfsense work just fine - its only your wireless that is having issues.  Please describe how your wireless is setup.  If interface on pfsense optX for example then you would have to configure the firewall rules on that interface to allow traffic.. By default any new opt interfaces you create in pfsense have NO rules and all traffic is blocked.

They are still routing to the IP address. But on the local segment traffic to the gateway address is ARPed then traffic is actually sent to the MAC address. All that happens is the backup node starts responding on the MAC address and the CARP VIP. The hosts don't see anything change. The switch moves the MAC address to the new port automatically. It all works pretty well.  Google for CARP, HSRP, and VRRP as has been mentioned. Good writeup in the pfSense book. You'll want to read the 2.2 release notes since the book is 2.1 and CARP VIPs changed in 2.2.

Hi John just thought I'd see if you had any more thoughts or suggestions or if you needed any more info from me.

VMs could look like more clients.  A bit of Googling should show up some tools that could help.

@LinuxTracker: So dooods.  All pfSense.org's DNS records have disappeared - pOoF! What happened? Just got JimP's tweet about it https://twitter.com/jimptwit/status/701769760560656384 "Some planned maintenance is running long." Looks like it's back… Was unable to reach anything this morning...

@Alex: You do realise you will just end up blocking Windows Update and Windows Defender, potentially leading to much wider security issues than Microsoft being able to see what apps you use. Yes, I do. Although, to be a nitpicker, the telemetry stuff is not a security concern. It's a privacy and control concern. I make the choice to have privacy (and control) in cost of security. Microsoft is not transparent and honest about what a patch does. It's not like FreeBSD, pfSense, and Linux distros. There are numerous articles mentioning that Microsoft introduced telemetry in Windows 7 and 8 WITHOUT being clear about. Without giving users the choice. If you use Windows, you have two enemies: the malware creators and Microsoft itself. By using Windows I accept that my computer is insecure. I mitigate the issue by using none of the bundled software (I hope that'll manage to have Skype updated, if not I'll just run it in a VM), using an anti-virus solution, relying on the firewall of my modem-router (and pfSense could very well replace that), and being religious about backups.

Hi, what is the status of Status: Gateways have a look in Status: System logs: Gateways maybe the apinger is doing some strange thing.