Yes, it was a browser issue.  I didn't come accross the same problem doing a search. The speed seems better now that the correct settings are in place.  It also held an IPSEC VPN connection over the weekend without dropping…

Nope, not supported! Thanks for the link. Now I know.

so is there anything looking wrong ? I need to mention that the similar setup worked perfectly using 1.2.3

Infrustructure on pfsense site had some down time due to a faulty equipment and should be ok now.

Get the current version of FreeBSD, load it onto a machine/ VM then try to extract the .ko module and copy to pfSense? Alternatively, you'll need to extract the files, load FreeBSD 8.1R onto the VM and compile then extract the .ko module onto a thumbdrive and copy into pfSense. See:  http://forums.freebsd.org/showthread.php?t=16186

Hi ermal, this is looking good now, finally working :) thnx a lot to you and sullrich stefanero

that is far as it gets then the upgrade fails

Hello, I have the same problem but have managed to resolve it partially. We now have access to our internal network via PPTP connection but no access to internet while connected. I know that one fix is to disable something in the client VPN setup (something about not using default gateway on remote network). This could be done but it means we have to change it on all our employees computers… It would be really nice to get the old functionallity back. Current setup that allows access to internal Servers and Lan: WAN: x.x.x.x <- public IP and also some Virtual IPs LAN: 10.0.0.x ServerLan: 10.0.2.x RemoteServer: 10.0.242.1 RemoteAdressRange: 10.0.242.16 Set up manual PPTP VPN iface rule : Proto * Source * Port * Destination * Port * Gateway * Queue * Schedule none Description blabla

I got RFC 2136 updates to work by putting in the complete FQDN of the hostname to be updated in the "host" field. I updated the ticket requesting a change to the GUI. The field SHOULD read, "fully qualified hostname to be updated"

Was named and thought it had rebooted, but I guess not. It works after a reboot. Thanks

mmhhh… I am still investigating... it looks like I mistaked the problem, even if a problem there is... The rule "lan to *" is set up in the firewall as an "interface rule" (not floating)... that rule is assigned to: "qIN_Navigazione" as queue "qOut_Navigazion" as ack queue the matter is that only the "qOut_Navigazion" is filled, the "qIN_Navigazion" is not used at all... so it makes sense that the qOutNavigazion has that amount of traffic... the only thing I can't understand is why the queue is not used... I have the rule (from rules.debug): pass  in  quick  on $LAN  from 192.168.0.0/24 to any keep state  queue (qIN_Navigazione,qOut_Navigazion)  label "USER_RULE: Consenti Uscita" and the queues are: altq on  em2 hfsc bandwidth 2Gb queue {  qWan_Local_In,  qWan_Local_Out,  qWan_Ext_In,  qWan_Ext_Out  } queue qWan_Local_In on em2 bandwidth 200Mb queue qWan_Local_Out on em2 bandwidth 200Mb queue qWan_Ext_In on em2 bandwidth 20Mb {  qIn_Alta,  qIn_Bassa,  qIn_Altissima,  qIN_Navigazione  } queue qIn_Alta on em2 bandwidth 70% hfsc (  default  )  queue qIn_Bassa on em2 bandwidth 10% queue qIn_Altissima on em2 bandwidth 10% hfsc (  realtime 1Mb )  queue qIN_Navigazione on em2 bandwidth 10% queue qWan_Ext_Out on em2 bandwidth 20Mb {  qOut_Alta,  qOut_Bassa,  qOut_Altissima,  qOut_Navigazion  } queue qOut_Alta on em2 bandwidth 70% queue qOut_Bassa on em2 bandwidth 10% queue qOut_Altissima on em2 bandwidth 10% queue qOut_Navigazion on em2 bandwidth 10%  the qOut_Navigazion is used ONLY in the above rule, so if it's used, it should be used the qIn_Navigazione also… don't know... do you have an answer? Thanks, Michele

