alright,

so i managed to figure out the difference between the setups and i got my tunnel working - i can now ping across the network however with the custom options box now missing from 2.0 it's not so easy to force all traffic through the tunnel

i used the site-to-site using pki tutorial http://forum.pfsense.org/index.php/topic,12888.0.html and in that it tells you to leave the client interface ip blank - once i filled it in it worked into a pfsense2.0 server

theres a checkbox for force all client generated traffic through the tunnel however i dont think its working or i have something in my configuration thats wrong

anyone point me in the right direction?

i want to be able to flow through the vpn and come out the wan on the other site as it has access to network resources i cant get on the client side - i have this working perfectly under 1.2.2 using the  - push "redirect-gateway def1" - custom option

Fixed my problem… just went back to factory defaults and started from scratch.  For some reason the first time it came up I never got the Wizard, but after a factory restore it came up and everything started working correctly.  I did get some unusual errors about readonly, since it is a embedded device and a random reboot in the middle of booting up, but it eventually came up and I was able to configure everything.

We converted from CVS to git over the weekend, and are still working out some kinks and figuring out everything. Snapshots are on hold temporarily. They're building right now, if things test out okay they'll be back later this week.

@dotdash:

I have had no trouble with 1.2, 1.2.1, 1.2.2, and 2.0-Alpha-Alpha on various Alix 2c3's.

Could you post a dd image for a working 2.0 pfSense on ALIX?

After some more testing and trying some new snapshots. It appears that none of the new rules I create via the webUI are actually getting created. Any suggestions?

Can anyone whose using multi wan with v2.0 tell me what build date they are using? I've tried numerous snapshots and multi wan seems to be broken, Im sure I read reports here of people successfully getting multi wan working on v2.0.

Thanks

Hi
also look for this option
any news please !

;D

Takes a big man to admit guilt!  :P

;D ;D

exemple of my states logs…

udp  192.168.0.1:29369 -> 192.168.0.1:53  MULTIPLE:MULTIPLE 
udp 192.168.0.1:53 <- 192.168.0.1:29369
udp  192.168.0.1:29369 -> 192.168.0.1:53  SINGLE:NO_TRAFFIC 
udp 192.168.0.1:53 <- 192.168.0.1:21070 NO_TRAFFIC:SINGLE

In cvstrac:  http://cvstrac.pfsense.org/tktview?tn=1864

Ermal recently said he's swamped right now but I'm sure he'll get this resolved.  Solution is just to change the setup process to run ifconfig xx up for each interface before creating lagg.

fixed after reboot

-BUMP-

Any update on this?

Auto update has never work on ALIX for any release.  You have to reflash.  I would be GREAT if they could fix this in 2.0.

my problem seems that i cannot add this in the client specific config

iroute 192.168.200.0 255.255.255.0

some help please

MAN are for metropolitan area.  MAN = 50 Mbps and Internet=10 Mbps so I need them into my shaper to separate traffic with different speeds. All traffic with dest MAN can have 50 Mbps than everything else is shaped with HFSQ (dns, http, p2p etc).

For now I'm running this by using 9 aliases wich is pretty messy :D

I just noticed,

that after the pppoe connection is reset, the dyndns accounts don't get updated  :o