Not really. I run one from my house (2.0) to an employer (1.2.3) and it works flawlessly.

Also would like to vote for multiple gateways settings :)

I found another bug in how that box was getting checked. It should be OK in snapshots dated after this post.

It's built into the 2.0 kernel. You do not need to touch loader.conf at all.

@_igor_:

I've had the same probs updating from 1.2.3 to 2.0. Simple config but blew up the router. It was not a nanobsd-upgrade, it was a normal instzall. Installing from scratch and configuring by hand was the only solution. I stated this here: http://forum.pfsense.org/index.php/topic,26536.0.html
I think that you may have luck or not.
My config was sent to cmb.

That is probably a different issue. He forwarded me a copy of that config but I haven't had a chance to test it out.

Thnx!
I added nobody, re-saved all users and all show up in passwd now.

Thanks many times ;)

From what I can see, you would have to mathematically calculate what should be there (in hex), based on the format described in RFC3442 (http://www.faqs.org/rfcs/rfc3442.html)

OK, nevermind, got it now.  All working as desired.

Now, how to work on the throughput.  The reason for the VPN is so that I can get Skype and Internet TV such as Netflix, VUDU, etc., over where I live in the Middle East.  Thus the reason for the two LANs.

LAN1 has my regular computers I use for surfing the net and work.  Which is why I want all of that traffic to get routed straight to the net.  LAN2 has my Skype phone and Media Center PC and BlueRay player on it.  Thus why I want all of that traffic routed over the VPN to my pfSense box in the 'States.

I would like to put maximum priority on streaming traffic over the VPN.

I know this is off the topic but any suggestions on where to start?

Thanks again

Yeah they probably wouldn't route a single public IP to you (though they could and you could make it work that way, it's kinda ugly), probably be a /30.

On the console menu, using set interface address on anything will ask if you want to change to HTTP.

@kentbjoh:

Right now I have no rules on V254, but all traffic except WAN is getting through to that VLAN. If I disable the rule in vlanInternet however no traffic is passed to V254

Exactly my point - that traffic isn't initiated on VLAN254. Traffic is only filtered on the interface where it's initiated. Everything is functioning as it should be from that description. If you don't want the other interfaces to talk to VLAN254, block them on their interface, the source interface of the traffic, not the destination one.

Wouldn't have a clue my friend. In the end, if you followed the thread since the beginning, we got the ISP to "donate" some Static IPs so that issue has been resolved, but I worry about it in the future when I might have another installation.

not that I saw. I had to give up playing for a bit, but I am helping a friend tonight with the latest snap shot to test compat with a new router he was planning on installing *-wrt on. I will attempt to confirm, but when I looked, that wasn't there.

-My test machine (my other machines "1.2.3Release" I am very satisfied) "PfSense 2" with the Beta 1 build the image of the wan out of the first version of my "PPPoE" mode worked healthy. Set wan bridge mode modem took out my real IP. I came to this level so that the beta3. I wondered one day I wanted to re-install version Beta3 cd reputation. Make sure you follow the installation steps completely before making the settings, but somehow I did not wan take out the real ip .. I went two days in total, two or three previous beta was not tried it with CDs. A kind of fame has changed since the beginning of beta3 wan out what I could not get the real ip. 2. At the end of the day finally came to my mind have cd in beta1. I installed it I used the same steps wan port finally took out the real ip.
-Rate beta3 the "PPPoE" my fault?
-Beta1 or as easy, right?
-More steps needed?
-eg from Beta3 to "assign interfaces in" how PPPs should be set?
-I was very involved with PPPs, but it was not set.
Regards.

The output of the following commands from the shell would also help:

Same thing with PPPoE server logs using recent snapshots. Haven't tested the latest yet.

only wireless clients have the issue, lan clients r normal.

under system -> routing the default rule exists (Interface wan Dynamic Gateway)

I suppose you could say that an associated rule is for when you want to add some of the advanced options on the firewall rule, rather than just the simple pass.

Polling has been disabled, and my firebox is now much happier. Thank you guys for the help!

Other then that one issue I have to say I have been having a much better experience with 2.0 then I did with 1.2.3 on my firebox, I assume a lot of that is FreeBSD 8.1 but even still Bravo!