Performance in VSphere and the new RC2…
-
First of all thks for a very nice product(1.2.3)! :)
I am currently testing different scenarios in VmWare Vsphere. (2.0 RC2)
On boot it hangs for a couple of minutes on OpenNTP client waiting….
Jun 4 19:59:18 kernel: IPsec: Initialized Security Association Processing.
Jun 4 19:59:18 kernel: acd0: CDROM <vmware virtual="" ide="" cdrom="" drive="" 00000001="">at ata1-master UDMA33
Jun 4 19:59:18 kernel: da0 at mpt0 bus 0 scbus0 target 0 lun 0
Jun 4 19:59:18 kernel: da0: <vmware virtual="" disk="" 1.0="">Fixed Direct Access SCSI-2 device
Jun 4 19:59:18 kernel: da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit)
Jun 4 19:59:18 kernel: da0: Command Queueing enabled
Jun 4 19:59:18 kernel: da0: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C)
Jun 4 19:59:18 kernel: Trying to mount root from ufs:/dev/da0s1a
Jun 4 19:59:18 kernel: WARNING: / was not properly dismounted
Jun 4 19:59:18 kernel: WARNING: R/W mount of / denied. Filesystem is not clean - run fsck
Jun 4 19:59:18 kernel: pflog0: promiscuous mode enabled
Jun 4 19:59:19 apinger: Starting Alarm Pinger, apinger(18345)
Jun 4 19:59:21 php: : ROUTING: add default route to .228.201.113
Jun 4 19:59:29 apinger: ALARM: Telia(90.228.201.113) *** down ***
Jun 4 19:59:39 check_reload_status: Reloading filter
Jun 4 20:01:08 php: : OpenNTPD is starting up.
Jun 4 20:01:08 dnsmasq[36718]: started, version 2.55 cachesize 10000
Jun 4 20:01:08 dnsmasq[36718]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Jun 4 20:01:08 dnsmasq[36718]: ignoring nameserver 192.168.1.1 - local interface
Jun 4 20:01:08 dnsmasq[36718]: ignoring nameserver 192.168.1.1 - local interface
Jun 4 20:01:08 dnsmasq[36718]: reading /etc/resolv.conf
Jun 4 20:01:08 dnsmasq[36718]: using nameserver 195.67.199.40#53
Jun 4 20:01:08 dnsmasq[36718]: using nameserver 195.67.199.39#53
Jun 4 20:01:08 dnsmasq[36718]: using nameserver 208.67.222.222#53
Jun 4 20:01:08 dnsmasq[36718]: using nameserver 8.8.8.8#53
Jun 4 20:01:08 dnsmasq[36718]: read /etc/hosts - 2 addresses
Jun 4 20:01:08 check_reload_status: Updating all dyndns
Jun 4 20:01:13 php: : Creating rrd update script
Jun 4 20:01:13 php: : Restarting/Starting all packages.
Jun 4 20:01:13 login: login on ttyv0 as root
Jun 4 20:01:13 sshlockout[62676]: sshlockout/webConfigurator v3.0 starting up
Jun 4 20:01:14 php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Jun 4 20:01:16 check_reload_status: Reloading filter
Jun 4 20:01:19 apinger: Error while feeding rrdtool: Broken pipe
Jun 4 20:01:58 check_reload_status: Syncing firewall
Jun 4 20:02:19 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
Jun 4 20:02:27 kernel: em1: link state changed to UP
Jun 4 20:02:27 check_reload_status: Linkup starting em1
Jun 4 20:02:27 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.5.1)
Jun 4 20:02:27 check_reload_status: rc.newwanip starting em1
Jun 4 20:02:28 php: : rc.newwanip: Informational is starting em1.
Jun 4 20:02:28 php: : rc.newwanip: on (IP address: 192.168.5.1) (interface: lan) (real interface: em1).
Jun 4 20:02:28 apinger: Exiting on signal 15.
Jun 4 20:02:29 check_reload_status: Reloading filter
Jun 4 20:02:29 apinger: Starting Alarm Pinger, apinger(54119)
Jun 4 20:02:34 php: : Resyncing OpenVPN instances for interface LAN.
Jun 4 20:02:39 apinger: ALARM: Telia(90.228.201.113) *** down ***
Jun 4 20:02:42 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.101
Jun 4 20:02:42 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.101
Jun 4 20:02:49 check_reload_status: Reloading filter</vmware></vmware>Then when I add the IP adresses on the WAN and LAN, add the gateway, then the GUi becomes unresponsive. I uncheck NAT reflaction and it works for the internal sites but NOT for the internet despite having rules in place that allows access. I use the E1000 NIC's in VSphere.
It simply doesnt work….it stops responding and the routing is extremely slow!
-
Seeing it when applying a static interface on WAN. On WAN DHCP it works fine.
Static makes it unresponsive.
-
Your WAN is showing as down, so you probably have a connectivity issue of some sort. That will kill states and make the GUI appear sluggish or unreachable. While troubleshooting you can disable that under System>Advanced, on the Misc tab IIRC.
-
Thx but it doesnt make a difference. When WAN is up and using DHCP, then it is fast. Using Static config, and it becomes very slow…