@ermal: Can yo ushow screenshots of your rules? Aslo the relevant system log and blocked packets from filter log? The screenshot of my rules is shown in my original post: The firewall logs show this: Mar 25 15:30:14 poes10   x.x.x.x:46655   64.235.47.134:80 TCP:S Mar 25 15:30:38 poes10   x.x.x.x:46655   64.235.47.134:80 TCP:S Mar 25 15:31:26 poes10   x.x.x.x:46655   64.235.47.134:80 TCP:S Mar 25 15:33:03 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:33:06 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:33:12 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:33:24 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:33:48 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:34:37 poes10   x.x.x.x:35882   69.30.193.218:80 TCP:S Mar 25 15:36:13 poes10   x.x.x.x:46273   72.232.223.58:80 TCP:S Mar 25 15:36:16 poes10   x.x.x.x:46273   72.232.223.58:80 TCP:S The firewal log Mar 25 15:03:11 pfsense dhclient[30076]: DHCPREQUEST on em0 to 10.1.1.1 port 67 Mar 25 15:03:11 pfsense dhclient[30076]: DHCPACK from 10.1.1.1 Mar 25 15:03:11 pfsense dhclient: RENEW Mar 25 15:03:11 pfsense dhclient: Creating resolv.conf Mar 25 15:03:11 pfsense dhclient[30076]: bound to 10.1.1.56 – renewal in 1800 seconds. Mar 25 15:11:39 pfsense apinger: ALARM: WAN(10.1.1.1)  *** down *** Mar 25 15:11:43 pfsense apinger: alarm canceled: WAN(10.1.1.1)  *** down *** Mar 25 15:11:49 pfsense check_reload_status: reloading filter Mar 25 15:11:53 pfsense check_reload_status: reloading filter Mar 25 15:33:11 pfsense dhclient[30076]: DHCPREQUEST on em0 to 10.1.1.1 port 67 Mar 25 15:33:11 pfsense dhclient[30076]: DHCPACK from 10.1.1.1 Mar 25 15:33:11 pfsense dhclient: RENEW Mar 25 15:33:11 pfsense dhclient: Creating resolv.conf Mar 25 15:33:11 pfsense dhclient[30076]: bound to 10.1.1.56 – renewal in 1800 seconds. Mar 25 15:36:38 pfsense php: /system_advanced_admin.php: Successful webConfigurator login for user 'admin' from 10.1.3.20 Mar 25 15:36:38 pfsense php: /system_advanced_admin.php: Successful webConfigurator login for user 'admin' from 10.1.3.20 Mar 25 15:37:21 pfsense check_reload_status: syncing firewall Mar 25 15:37:21 pfsense check_reload_status: reloading filter Mar 25 15:42:59 pfsense check_reload_status: syncing firewall Mar 25 15:43:22 pfsense check_reload_status: syncing firewall Mar 25 15:43:30 pfsense check_reload_status: syncing firewall

Solved this with the help of this thread and post:  http://forum.pfsense.org/index.php/topic,34714.msg180818.html#msg180818

