Status_gateways
-
Hi
Weird issue and i can't really find any info about it.
Running latest stable in a vMware-env with first 3 NIC's, WAN, LAN, WLAN.Everything is awesome, found out that my isp offers me three ip's and i got curious on LoadBalancing, added two more NICs, got ip, got loadbalancing to work, realized that i still just got 100/100Mbps so i changed it to Failover, just for fun and to try it out.
Today my box just decided to take a shit on me, no real information. Just nothing would resolv or work.
I rebooted it, still no resolving or anything. I removed the failover setting and still the same issue, rebooted, same issue. Disabled the WAN2 and WAN3. And suddenly, internet was a success.But now that i click status_gateways.php it just loads, and loads and loads and loads. Nothing is happening.
Checking Routing and it shows me my gateway properly, but i cannot get any status of it.Anything that i could do or just.. ignore it?
-
How are you connected to your isp?
If all three WANs have the same gateway IP, which seems likely, this is always going to cause problems.
I believe you can do it with three PPPoE connections but if they are all from the same place you're not really getting any benefit.Steve
-
Different Subnets from the same ISP, so different gateways for me
This is not really the issue, it worked good. But now that something b0rked i removed everything and still wonders why i cannot click status_gateways.php. Just loading and loading forever and ever.
Even after reboot -
I've been using Pfsense 2.1 Beta1 for about 3 months now.
I did a LOT of experimenting for the first 2 weeks. I must have done 7 or 8 clean installs with different package installs in each instance testing various configurations. When things went south they tend to stay south. I believe some of the problems is simply error handling not being at 100%. Maybe its Pfsense or could be the package or a combination of both. I guess if your a Unix Guru and Pfsense did spit out a valid log you would have a hint of where things went south. If no logical error was generated than theirs no way of finding the problem other than jumping into the code it self to hunt it down.
My solution and the easiest in most cases, is to perform a fresh reinstall and try not to reproduce the error again if possible.
I would not expect error handling to be at 100% as it is a very time consuming task and hey, its open source after all…....Great firewall, would love to contribute, but I have no knowledge of Unix.
