Hmm…that sound not really good. I hoped that someone could make a dirty hack and kill the radiusd process some time after start and then just restart it.

But I know that this is a problem of an unmaintained package :(

---edit----

Newer freeRADIUS package version solved this problem.

If that is a site-to-site SSL/TLS tunnel, with only one client, make sure you are using a /30 subnet for the tunnel network on both sides.

OpenVPN is the only VPN that currently uses the settings from the user manager. There is no privilege for OpenVPN access, not yet anyhow. Probably won't be in 2.0 since it's just about ready to ship.

Not sure about the LDAP bits.

I believe I've figured it out. I de-activated the snort icmp rules (including the so rules) and Google is now working. Normally I'd have to reboot the firewall to get it working again. I'll monitor it for a while to see if the problem recurs. I don't understand why this only affects Google and no other web sites. ???

Done again.

Thanks and no worries.

I may add that in order to install pfsense, I had to boot the installer without ACPI (option 2 in boot menu), else it hanged during the /usr copy.
Thus I prefered not activating powerd… Better being safe on this.

Also, I have another question, why do speed tests get put in the p2p queue? I thought they were http traffic…  :o

Also, as a feature request, could we get a section for FTP transfers?  ;D

PPTP seems to be working tonight without any changes.  So I guess there must have been something else going on between home and work last night.  OpenVPN also started working again after I stopped and restarted the service.

–
David

Grazman, your last problem, why does it fail when I enter the speeds in Mbit, and then use Kbit/s later.

I just tried to replicate this problem and I wasn't able to.  I entered the Up and Down speed as 5Mbit and set the qVoip to use 256Kbit/s.

Please reply with step by step instructions for replicating the problem you are seeing.  Note every option you choose.

Thanks

I've just updated to pfSense-Full-Update-2.0-RC3-amd64-20110810-1042.tgz and everything is working OK.

;D

First please update to an actual snapshot. Searching for bugs in old software isn't useful.

But perhaps it's just a misconfiguration.

Pleas show us screenshots of your:

Further tell us your subnets with subnetmask of LAN and OPT1

I have the same problems, albeit a bit different, I get this message only for one interface, when I try to put it into the same gateway group and put it on the same level to have loadbalancing.

Connections trying to use the new interface fail and the connections do not work proberly at all (most of them time out).

I use VLAN's for my WAN connections. Each ADSL Router has it's own VLAN and Network (a 10.100.<vlan>.0/28 net) where vlans are counting up from 100. So there is no overlaping.

Another symptom I have is with the failover pfsense box, which when started does not recognize it's Backup and everything is Master, I have to deactivate CARP and activate it again on the Backup-Router to have it become Backup. Then all gateways are offline except the one which is on the interface which gives me the problems described above with llinfo stuff, it stay's online and I get packet loss on both, the primary and the backup box …

The servers are no-name computers with Intel PRO dual-port server network cards.

Hope someone can figure out what's going on, i have this since the Beta through 2.0-RC3 (i386) built on August 3rd.

best,
Ray</vlan>

Well, it has been like this for a long time, through many restarts.

Ok, looked into it a bit more, and the problem seems to be that the timezone info in the FreeBSD release must be wrong.  The pfSense webGUI properly reports the time as AST (Arabia Standard Time), but the shell "date" commmand reports the time zone as ADT (Arabia Daylight Time?) and is 1 hr ahead which would be right for Asia/Baghdad and others if that time zone existed but it doesn't.

Probably not important, but I would like to see the world get synchronized, since it is 2011 and no longer 1982 :)  There must be an upgrade somewhere that could be built into a release version of pfSense…

Hi guys,

problem is solved for now. I configured another default gateway.
But it seems, that pfSense didn't take the right route. When a client tries to reach the server, pfSense routes the packets to the default gateway even though the subnet with the server is located behind another gateway for which I created a route to.

But I have a working solution now.
All in all, thanks for your help. I appreciate that!

I've attached the CARP settings of both machines. Note that both machines can reach each other by ping on the given IP's. Also there exists a rule on both machines allowing all traffic on the interface concerned. None of the usual messages appear in the GUI (I've seen them before). Also still nothing in the system logs, nor do i see anything else than pfsync traffic when i do a packet capture.


Or here:
https://github.com/bsdperimeter

Then click on:
pfsense
pfsense-packages
and then commits

@theanh3112:

i have 2 FTTH lines.

Line 1: max download: 50 Mbs/s Line 2: max download: 40 Mbs/s
I want to config that: when the line 1 is full, the packets change to line 2
Help me, pls.

This will not work like you want.
pfsense LoadBalancing is using "RoundRobin" so it changes the both lines with every new connection or do an automatic failover if one line goes down.