yes…vmware v12 here too
I´m bit confused…so, I have both virtual box, and vmware installed. here’s a snapshot of SMAC with adapters ips:
realtek is the physical ethernet card, right now connected to internet, and appears with an external ip 177
Vmware has 2 (I really dunno why) but they show the internal address in 192.168 range, tho inside vmware, where kali linux is runnig in bridge mode I see also an external ip 177
eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 177.x.x.x netmask 255.255.248.0 broadcast 177.x.x.x
inet6 2804:14c:3baa:4000::226 prefixlen 128 scopeid 0x0<global>
inet6 fe80::20c:29ff:fe6b:4691 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:6b:46:91 txqueuelen 1000 (Ethernet)
RX packets 2275628 bytes 200574268 (191.2 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 5077 bytes 622305 (607.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
so you are using dhcp in container and you are receiving an ip in the internal 192 range?
or just setting the ip, statically? cause, like that you are still using the host external connection, you have a unique internal ip but you share the same external ip with the host, just like when you connect to a wifi hotspot, right?
here both windows and kali have their unique external ip 177. this is the ipconfig:
Ethernet adapter Ethernet 4:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2804:14c:3baa:4000::150
Link-local IPv6 Address . . . . . : fe80::c1ee:2a17:ff01:12a5%13
IPv4 Address. . . . . . . . . . . : 177.x.x.x
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 177.x.x.x
so when I go to ipchicken with kali, It shows me a different ip than when I go there on windows, got it?
there is a way to do it, cause that’s what vms do and it works, we are almost there