may be changes in the VSwitch/VLan Configurations prior to the reboot? serval functions of the emulated VMWare NICS ain't supported anymore by WMware in compare to older ESX Versions. at least in the case of the Intel kind. e.g. pptp will not work reliable with the emulated intel nics.
= = = http://michael-schuh.net/ = = = Projektmanagement - IT-Consulting - Professional Services IT Postfach 10 21 52 66021 Saarbrücken phone: 0681/8319664 @: m i c h a e l . s c h u h @ g m a i l . c o m = = = Ust-ID: DE251072318 = = = 2014-04-26 14:18 GMT+02:00 mayak <ma...@australsat.com>: > hi all, > > boy -- what a night -- i rebooted 2.1.2 x64 running in vmware esxi 5.5.0 > u2 and VPNs ceased functioning: > > - vmware 5.5.0 u2 on a dell 2900 > - 2 ethernet ports > - 2 gigs of memory and 32GB disk > > port 0 -- WAN > - no ip address > - no mac spoofed address > - wmware network config: mtu=1500 vlan=4095 (all) > - 2 VLANS declared on em0: 100 and 200 > - interfaces created for these two vlans -- each has an ip address -- > 192.168.1.254 and 192.168.2.254 respectively > - port0 connect via physical cable to a Dell 3524 switch port 48 that is > configured to be a trunk carrying vlans 100 and 200 > - dell 3524 port1 connected to adsl1 -- access level port member of vlan > 100 > - dell 3524 port3 connected to adsl2 -- access level port member of vlan > 200 > > port 1 -- LAN > - connects to another port on Dell 3524 along with PCs, etc > > problem > - if pfSense is rebooted, i cannot ping either adsl > - no traffic can pass > - it will sit for hours and no change > > solution > - open each: Interfaces -> vpnInterfaceName -> click save on each -> hit > Apply Changes > - adsl interfaces are now operational > > what could this be? > > thanks > > m > _______________________________________________ > List mailing list > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
