Thanks for the info.  I will play around with the configuration and post some results.  Perhaps others will find this useful…

Just enable DHCP on the LAN2 interface and then create firewall rules on each interface that blocks traffic destined to the other segment.

I think I get where your going with this but I think the answer is no!
Bonding only works if the device doing the 'packet splitting' is splitting them in such an 'ordered' fashion that the device doing the joining (switch/router) knows and expects how to re-join them.
If the packets are coming from completely different souses they will arrive in a shot-gun fashion. bonding requires order and harmony and the internet is anything but.

Cheers

Ok,
Resolved.
It was the windows Firewall on the aimed server. It should have been deactivated, but apparently was not (wonder why?).

Yes filtering is completely disabled. The problem was solved, there was an issue with my vlan setup on my switches.

I have had this same problem on multiple new installs with different CF cards and on multiple hardware platforms (net5501 and PC hardware)

Houston, we have a real problem here!  A problem I can live with but none the less a problem that should be addressed.

Roy…

@subfire91:

hi guys

i have 3 interfaces on my pfsense 1 for wan 1 for lan and one empty. i need to connect my linksys to the empty pfsense port and i need recommendations on the connectivity and settings.
First of all i will connect the linksys WAN port on the empty pfsense port using a cross cable right? Furthermore will static routes be needed in order for my lan to communicate with the wireless lan? Finally what settings should i configure on the linksys ? i will have to enter dns settings manually right ?

thnx for the time

Find a router that can set its wan as lan (to have an extra port) or just tape over the wan port (reminds me not to use the port), give it an ip in same subnet & don't forget to give it an address of your gateway for the DNS, and turn off the DHCP server.

No. By default the webgui is not open on the WAN. There are no open ports on a default install. If you are failing the shields up test you configured something wrong. Or it's not coming from your firewall.

what he said ^

Satellite…  dont they put you on a proxy?  The results may be showing you something related to the noc...

Thanks for the reply, I have ammended config.xml.

Cheers

Split into new topic as it was completely unrelated to the hijacked thread (please don't append to another thread unless it's clearly identical, this isn't even close to the same).

As for the problem: wallabybob posted some good questions, not enough info here to tell you anything.

Look on the doc wiki at the Multi-WAN howto. There are instructions there that cover everything you need to do, such as making load balance/failover pools or perhaps just policy routing.

Even if you don't follow it exactly, just read through and get an idea of what is going on and how things are done you should be able to adapt it to your setup.

Well, it has been over 4 days since I added a new switch between the WAN port and the ISP equipment, so that I could also add a second device with an IP address to that switch to try pinging in case of an outage.

Fortunately(?) the system has not gone down since making this change.  I am starting to think that the problem may have been with the hardware.  I had a different cheap switch in place before, which may have been causing the problem.

I'll keep watching…

Thanks!

I setup a test network with just one laptop and the pfsense box. I set everything back to defaults and went through the wizard setup using dhcp and dns on the pfsense box. Everything came up workikng great. I then updated to 1.2.3 and put it back on my production network and turned off dhcp on the pfsense box and everything came fine. Don't know if it was the update or my isp since I was trying to bounce back and forth from the pfsense box to my old router trying different configs and checking this forum. Thanks for your help and quick responses. I'm really looking forward to using this firewall for a long time to come.