@mrquintopolous:

Hate replying to myself but apparently I need to setup routes on the servers … since this is a transparent bridge, traffic needs to hit the firewall for it to be encrypted, and not hit the default gateway which is on the other side of the firewall.

Yes, if it's not directed to an IP on the firewall, it won't route it. Without that, you're directing the traffic to the default gateway, which the firewall isn't going to route, it'll pass to the default gateway as it should (that's what the host is telling it to do by using that dest MAC).

I've solved my own problem.

The REAL default gateway at work needed a route added for the ADDRESS POOL, not the client side's LAN.  Using a route for the client side's LAN allowed them to see me, but not respond to me.

Hope this helps anyone else attempting to configure a similar setup.

Ok, I assume thats installed from Packages and is fairly straight forward. I have the pfsense book so I will reference it and see if it mentions anything of it. Thanks for your help.

Is it choppy both ways?

I haven't tried that one, but I have used Pidgin+Bonjour to use local network chat across OpenVPN by running the Avahi package on both ends of the OpenVPN tunnel.

thanks,

your suggestion worked

I am still having this problem.  I have also tried just running openvpn from the command line using the above listed configs.  It just seems like the float command is not doing anything or is not working the way that it should.  I see the client try to re-establish the link, and the server just doesn't accept the connection.

Any thoughts / suggestions?

Thanks

Hi,

Problem Solved.

In WAN2 firewall rules for OPENVPN there was WAN2 gateway. I changed it to default gateway and it started working.

thanks

It seems to all be working now. I didnt change anything else so I am unsure what the cause was. Tomorrow I am bringing the 3rd branch online.

Not me, but someone else might.

It may just be a matter of setting up a FreeBSD 7.2 VM and recompiling openvpn with the option you want.

I believe that is a similar problem to what I've got over at the link below.  As far as I've seen there is no way to do it in 1.2.3 as a compile option for openvpn is missing.

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

Hello, thanks for replies, Im using udp, and tried with and without compression, and we did not improve the quality, our main problem appears to be latency, our system, alcatel OXO appear to need latency below 100ms, we need to mark whole tunnel as VoIP, and reserve bandwidth for it to lower the delay, any idea?

Thanks a lot for your reply, I have been doing some test, and test and…
You are right, 3G modems have big latency, we have between 200-300ms on all, even with great bandwidth, the latency is too much to have a clear voice call.

But we have now some lines working on ADSL routers, some of them have latency (ICMP) between 100-200ms, in this enviroment I think that priorize whole tunnel will improve enough the comunication, beacuse the tunnel have only One RDP connection(With minimun resources for 56Kb lines) and the VoIP.

So, now how can I priorize the whole tunnels? I have Pfsense 1.2.3 and the wizzard does not give much features to configure it.

Many thanks

i have one another thing to ask, is it possible if i change the configuration into something like this?

HQ office:
–-----------
WAN ip address: 102.XX.XXX.XX
Lan subnet: 10.0.0.0/16
Lan Gateway 10.0.0.1

OVPN config (server)
protocol: udp
dynamic ip: tick
local port: 1194
adress pool: 10.10.0.0/16
remote network: 10.0.0.0/16
authentication method: Shared Key

wan address: dynamic
lan subnet: 10.0.0.0/16
lan gateway: 10.0.25.1

OVPN config (client)
protocol: udp
server address: 102.XX.XXX.XX
server port: 1194
interface ip: 10.10.0.0/16
remote network: 10.0.0.0/16
cryptography: shared key

or any suggestion from the expert?  ::)

Ok, so, I made an assumption that in pfsense:

Disable all auto-added VPN rules.
Note: This disables automatically added rules for IPsec, PPTP, and OpenVPN.

…meant that some "built in" pass rules were just disabled.  I didn't realize that NOT checking this option prevents the rules one creates for the new OPT interface to be used.

I checked this and everything works!

Sorry all !!!

Found the solution:

Due to the Dual WAN solution.  all my LAN traffic  wanted to go true the  MULTIWAN  Gateway.    this means also OpenVPN traffic.

Now that I made 1 rule on my LAN    that only traffic for port 80 needs to be balanced and go true the MULTIWAY Gateway 
then 1 rule  lower pri  that lets all other traffic  true the * default gateway.

NOW my OpenVPN works in both directions

@pisang98:

Site 1 (PFSense 1.2.3-RELEASE)
Dual WAN (Fixed IP's)
OpenVPN Server
LAN 192.168.1.1

Site 2 (PFSense 2.0-BETA1)
Dual WAN (Dyn IP's)
OpenVPN Client
LAN 192.168.0.250

When I had a PFSense 1.2.3 on site 2 my OpenVPN (Site2Site) worked without any problems.

Now that I have upgraded to PFSense 2.0 (2x Dyn PPPoE)  I'm having troubles with my OpenVPN

My 2XWAN on Site2 are balanced TIER1 and thats working.
OpenVPN connects and is working.  Ping on the PFsense interfaces work to all ip's (Site1 & Site2)

Connecting from site 1 -> site 2 is working.  (OpenVPN Server)
Connecting from site 2 -> site 1 is NOT working. (OpenVPN Client)

I need a OpenVPN Bridge <-> from all networks.

I have a Firewall rule   *  *  *  *  *  *  none     OpenVPN  for the OpenVPN Traffic on Site2

I have something wrong on my new PFSense 2.0 (Site2) config.  Or I don't understand the new OpenVPN in 2.0

Please help.

Thanks, I had mess up the certificates! Now it works.