@ermal: It means that rules should not override each other like 'foot stepping each other'. Waiting for the results. Until now  with some added deleted edited and limited MACs.  without problems  :D Thanks [2.0-RC1][root@quinimari.compuven.local]/root(1): ipfw show 00002      0         0 pipe 20003 ip from any to any MAC 00:02:2d:b3:21:26 any 00003      0         0 pipe 20002 ip from any to any MAC any 00:02:2d:b3:21:26 00004      0         0 allow ip from any to any MAC any 00:02:6f:6f:57:7f 00004  51977   7161831 allow ip from any to any MAC 00:02:a5:7c:4f:96 any 00005  59786   8611488 allow ip from any to any MAC any 00:02:a5:7c:4f:96 00005 517842 292105249 allow ip from any to any MAC 00:1a:70:75:e7:e5 any 00006 490410  38676017 allow ip from any to any MAC any 00:1a:70:75:e7:e5 00006      0         0 allow ip from any to any MAC 00:1a:80:f2:02:ab any 00007      0         0 allow ip from any to any MAC any 00:1a:80:f2:02:ab 00007 120743 123749246 allow ip from any to any MAC 00:1b:b9:a2:f7:9f any 00008  89283  13542185 allow ip from any to any MAC any 00:1b:b9:a2:f7:9f 00008  10960  13609926 allow ip from any to any MAC 00:1d:92:f5:8b:37 any 00009   7208    938701 allow ip from any to any MAC any 00:1d:92:f5:8b:37 00009      0         0 allow ip from any to any MAC 00:1e:ec:2d:2e:04 any 00010      0         0 allow ip from any to any MAC any 00:1e:ec:2d:2e:04 00010      0         0 allow ip from any to any MAC 00:1f:3c:4b:50:97 any 00011      0         0 allow ip from any to any MAC any 00:1f:3c:4b:50:97 00011  20454  19476067 allow ip from any to any MAC 00:21:27:f1:33:26 any 00012  17522   3396144 allow ip from any to any MAC any 00:21:27:f1:33:26 00012  94997 113900837 allow ip from any to any MAC 00:22:6b:8c:95:56 any 00013  70925   8551948 allow ip from any to any MAC any 00:22:6b:8c:95:56 00013      0         0 allow ip from any to any MAC 00:22:fb:6d:bd:be any 00014      0         0 allow ip from any to any MAC any 00:22:fb:6d:bd:be 00014  49533  59557085 allow ip from any to any MAC 00:23:cd:f8:95:a6 any 00015  47353   4936692 allow ip from any to any MAC any 00:23:cd:f8:95:a6 00015  41755  51038612 allow ip from any to any MAC 00:23:cd:f8:97:cd any 00016  31249   3955573 allow ip from any to any MAC any 00:23:cd:f8:97:cd 00016   1988   2194783 allow ip from any to any MAC 00:23:cd:f8:9a:1d any 00017   1737    294107 allow ip from any to any MAC any 00:23:cd:f8:9a:1d 00017    279    123185 allow ip from any to any MAC 00:23:cd:f8:9a:7a any 00018    524    325603 allow ip from any to any MAC any 00:23:cd:f8:9a:7a 00018      0         0 allow ip from any to any MAC 00:25:86:cf:01:d1 any 00019      0         0 allow ip from any to any MAC any 00:25:86:cf:01:d1 00019      0         0 allow ip from any to any MAC 00:25:86:ce:fb:e3 any 00020      0         0 allow ip from any to any MAC any 00:25:86:ce:fb:e3 00020      0         0 allow ip from any to any MAC 00:25:86:cf:00:7b any 00021      0         0 allow ip from any to any MAC any 00:25:86:cf:00:7b 00021 114940 159257826 allow ip from any to any MAC 00:25:86:cf:05:aa any 00022  77760   6035113 allow ip from any to any MAC any 00:25:86:cf:05:aa 00022 157628 178130744 allow ip from any to any MAC 00:25:9c:14:05:e4 any 00023 155219  18717579 allow ip from any to any MAC any 00:25:9c:14:05:e4 00023  34616  36185409 allow ip from any to any MAC 00:27:11:00:1b:d7 any 00024  43762   5240806 allow ip from any to any MAC any 00:27:11:00:1b:d7 00024   9785   8688988 allow ip from any to any MAC 00:27:11:00:1c:6b any 00025   8723   1267447 allow ip from any to any MAC any 00:27:11:00:1c:6b 00025  71031  70493621 allow ip from any to any MAC 00:27:11:00:1b:55 any 00026  85295  18539086 allow ip from any to any MAC any 00:27:11:00:1b:55 00026  88291  99202415 allow ip from any to any MAC 00:27:11:00:1c:69 any 00027 106236  12353854 allow ip from any to any MAC any 00:27:11:00:1c:69 00027  46878  53463407 allow ip from any to any MAC 00:27:11:00:1c:6a any 00028  49956   6038922 allow ip from any to any MAC any 00:27:11:00:1c:6a 00028   1045    922766 allow ip from any to any MAC 00:27:11:00:1c:a4 any 00029   4205    367017 allow ip from any to any MAC any 00:27:11:00:1c:a4 00029      0         0 allow ip from any to any MAC 00:27:11:00:1c:a5 any 00030 162944 139005462 pipe 20031 ip from any to any MAC 00:27:11:00:1d:6a any 00031 143211  37302976 pipe 20030 ip from any to any MAC any 00:27:11:00:1d:6a 00032  15467   1338181 allow ip from any to any MAC any 00:27:11:00:21:2b 00032  28725  26521616 allow ip from any to any MAC 00:27:11:00:22:8a any 00033  27162   5421497 allow ip from any to any MAC any 00:27:11:00:22:8a 00033  19348  15383230 allow ip from any to any MAC 00:27:11:00:22:8e any 00034  28742   3775913 allow ip from any to any MAC any 00:27:11:00:22:8e 00034 103500 123350415 allow ip from any to any MAC 00:27:11:00:22:ff any 00035  86284  10659014 allow ip from any to any MAC any 00:27:11:00:22:ff 00035 141923 193217703 allow ip from any to any MAC 00:27:11:00:23:ac any 00036  95859   9334524 allow ip from any to any MAC any 00:27:11:00:23:ac 00036  26605  29348500 allow ip from any to any MAC 00:27:11:00:57:30 any 00037  21061   2722403 allow ip from any to any MAC any 00:27:11:00:57:30 00037      0         0 allow ip from any to any MAC 00:e0:4d:8f:6a:d7 any 00038      0         0 allow ip from any to any MAC any 00:e0:4d:8f:6a:d7 00039      0         0 allow ip from any to any MAC 00:23:cd:f8:96:fc any 00040      0         0 allow ip from any to any MAC any 00:23:cd:f8:96:fc 00040 231487 324449546 allow ip from any to any MAC 00:23:cd:f8:9a:7b any 00041 164734  11210857 allow ip from any to any MAC any 00:23:cd:f8:9a:7b Does not look to be a missed "any"

@ermal: On a closer look that seems like a hardware issue rather than software. Can you check your hw first? ok… I updated the motherboard's bios and I disabled ACPI... don't know what to do exactly to test this hardware, the only thing I could think is some issue on the onboard ethernet adapter, which is marked VR0 (VIA), while the other interfaces are 3Com (XLn)... After this bios update I will let you know if it hangs again... Thanks a lot! Michele

If we set the gateway for the WAN interface to "none" it seems to work fine. Now the pfSense uses the right static routes.