btw: You can delete on both interfaces all the rules except the first.

See my signature why ;)

System, Advanced: check the box to disable the firewall. If you STILL can't ping, I would verify the hardware setup- NIC in the firewall, switch, etc…

If i understand correctly…. When connection through first provider is not a vpn connection(connected directly to main office by dsl), then when openvpn(on second prov) is up - it'll be primary connection(primary for certain network).  And when ovpn drops, pfsense will use dsl then, right?

Thank you GruensFroeschli,

i think i'll not touch my current configuration, i already insert the pfsense WAN-ports in my routers "exposed host" section.

Afterwards i will change/remove the pfsense and try it with an hardware dual wan/loadbalancing router (Lancom 1811)

Thanks all anyway for your answers
MBChris

Many thanks, I'll try that.

Hi ,

Its is works?

What I do is set up aliases
that Rep your dads Subnet and then another for your machine then under Lan tab just set rules for what goes where w/ gate way policy based routing

also using the rock Star failover feature you shouldn't loose Connections

Love you guys! Never noticed that option was there until you read it out! HAHA.

@GruensFroeschli:

do you have these NAT rules on the manual outbound NAT page?
because this page is for outbound rules.
for inbound rules you use the normal NAT page.

no, i dont have outband nat

just enable outbound, 1 rules for lan, 2 port forward, each for wan and opt1

LMAO I knew someone would call me out for me to do it :).  I can probably start it, but i wil get lost in the loadbalancing routing.  Unless someone already has a simple vmware setup they want to share.

OK thanks.. It just seems a little strange that services running on the firewall will still "see" broadcast traffic (DHCP, etc) with the rule in place, but not multicast.  I would have thought it should always see both regardless of where they're being forwarded.  In any case, I ended up adding a rule "source * destination 239.0.0.0/8 gateway *" at the top of the list which resolved the issue for all of the devices on the network.

Yes static routes for DNS is vital.  I would suggest using the ISP DNS servers and setting up static routes to them.

^ Almost perfect. The interface you select needs to be the interface the rule will apply to (the interface the traffic is originating on). So you can change it to LAN, or whatever other LANs you're using.

In my case, this problem only manifested itsself on my second LAN (not my default LAN) so I created two of these rules, both for the "Public" interface. (In my case I was using an interface called Public).

@sai:

That does not make any sense to me either. What are your NAT rules?

for example
interface OPT
external address ANY
protocol TCP/UDP
external port range (irrelevant)
nat ip some network IP (irrelevant)
internal port xxxx

on firewall rules everything same, except, gw is default, and default gw is WAN ???
:)

but it works now, no complain ;)

if you dont have a VLAN capable device in front of the fxp1 that is configured to handly VLAN tagged packets it wont help you to create a VLAN.
If you have static IP's for the WAN's then use VIP's.

No answer. Is my question stupid or what?  ???

Can someone please tell me how to make a subnet from my C class (/24) WAN available on OPT3 (subnet like (/25 or /26) ) via routing?

Thank you.

http://doc.pfsense.org/index.php/MultiWanVersion1.2