Dear chanrio13 Thank you for your reply. I think the static IP Address is better way for router.

Alright, so after a ton of digging I came across a site with someone having the same issue as me. It turned out to be a acpi issue. So I followed in his footsteps and disabled acpi in the bios and booted pfsense with the disable acpi flag. This seems to have done the trick for me. I no longer lose one of my wans now. It appears to have completely corrected my issues. I could not be happier right now!!! I can't tell you how many nics I swapped in out, cheapo routers I swapped, etc. I hope this may help others who were in my boat. Time to get this beast back together, and back in the rack. Thank you to the people who responded to my plea!

i think its possible if you will make your modem / router to router mode (the modem is the one that dials PPPoe) and leases a static IP

I believe the issue displayed here is only cosmetic on the Status>Interfaces page. Though there could be some other issue there on 1.2.3, would be fixed on 2.0 though.

That's great, thanks for the information. Glad to know I wasn't going completely mad in my understanding.

Yes that's right.

Do you have a gateway entered on the OPT1 config page? (Interfaces > OPT1). IIRC, only interfaces with gateways are put into that page.

You need to use a transparent bridge to allow public IPs on the LAN. As far as Squid, I cannot help you there my friend but my guess is once you get the bridge working you should figure it out fairly easily. WAN - Set IP, Subnet, Gateway LAN - Set IP address to "None" System Tunables -> pfil_member to 1 , pfil_bridge to 1 LAN Rules - Change LAN subnet on the ANY rule to ANY, so it should be ANY ANY (otherwise you will be locked out). Remember, when you set the IP to none on the LAN, there is no longer a LAN subnet. Now it's just a interface which is what you want. Bridge the interfaces together Configure Squid (cant help you on this one) Hope this helps, otherwise I misunderstood your post. BTW, this issue haunted me for a week, very tricky to figure out on 2.0 and a lot of experimenting and testing.

Ok, semi-resolved After I updated to a new snapshot, it started working again. For whatever reason, after I installed 2.0-RC1 and it was working right, then updated a snapshot, it stopped working and now I updated to a snapshot from today and it started working again. I will monitor it for 24 hours and post the results then mark this topic resolved. FYI, if you're using a transparent bridge make sure you have pfil_member set to 1, and pfil_bridge set to 1. Also make sure all of the rules are in place because it's very easy to lock yourself out of the pfSense box. By default, the LAN rule will allow LAN subnet to any, however when you bridge to the WAN there is no longer any LAN subnet so it's very important to change LAN to any, so on the LAN rules you should have ANY ANY.

New information: I can ping the WAN interface from the router but not the LAN interface even though all routes are in place. Something on the firewall is blocking the traffic through to the LAN… even when IP filtering is turned off!! Nothing shows in the logs either!

Ok, I will test and report. Thanks

Dear Nachtfalke Thank you very much for your help from began.

@bouncer: 2.0 RC2  ??? Configuration is for pfsense 2.0 In pfsense 1.2.3 there are no "Routing Groups" for LoadBalancing.

So you have 2 subnets in your LAN. The best practice to handle this is VLAN: Create 2 VLANs on your switch Create those 2 VLANs on your pfSense and the pfSense will be the default gateway for your 2 subnet Configure rules as you wish on pfSense That's it…

@cmb: You only need virtual IPs where the firewall must answer on layer 2 on those IPs, that's not the case when bridging (and VIPs will break bridging environments as it will create an IP conflict). Thank you Chris, enjoy your weekend!