New answers tagged

0

Yes it's possible. Create the virtual switches in ESX, and assign the NICs on the VMs accordingly. You'll have one vswitch for the public network, and at least one additional with no physical NIC associated with it for the private network. You probably don't want both a public and private IP on the Windows VMs, as that would defeat the purpose of having a ...


0

What is the default gateway and IP settings for the End Machine? This might indicate that the End Machine is not routing IP addresses outside its subnet to the correct gateway. "Running traceroute to a 192.168.5.x machine from the switch turns up 0.0.0.0 as the first hop. But pinging the same machine from the switch turns up successful."


0

I did this creating a new vSwitch, in this vSwitch you need to put the 2 servers. This new vSwitch maked a virtual network for you. Add this new network with another interface to the pfsense, and then config the new private network in the pfsense inside the DMZ.


1

Uncheck "Share this network with management OS" in the switch configuration if you don't want the management OS to use that network.


0

NAT reflection is disabled by default, so tests from your internal network are going to fail. From pfSense's Troubleshooting Guide: Port forwards do not work internally unless NAT reflection has been enabled. Always test port forwards from outside the network, such as from a system in another location, or from a 3G/4G device. I think I've tripped over ...


1

If you have other 'device' stats then munin-node at the 'device' platform observed is working. So you can start by check munin-node list of plugins reported by the device by 'telneting' to port 4949, as explained at munin-node test wiki http://munin-monitoring.org/wiki/MuninTroubleshooting . Then I guess you have to check what interfaces you want to ...


0

In addition to everything else Per has said. You're AP gateway is pointed at itself. It needs to be pointed at the router.


0

You need to disable the DHCP server on the TP-link box. Most likely your wireless clients are getting DHCP off your AP and you haven't configured a correct gateway and DNS.



Top 50 recent answers are included