You could also just switch the NICs from the console to make the former outside interface the inside interface and so on. Then you'd be able to access the web GUI. Or in VMWare change the Virtual LANs that the NICs are attached to. Or set a static and manually connect your client PC to the (formerly LAN, currently WAN) side and access the GUI. There's many ways it seems to resolve this but I don't think anyone here could tell you why VMWare suddenly decided to alter the virtual NIC assignments or if they were not altered in VMWare then why/how they got detected in the wrong order causing pfSense to get confused. If your wanting to fix it there are plenty of possible ways a few of the more obvious of which are stated above. If you're wanting to explain the cause of it then searching vmware KB articles might be more productive than asking here. Given the low cost of putting together a simple fanless flash-based low power appliance (I use a "set-top" type PC) to run pfSense the whole virtual thing doesn't make much sense to begin with unless it's just VM's themselves that you are trying to firewall.
On Mon, Nov 3, 2014 at 11:35 AM, Jim Thompson <[email protected]> wrote: > > > On Nov 3, 2014, at 7:25 AM, Brian Caouette <[email protected]> wrote: > > > > Out of the blue this weekend pfsense went down. After further > investigation i've found that in VMWare 4.1 the status of the nics are > inverted. The ones that should be connected are disconnected. The ones > there had nothing plugged in show connected. If I unplugged the cable is > goes to connected and vise verse. I powered down the server a Dell 2850 and > powered it back up. No change. I used the ESXI cd and did a repair. No > change. I can't even get to the management software because the nics status > is reversed and for whatever od reason pfsense never auto starts. Can > anyone point me in the right direction to get this resolved? > > You could update. Your hardware is quite old. Your software is likely > quite old. > > First, this isn’t Dell or VMware customer support. > > You don’t state the version of pfSense that you’re running. > > VMware 4.1 was first released in July of 2010. 4.1 update 3 was releases > in August 2012. There is an update to 4.1.3 in April of this year. > > The PowerEdge 2850 was released in 2005, and given that the follow-on 2950 > was first released in 2006, your 2850 dates from nearly a decade ago. > > It’s likely that the savings on your power bill could pay for a modern, > low-wattage server. > > > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
