Forum Discussion
F5 BIG IP and wmware workstation
I just started the F5 course. My lab seems to me to be architected like that of the TP. I run it from a VMware Workstation 16. Everything is OK, except the possibility to attack the "external" paw 10.10.10.0/24 from my client machine.
A ping of ip self 10.10.10.200 with the port lockdown allow default option from the PC_Client is failed. A ping of 10.10.10.1 from the PC_Client responds.
The "external" network is connected to my vmnet13 which also connects my Client and the "1.2" interface via the external vlan of the F5-BigIP.
It is therefore impossible for me to perform the access test in HTTP and HTTPS to my VS 10.10.10.10 which does not respond.
If anyone has a lead, I thank them in advance.
Kind regards
farid95 - if you have not been able to resolve this yet let me know and I will see if I can get an expert to take a look.
- farid95
Nimbostratus
I couldn't find a solotion
here is my LABnetwork:
vmnet13 host only 10.10.10.0/24
vmnet12 host only 172.16.10.0/24Network adaptater 2: vmnet12
Network adaptater 3: vmnet13Internal VLAN: Interface 1.1
External VLAN: 1.2 interfaceSelf IP : 172.16.10.200 , vlan internal
self IP: 10.10.10.200, vlan external , port lockdown default allow
Ping NOK from my physical machine to 10.10.10.200VS: 10.10.10.10:80 with http profile
the VS is not reachable from my physical machinedo you have a solution?
- Jonathancert
Nimbostratus
I want to make sure i understand your problem. I believe you want to connect to your VS in VMware form your physical machine and not through a virtual client within VMware. I've been working on a VMware lab also. I have two LTM in active/standby and one GTM. I am able to ping my VS from mt physical machine and even connect to the VS via a browser. Is it possible your PC firewall could be blocking things. Is this what you are trying to do (see below).
kjl0000@(dscclab-ltm1)(cfg-sync Disconnected)(Active)(/Common)(tmos)# sho ltm virtual
------------------------------------------------------------------
Ltm::Virtual Server: cbt_nuggets_vs
------------------------------------------------------------------
Status
Availability : available
State : enabled
Reason : The virtual server is available
CMP : enabled
CMP Mode : all-cpus
Destination : 192.168.157.50:80C:\Users\Jonathan>ping 192.168.157.50
Pinging 192.168.157.50 with 32 bytes of data:
Reply from 192.168.157.50: bytes=32 time=1ms TTL=255
Reply from 192.168.157.50: bytes=32 time=1ms TTL=255
Reply from 192.168.157.50: bytes=32 time=1ms TTL=255
Reply from 192.168.157.50: bytes=32 time=1ms TTL=255
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com