i have added 4 rules in openvpn tab, one by openvpn with a defined gateway to the wan interface

Proto Source Port Destination Port Gateway Queue
TCP/UDP 10.62.62.0/24 * * * ADSLFREE2 none

My Firewall rules are:
              ID Proto Source       Port Destination         Port         Gateway Queue Schedule Description
Servers:
                          * SERVERS net * ! HOME net *               *        none
BezeqintL2TPDialer:
                        ICMP     *                 * SERVERS net *               * none   Allow ping to servers

UDP     *                 * 192.115.20.204 53 (DNS)       * none   Allow DNS 204

UDP     *                 * 192.115.20.205 53 (DNS)       * none   Allow DNS 205

TCP     *                 * 192.115.20.203 *               * none   Allow web 203

I can access the sites on the server normally by using the domain name from the LAN.
Only when trying to access them from WAN (BezeqintL2TPDialer) I can't seem to be able to use the Domain name. only the IP.
Since the sites are using vhost on the same IP this is a problem.

Plz help

I have the same exact problem using the same chipset. Though I'm really happy you stated that it worked for you in 1.2.3. I beg to ask it there a significant benefit to 2.0 over 1.2.3.

i have changed dns config

System: General Setup

i have uncheched
Allow DNS server list to be overridden by DHCP/PPP on WAN

and i have added the isp dns server (the same as before) in the edit box with use gateway selected

and now i can put ipsec/status on the dashboard

Ah that can be provided from HAproxy.
I do not think/know relayd can do such thing!

Great!

@Disconnect:  Here's your problem - Mon Apr 18 21:27:46 2011 WARNING: potential route subnet conflict between local LAN [10.2.1.0/255.255.255.0] and remote VPN [10.2.1.0/255.255.255.0]

You need to set a different subnet for the VPN network than your client's LAN network.  Otherwise, the client system doesn't know where to route traffic to (it sees both the VPN subnet and the LAN subnet as valid choices when it tries to contact the VPN gateway).

you can find a solution here without symbolic links http://forum.pfsense.org/index.php/topic,33901.0.html

Change freebsd ftp server to the one fits your achitecture.

Hope this helps.

Here are two log files, one (run) showing that the ppp starts if the USB modem is connected
when the alix is booted.  The second (norun) shows that the ppp does not start if the
modem is connected after the alix is booted.

system.log.run.txt
system.log.norun.txt

I Agree with Johnpoz, 0.0.0.0 - 126.255.255.255 used to be classed as 'Class A' but since the introduction of Classless routing such boundaries no longer exist.

in answer to BILTRITEPC, I can say pf2.0 has no problems with using 10.10.123.1/24 on the LAN if, I have built a  test box and have just pinged it successfully for the last 10 mins without a hickup.

I use a 10.x.x.x/24 (Actually I have 4 of them) on my home network and they all work perfectly using PF2.0 to route between them.

Can you check that all settings are correct ie, lan DNS server is running, WAN DNS servers( listed in the general settings) are running and they can be used to resolve FQDN's.

what are the WAN and LAN ip's

Something is wrong and I would like to help.

That will NAT things that may not need it, though, not just things that don't have the gateway set. That's up to you though.

Possibly. Usually this are pnp devices but if your setup works its nothing to worry about.
pciconf -liv would give you more hints on device class

Oh, and I forgot to mention, NIC setup was invoked automatically on the command line after boot wiht the new NICs and the configuration was applied to the new interfaces without any issues… nice work, guys!

Reinstall it again when the new version shows up on the package repo (2-3 minutes from now). It should export those as well.

this is the normal kernel see:

FreeBSD xxx 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #1: Mon Apr  4 06:03:23 EDT 2011    sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386

even 3 minutes seems long, I just updated mine to
2.0-RC1-IPv6 (i386)
built on Wed Apr 27 22:00:11 EDT 2011

And its an OLD P3 800mhz running on a antique of a 6GB HDD ;) and only took like 1:40 from reboot to beep.

yes i need it to! havp as parent for squid, squid transparent and multi-wan!
there is at moment no solution for this

Updated today and no errors are showing.  Thanks JimP!!

I think the issue is resolved.  I've updated several times in the last two weeks and even though my connection has dropped the upgrade completed successfully.