Can't replicate that. Need more details, exactly what do you mean by "null url", got a screenshot of what you're seeing?

Yeah and that's what is not working….

I opened up tcp 21 and after that I can see the dropped packets from ports higher > 35000 to the external ftp server. So the kernel proxy is not working....

Perhaps the package did not fully install correctly?

I tried a few packages and one or two didn't show up, presumably because they are not working on either pfSense 2.0 or FreeBSD 8. Others installed fine and show up.

As these are located, they will need to be fixed by their maintainers or other developers.

so basically u even make the p2p queue slower by not specifying the ackqueue?

some other things i noticed was like i said, as soon as u run the wizard and then check floating rules nothing seems to be there untill a reboot and secondly only outbound queues and rules r only created by the wizard and also in the wizard if u select the multi wan/lan then in the first screen it asks number of wan interfaces so if u type 1 in that then it wont go through.

other smaller issues i saw was the dashboard never refreshes so the CPU usage doesnt show, the traffic graph, if u select the opt1 then it graphs the in and out traffic but on the right hand side it doesnt show the ip of the wireless client and the rate at which its using, either its a bug or either my wireless is bridged to lan which is the cause of it not listing any ips.

Yes I'm pretty sure I am. I upgraded this morning. Is there a way I can tell, like a certain build string, instead of just Beta1?

@grandrivers:

what is the status of snort and snort-dev for 8.0 beta it appears that current isn't up to date and no dev version available

just checking thanks

Pfsense 2.0 uses php 5 and code has to be justed for that.

follow my changes at https://rcs.pfsense.org/users/robiscool

James

Read the iwn(4) man page carefully. It only supports station, adhoc, and monitor modes. It does not support hostap mode so it could not be used as an access point.

It could be used as a wireless WAN, however.

Should be, I'd say.

beta snapshot working smooth on alix

Those issues are worthy of a new thread if you have not started one already. I suggest you start a new topic with a relevant subject line for the traffic shaping issues.

Anybody uses it the spmad or testing ?

I've had the same problem for a month or two. CP redirect doesn't seem to be working for me either, even with an allow all rule on the interface.

Actually just today i fixed a problem with dyndns+dhcp setups.
For the other cases i am not sure other that it needs more debugging!
Try a new snapshot and report what you found.

There seems to be an update about one or two weeks ago which broke my dyndns in this way that I have to go to  Services - dyndns and have to save my settings without changing them. After this saving my dyndns-adress is actualized. The update-dyndns which is present in cron never detects a new IP-adress. I put the error on redmine.

@cmb:

http://forum.pfsense.org/index.php/topic,10332.msg57843.html

Thanks, I just read that. However, I don't consider my home a serious production environment, but I do like having a working router that load balances correctly, so I suppose I will hold off on an upgrade until the ALPHA tag is gone. ;)

@jimp:

I did find an unrelated bug and fixed it, you may want to try a gitsync on the off chance it might help.

Seems that didn't fix it either :(
I'll just go with a clean install once I upgrade my hardware, which hopefully is soon! (that PII is starting to get dusty :D)

Thanks for all the help though!

I tried the following: When I got disconnected from ISP, connected again and dyndns-update didn't run. So i run the update-command manually: /usr/bin/nice -n20 /etc/rc.dyndns.update, no success, it stated "no change of IP which is not true. Afterwards i went to the dyndns-settings and pushed "save": It stated a change of IP which is right.

Here the logs:

Dec 17 10:05:11 pfsense mpd: [pppoeclient] IFACE: Up event Dec 17 10:05:13 pfsense apinger: alarm canceled: wan(195.14.226.7)  *** down *** Dec 17 10:05:15 pfsense check_reload_status: rc.newwanip starting Dec 17 10:05:16 pfsense php: : Informational: rc.newwanip is starting pppoe0. Dec 17 10:05:16 pfsense php: : rc.newwanip working with (IP address: 78.34.164.146) (interface: wan) (real interface: pppoe0). Dec 17 10:05:16 pfsense php: : WARNING! /etc/rc.newwanip could not determine the previous IP address of wan( pppoe0 ). Dec 17 10:05:26 pfsense check_reload_status: reloading filter snipped some other info not dyndns-related... Dec 17 10:07:10 pfsense php: : DynDns: Running updatedns() Dec 17 10:07:10 pfsense php: : DynDns: updatedns() starting Dec 17 10:07:10 pfsense php: : DynDns: _detectChange() starting. Dec 17 10:07:10 pfsense php: : DynDns: _checkIP() starting. Dec 17 10:07:10 pfsense php: : DynDns debug information:  extracted from local system. Dec 17 10:07:10 pfsense php: : DynDns: Current WAN IP: Dec 17 10:07:10 pfsense php: : DynDns: Cached IP: Dec 17 10:07:10 pfsense php: : phpDynDNS: No Change In My IP Address and/or 25 Days Has Not Past. Not Updating Dynamic DNS Entry. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: Running updatedns() Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: updatedns() starting Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: _detectChange() starting. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: _checkIP() starting. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns debug information:  extracted from local system. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: Current WAN IP: Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: No Cached IP found. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: cacheIP != wan_ip.  Updating. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: Initial run.  Updating. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: DynDns _update() starting. Dec 17 10:07:46 pfsense php: /services_dyndns_edit.php: DynDns: DynDns _update() starting. Dynamic Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting. Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: DynDns: Current Service: dyndns Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: DynDns: _checkIP() starting. Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: DynDns debug information:  extracted from local system. Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: phpDynDNS: updating cache file /cf/conf/dyndns_wandyndns.cache: Dec 17 10:07:47 pfsense php: /services_dyndns_edit.php: phpDynDNS: (Success) IP Address Changed Successfully! () Dec 17 10:07:47 pfsense check_reload_status: syncing firewall

dyndns.gif
dyndns.gif_thumb

@_igor_:

Yes: Revert to http on console, delete your Cert when you access via http, wait some minutes and create the cert new. Then revert back to https. That worked for me.

Thanks, Igor, will try..

Its reported in redmine a couple of days ago, maybe fixed. Look at redmine.pfsense.org.